| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
The Everpure FlashArray Cinder driver imports the py-pure-client SDK,
which kolla-ansible's native enable_cinder_backend_pure_* flags assume
is present. Stock images do not carry it, so operators have to rebuild
cinder-volume themselves. Baking the SDK in is not an option: it
installs to roughly 700 MB of generated REST models, far too much to
add to every cinder-volume image for one backend.
Instead give cinder-volume its own pip package list, empty by default
and run through the customizable filter, so a vendor SDK can be added
with a single template-override line:
{% set cinder_volume_pip_packages_append = ['py-pure-client'] %}
without touching cinder-base and therefore the API, scheduler and
backup images. This is the mechanism nova-compute and ironic-conductor
already expose for their optional packages.
Related-Bug: #2170385
Assisted-By: Claude Code claude-fable-5-1
Change-Id: If8202b9f04f0299183019891e4ddd636669b25b4
Signed-off-by: Simon Dodsley <simon@purestorage.com>
|
|
Change-Id: Iaddda80bc78bf727d8a2835d1528f49639aa87a0
Signed-off-by: Michal Arbet <michal.arbet@ultimum.io>
|
|
Repos marked build_only: true are backed up before handle_repos()
overwrites them and restored at the end of each image build, so CI
mirror URLs are not baked into the final image.
The cleanup RUN was injected into every Dockerfile, not just images
that called handle_repos() for those repos. Child images with no
backup fell through to "rm -f", deleting the inherited repo file
(e.g. debian.sources in bifrost-base, breaking cpio install).
Fix by adding a {repo}.enabled sentinel that handle_repos creates
when it processes a build_only repo, making the cleanup conditional
on that sentinel.
Change-Id: Ie5b9970a4575b6258dc238059d3f33ddfe155789
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
[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>
|
