sig_cloud
/
diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
diskimage-builder/setup.cfg

52 lines
1.8 KiB
INI
Raw Normal View History

Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
[metadata]
name = diskimage-builder
summary = Golden Disk Image builder.
setup.cfg: Replace dashes with underscores Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I48d280192d3713e09571842d5515da2dcc637d08
2021-05-05 02:10:40 +00:00
description_file =
Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b
2015-02-07 10:30:02 +00:00
README.rst
Changed author and author-email Changed author to OpenStack and author_email to author-email Change-Id: Id1a398bfd644e8db41a8ab816c8c6ff3c322f7b4
2016-11-29 04:03:55 +00:00
author = OpenStack
setup.cfg: Replace dashes with underscores Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I48d280192d3713e09571842d5515da2dcc637d08
2021-05-05 02:10:40 +00:00
author_email = openstack-discuss@lists.openstack.org
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
license: Apache License (2.0)
setup.cfg: Replace dashes with underscores Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I48d280192d3713e09571842d5515da2dcc637d08
2021-05-05 02:10:40 +00:00
home_page = https://docs.openstack.org/diskimage-builder/latest/
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
classifier =
Update our package classifiers Our setuptools action classifiers are woefully out of date, notably: we are no longer alpha and we support python3. Change-Id: I2425152129406e22073936275761bd5d850903fb
2016-12-19 18:51:55 +00:00
Development Status :: 5 - Production/Stable
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Update our package classifiers Our setuptools action classifiers are woefully out of date, notably: we are no longer alpha and we support python3. Change-Id: I2425152129406e22073936275761bd5d850903fb
2016-12-19 18:51:55 +00:00
Programming Language :: Python :: 3
Revert "Remove py 3.6 support and update jobs" This reverts commit fe0e5324d4248d114660ec35111ae9601e05b95b. Reason for revert: Python3.6 is still being used on Centos 8 based platforms. This is a partial revert, since the py36 job is currently failing, it will be restored in a follow-up patch. Change-Id: Idc0373f9a639cd66925543376fb1e2e3398666da
2022-06-09 05:11:42 +00:00
Programming Language :: Python :: 3.6
Programming Language :: Python :: 3.7
Cleanup py27 and docs support This repo is now testing only with Python 3, so let's make a few cleanups: - Remove python 2.7 stanza from setup.py - Remove obsolete sections from setup.cfg - Update classifiers - Update requirements, no need for python_version anymore - Cleanup doc/source/conf.py to remove now obsolete content, use sphinxcontrib.apidoc to build module index again (this seems to have been broken when switching to sphinx-build). - Remove install_command from tox.ini, the default is fine - Use TOX_CONSTRAINTS_FILE instead of obsolete UPPER_CONSTRAINTS_FILE. - Update tox.ini for python3 only support. Change-Id: Id8738ecfb0f578d2a7953c63ffe10779f835bcaf
2020-06-05 07:51:28 +00:00
Programming Language :: Python :: 3.8
Remove py35 tox jobs At this point py35 practically means Xenial, and we are not interested in having that as a build platform. Drop the py35 jobs. Update python setup.cfg metadata; we are building on 3.9 so add that. Change-Id: I981f0f67a6fd809af1ab70934358dc3404890f35
2021-10-19 22:36:33 +00:00
Programming Language :: Python :: 3.9
Add support for Python 3.10 Unit tests are currently passing on python 3.10, and distributions shipping python 3.10. Mark dib as supporting this in setup.cfg Change-Id: I32dfefbe4bf5285d94b92822fd64141b748ae9ef
2022-06-03 15:48:30 +00:00
Programming Language :: Python :: 3.10
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
Environment :: Console
Revert "Remove py 3.6 support and update jobs" This reverts commit fe0e5324d4248d114660ec35111ae9601e05b95b. Reason for revert: Python3.6 is still being used on Centos 8 based platforms. This is a partial revert, since the py36 job is currently failing, it will be restored in a follow-up patch. Change-Id: Idc0373f9a639cd66925543376fb1e2e3398666da
2022-06-09 05:11:42 +00:00
python_requires = >=3.6
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
[files]
packages =
diskimage_builder
Package dib-run-parts dib-run-parts is a symlink into the elements directory. During packaging the symlink is preserved however during installation dib-run-parts becomes a file containing the contents of the symlink target. Related-Bug: #1212482 Change-Id: I78c28a52689810a2ccfc9925a9ac8df017c44326
2013-08-06 02:30:56 +00:00
Use dib-run-parts from dib-utils Now that dib-run-parts has been moved to the dib-utils project, we need to update diskimage-builder to use it instead of the version directly in diskimage-builder. This change removes the old copy of the dib-run-parts script in the element, adds dib-utils as a dependency of diskimage-builder, and updates the uses of dib-run-parts to correctly handle the fact that it is now external to the project. Requires I0be1f876d0e4a7d38e0d5c6010a552a8ebb158a4 Change-Id: Ia0a0df7784a14c49b5c47ac0b03e6c2602c84b3b
2014-06-14 00:38:16 +00:00
# ramdisk-image-create is a symlink which becomes a
# real file on install; see lp bug #1212482
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
scripts =
Add dib-lint script This will provide a place to put checks that catch common errors in elements. To start, this just checks that files starting with a shebang are chmod +x so they can actually be run. Change-Id: I4116a8f38f7bdfc5866764354c459fad8ca18e92
2014-03-20 01:56:27 +00:00
bin/dib-lint
Package with pbr. Uses pbr-0.5.20 glob support to install elements, lib and scripts. Change-Id: Ie466e753f6e75a943ced1a2939c9bb27aec4a6b0
2013-07-07 23:54:40 +00:00
data_files =
share/diskimage-builder/scripts = scripts/*
Refactor: block-device handling (local loop) Block device handling can be somewhat complex - especially when taking things like md, lvm or encryption into account. This patch factors out the creation and deletion of the local loop image device handling into a python library. The main propose of this patch is to implement the needed infrastructure. Based on this, more advanced functions can be added. Example: (advanced) partitioning, LVM, handling different boot scenarios (BIOS, UEFI, ...), possibility of handling multiple images (local loop image, iSCSI, physical hard disk, ...), handling of different filesystems for different partitions / LVs. Change-Id: Ib626b36a00f8a5dc3dbde8df3e2619a2438eaaf1 Signed-off-by: Andreas Florath <andreas@florath.net>
2016-05-21 19:32:35 +00:00
[entry_points]
console_scripts =
Move diskimage-image-create to an entry point It has always been a weird thing that dib is a python package, but is totally driven by the disk-image-create script. It creates this strange division that is hard to explain. This moves disk-image-create to a regular python entry-point Currently, this simply exec()s the original disk-image-create script. However, we now have a (private) interface between disk-image-create written in python and the driver shell script. Here's some things we could do, for example: * Argument parsing is generally nicer in Python, and then end result is mostly just setting environment variables to flag different things in the shell script. I could see us moving the argument-parsing into diskimage_builder.disk_image_create:main() and just setting things in os.environ before the exec()). * I7092e1845942f249175933d67ab121188f3511fd sets IMAGE_ELEMENT_YAML in disk-image-create by calling-back to element-info. We can just call element_dependencies.find_all_elements() in here an export is to os.environ before disk-image-create starts. * remove need for ramdisk-image-create symlink by just exporting IS_RAMDISK based on sys.argv[1] value * you could even unit test some of this :) Change-Id: I69ca3d26fede0506a6353c077c69f735c8d84d28
2016-07-20 01:48:32 +00:00
disk-image-create = diskimage_builder.disk_image_create:main
ramdisk-image-create = diskimage_builder.disk_image_create:main
A new diskimage-builder command for yaml image builds The `diskimage-builder` command provides a yaml file based interface to `disk-image-create` and `ramdisk-image-create`. Every argument to these scripts has a YAML equivalent. The command has the following features: - Environment values can be provided from the calling environment as well as YAML - All arguments are validated with jsonschema in the most appropriate YAML type - Schema is self-documenting and printed when running with --help - Multiple YAML files can be specified and each file can have multiple images defined - Entries with duplicate image names will be merged into a single image build, with attributes overwritten, elements appended, and environment values updated/overwritten. A missing image name implies the same image name as the previous entry. - --dry-run and --stop-on-failure flags A simple YAML defintion would resemble: - imagename: centos-minimal checksum: true install-type: package elements: [centos, vm] - imagename: ironic-python-agent elements: - ironic-python-agent-ramdisk - extra-hardware The TripleO project has managed image build options with YAML files and it has proved useful having git history and a diff friendly format, specifically for the following situations: - Managing differences between distros (centos, rhel) - Managing changes in major distro releases (centos-8, centos-9-stream) - Managing the python2 to python3 transition, within and across major distro releases Now that the TripleO toolchain is being retired this tool is being proposed to be used for the image builds of TripleO's successor, as well as the rest of the community. Subsequent commits will add documentation and switch some tests to using `diskimage-builder`. Change-Id: I95cba3530d1b1c6c52cf547338762e33738f7225
2023-03-03 02:34:25 +00:00
diskimage-builder = diskimage_builder.diskimage_builder:main
Use stevedore for plugin config of block device This patch introduces stevedore plugin mechanism for use with the block device layer. This makes it possible that other projects pass in their own block device plugins. Change-Id: Id3ea56aaf75f5a20a4e1b6ac2a68adb12c56b574 Signed-off-by: Andreas Florath <andreas@florath.net>
2017-03-17 18:10:04 +00:00
diskimage_builder.block_device.plugin =
local_loop = diskimage_builder.block_device.level0.localloop:LocalLoop
partitioning = diskimage_builder.block_device.level1.partitioning:Partitioning
LVM support for dib-block-device This provides a basic LVM support to dib-block-device. Co-Authored-By: Ian Wienand <iwienand@redhat.com> Change-Id: Ibd624d9f95ee68b20a15891f639ddd5b3188cdf9
2017-06-08 05:02:18 +00:00
lvm = diskimage_builder.block_device.level1.lvm:LVMPlugin
Refactor: block-device filesystem creation, mount and fstab This patch finalizes the block device refactoring. It moves the three remaining levels (filesystem creation, mount and fstab handling) into the new python module. Now it is possible to use any number of disk images, any number of partitions and used them mounted to different directories. Notes: * unmount_dir : modified to only unmount the subdirs mounted by mount_proc_sys_dev(). dib-block-device unmounts $TMP_MOUNT_PATH/mnt (see I85e01f3898d3c043071de5fad82307cb091a64a9) Change-Id: I592c0b1329409307197460cfa8fd69798013f1f8 Signed-off-by: Andreas Florath <andreas@florath.net> Closes-Bug: #1664924
2017-01-29 23:52:40 +00:00
mkfs = diskimage_builder.block_device.level2.mkfs:Mkfs
mount = diskimage_builder.block_device.level3.mount:Mount
fstab = diskimage_builder.block_device.level4.fstab:Fstab
Add state object, rename "results", add unit tests A couple of things going on, but I think it makes sense to do them atomically. The NodeBase.create() argument "results" is the global state dictionary that will be saved to "state.json", and re-loaded in later phases and passed to them as the argument "state". So for consistency, call this argument "state" (this fits with the change out to start building the state dictionary earlier in the PluginBase.__init__() calls). Since the "state" is a pretty important part of how everything works, move it into a separate object. This is treated as essentially a singleton. It bundles it nicely together for some added documentation [1]. We move instantiation of this object out of the generic BlockDevice.__init__() call and into the actual cmd_* drivers. This is because there's two distinct instantiation operations -- creating a new state (during cmd_create) and loading an existing state (other cmd_*). This is also safer -- since we know the cmd_* arguments are looking for an existing state.json, we will fail if it somehow goes missing. To more fully unit test this, some testing plugins and new entry-points are added. These add known state values which we check for. These should be a good basis for further tests. [1] as noted, we could probably do some fun things in the future like make this implement a dictionary and have some saftey features like r/o keys. Change-Id: I90eb711b3e9b1ce139eb34bdf3cde641fd06828f
2017-05-30 02:06:41 +00:00
# unit test extensions
diskimage_builder.block_device.plugin_test =
test_a = diskimage_builder.block_device.tests.plugin.test_a:TestA
test_b = diskimage_builder.block_device.tests.plugin.test_b:TestB