diskimage-builder/requirements.txt

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.

networkx>=2.3.0 # BSD
pbr!=2.1.0,>=2.0.0 # Apache-2.0
PyYAML>=3.12 # MIT
stevedore>=1.20.0 # Apache-2.0
# NOTE(ianw) in here because dib-lint uses flake8
flake8<6.0.0,>=3.6.0 # MIT
jsonschema>=3.2.0 # MIT
Updated from global requirements Change-Id: Ie2bb534b456ed3aac79b706cf51ecee9789527e4 2014-09-23 01:55:13 +00:00			`# The order of packages is significant, because pip processes them in the order`
			`# of appearance. Changing the order has an impact on the overall integration`
			`# process, which may cause wedges in the gate later.`
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
Drop lower version requirement for networkx With [1] to fix lower constraints job, networkx requirement was bumped to 2.4.0, but since diskimage-builder is branchless and to get it work with stable/train upper-constraints for networkx i.e 2.3.0 can't bump to 2.4.0. Also networkx-2.3.0 has dep on decorator>=4.3.0 so actual decorator issue with 3.4.0 shouldn't be there. [1] https://review.opendev.org/c/openstack/diskimage-builder/+/811048 [2] https://github.com/networkx/networkx/blob/networkx-2.3/requirements/default.txt Closes-Bug: #1945926 Change-Id: I93a2826019d9bb0d004f7daa661fdd1ca4269331 2021-10-05 07:18:27 +00:00			`networkx>=2.3.0 # BSD`
Updated from global requirements Change-Id: I09b47aa75008bfd832ec8eec9108501f18223875 2017-04-12 04:10:50 +00:00			`pbr!=2.1.0,>=2.0.0 # Apache-2.0`
Updated from global requirements Change-Id: Idf7fa1936a9ee0fc6c3569f8c399f2039cd873a9 2018-03-04 10:01:45 +00:00			`PyYAML>=3.12 # MIT`
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			`stevedore>=1.20.0 # Apache-2.0`
Revert "dib-lint: use yamllint to parse YAML files" This reverts commit 6ee2995214ee5512c64244ce0ccc7fda639c2d36 and e85c2a6f035a016f80de3d5aebc026f28dfb6bc1. I missed that if you pip install and then run dib-lint, it's not going to pick up the .yamllint file shipped here. Thus it gives spurious errors. The reason for this was simply better duplicate key detection in yaml files, which caused us problems with the kernel installs. However, at this point it seems just the old "does it load" test from pyyaml will be enough. Change-Id: I87a9fc9bb119cfeffad48fc0fa0df31f0181825d 2020-05-28 06:41:01 +00:00			`# NOTE(ianw) in here because dib-lint uses flake8`
Allow flake8 version 5 This change enables using the latest flake8. Change-Id: Iaa19c36f8cab8482a01f764c588375db8e7d8be3 2022-08-25 18:28:22 +00:00			`flake8<6.0.0,>=3.6.0 # MIT`
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			`jsonschema>=3.2.0 # MIT`