| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.
Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.
Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Set bifrost internal_ip variable to adapt to change [1].
[1]: https://review.opendev.org/#/c/748230/
Change-Id: Idf401536b482b4088f5fb66408917752fd71726c
|
|
By default, the Bifrost Ansible playbooks will naturally run
everything against /usr/bin/python which means that some modules,
such as Shade when it has to be installed will use the system
Python installation.
By adding `ansible_python_interpreter` and pointing it towards
our Python interpreter, it fixes the failures related to system
Python and conflicts related to it (which in this case, resulted
in Shade failing to build properly).
Closes-Bug: #1673776
Change-Id: I2a5a2a3e2627a313b3306aeb1a910efe0e209496
|
|
TrivialFix
Change-Id: Id2cd736f136068514f26977b434b15a8b1ffc8be
|
|
- This change adds support for building and deploying
a bifrost container for baremetal provisioning.
- This change documents how to manually deploy and bootstrap
the bifrost container.
Implements: blueprint bifrost-support
Change-Id: I7d895839b11cbf916be33225875465c3358b5aa4
|
