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

82 lines
2.4 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.
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
[Core] Change openstack-dev to openstack-discuss. The openstack-dev address is replaces by openstack-discuss. Change-Id: Iba766d86db3c3f98a52e8dd17b61ac16083d2333
2018-12-05 08:52:01 +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)
Update the documentation link for doc migration The documentation has moved due to the docs manuals migration effort. See [1] [1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html Change-Id: I16fac4a1caea5e4b8c7e2d5adcb93d8a6535e65d
2017-07-14 05:51:23 +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
Programming Language :: Python :: 2.7
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
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
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
[build_sphinx]
all_files = 1
build-dir = doc/build
source-dir = doc/source
Use sphinx warning-is-error Sphix 1.5 (I9e7261c4124b71eeb6bddd9e21747b61bbdc16fa) includes "warning-is-error" which supersedes pbr's warnerrors. Enable this and fix up the resulting failures - trailing lines for lists in element_deps directive - missing README's that are linked - syntax error and highlighting in building instructions Change-Id: I6549551b4a9bf47076c9811a7a38a666cbea2a50
2017-03-14 00:33:01 +00:00
warning-is-error = 1
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
Produce API documentation There's an increasing amount of pydoc based documentation. Output the module reference and link it into the developers main page. One fixup to the rst needed Change-Id: I1d43a1fe1c735eb4559e3d2b40834d1c8115c586
2017-05-25 04:13:31 +00:00
[pbr]
autodoc_index_modules = 1
autodoc_exclude_modules =
setup.py
diskimage_builder.tests.*
diskimage_builder.block_device.tests.*
# elements are a weird mix of scripts & python
diskimage_builder.elements.*
Add timestamp output filter This adds a devstack-inspired output filter to standardise timestamping. Currently, python tools timestamp always (timestamp setup in logging_config.py) but all the surrounding bash does not. We have extra timestamps added in run_functests.sh for our own purposes to get the bash timestamps; but this ends up giving us double-timestamps for the python bits. Additionally, callers such as nodepool capture our output and put their own timestamps on it, and again have the double-timestamps. This uses a lightly modified outfilter.py from devstack to standardise this. All output is run through this filter, which will timestamp it. I have removed the places where we double-timestamp -- logging_config.py and the prefix in dib-run-parts. An env option is added to turn timestamps off completely (does not seem worth taking up a command-line option for). For callers like nodepool, they can set this and will just have their own timestamps as they collect the lines. Since all logging is going through outfilter, it's easy to add a --logfile option. I think this will be quite handy; personally I'm always redirecting dib runs to files for debugging. I've also added a "quiet" option. I think this could be useful in run_tests.sh if we were to start logging the output of each test to individual files. This would be much easier to deal with than the very large log files we get (especially if we wanted to turn on parallel running...) Change-Id: I202e1cb200bde17f6d7770cf1e2710bbf4cca64c
2017-06-16 02:09:24 +00:00
# this is non-pythony stuff
diskimage_builder.lib.*
Produce API documentation There's an increasing amount of pydoc based documentation. Output the module reference and link it into the developers main page. One fixup to the rst needed Change-Id: I1d43a1fe1c735eb4559e3d2b40834d1c8115c586
2017-05-25 04:13:31 +00:00
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/*
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[extract_messages]
keywords = _ gettext ngettext l_ lazy_gettext
mapping_file = babel.cfg
output_file = diskimage_builder/locale/diskimage_builder.pot
[update_catalog]
domain = diskimage_builder
output_dir = diskimage_builder/locale
input_file = diskimage_builder/locale/diskimage_builder.pot
[compile_catalog]
directory = diskimage_builder/locale
domain = diskimage_builder
Support building wheels (PEP-427) With that, building and uploading wheels to PyPI is only one "python setup.py bdist_wheel" away. Change-Id: Ia3b572d44e150911622e5f00592944099b11a95d
2013-11-19 09:22:19 +00:00
[wheel]
universal = 1
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 element-info to a standard entry-point Move element-info from a wrapper script to a standard entry-point console_script. Update the documentation to explain how to run it for development. I don't think we should support the idea that you can check-out the code and run ./bin/disk-image-create -- it has dependencies (dib-utils, etc) and needs to be run from a virtualenv (this is what CI in the gate does). A follow-up can clean-up some of the path munging stuff we have for this in disk-image-create. Change-Id: Ic0c03995667f320a27ac30441279f3e6abb6bca8
2016-06-17 05:45:20 +00:00
element-info = diskimage_builder.element_dependencies:main
Move dib-block-device implementation into cmd.py Move the command-line driver components into cmd.py. No functional change. Change-Id: I1919f6e865acae14ee95cd025c9c7b75ca266a9c
2017-05-02 01:52:21 +00:00
dib-block-device = diskimage_builder.block_device.cmd:main
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
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
Reference in New Issue Copy Permalink