openstack/kolla.git/docker/bifrost, branch stable/2025.2

Remove special handling for python3.12

2026-02-10T12:25:03+00:00

This is not required anymore since we have switched to Rocky Linux 10. Change-Id: I10b68c2d3afa91cabf9341df75d8cf9f626c0f9b Signed-off-by: Pierre Riteau (cherry picked from commit 64475a0b1b4dccbc3b817c78453e1d027b3f0d68)

Bump Ansible to 12 and ansible-core to 2.19

2025-10-28T10:45:51+00:00

Change-Id: I37f4515587cb040296612e35d4c643f0c2bea6f6 Signed-off-by: Michal Nasiadka

Move repo enablement to respective rpm blocks

2025-10-02T08:37:07+00:00

Currently we are enabling repos irrespective of rpm/deb statement blocks and not failing in the method used if a repository is missing. Downside is - we might be producing one more layer, but it probably is a more logical approach. This is required for adding rpm support in repos.yaml that will also include failing on missing repositories. Change-Id: I5479c5c935760f00fe4cd307366f261deee3199f Signed-off-by: Michal Nasiadka

Drop ironic-inspector

2025-09-05T07:23:23+00:00

Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/951864 Change-Id: Ie7e607c5a9c6f8c2e36aea5d52dc2ffbe97dddb3 Signed-off-by: Michal Nasiadka

bifrost: fix creation of python3 lib symlink

2025-05-02T18:11:38+00:00

When {{ venv_path }}/lib/python3 already exist and we run the ln command, we end up with: /var/lib/kolla/venv/lib/ ├── python3 -> python3.9 ├── python3.12 │ └── site-packages └── python3.9 ├── python3.12 -> python3.12 └── site-packages Instead, it should be: /var/lib/kolla/venv/lib/ ├── python3 -> python3.12 ├── python3.12 │ └── site-packages └── python3.9 └── site-packages Remove the existing link first to ensure it is created properly. Change-Id: I42dd2490d14070074fe1fa7ae9e0a4cbf095b06f

Merge "bifrost: bump Ansible version to 11"

2025-04-04T01:06:22+00:00

bifrost: bump Ansible version to 11

2025-04-02T08:30:46+00:00

Depends-on: https://review.opendev.org/c/openstack/kolla-ansible/+/945498 Change-Id: I0e7ce418508f6684a20539c6b6129a134f91c71c

Merge "Change Bifrost Python upper-constraints source"

2025-03-27T13:12:48+00:00

Change Bifrost Python upper-constraints source

2025-02-05T15:36:52+00:00

Users can override the upper-constraints.txt by setting the source of openstack-base in kolla-build.conf. However, bifrost-base Dockerfile so far doesn't pass overridden upper-constraints file to Bifrost install playbook resulting the playbook not acknowledging it and just use upstream one. This change sets the source of Bifrost upper-constraints to use upper-constraints of openstack-base for consistency among all Kolla images With this, change the environment variable UPPER_CONSTRAINTS_FILE is only affecting kolla-toolbox image. Therefore, moved UPPER_CONSTRATINS_FILE variable example to the ``kolla_toolbox_pip_conf`` block of kolla-toolbox Dockerfile. Additionally, updated 'Python packages build options' section of documentation to represent latest method of changing Python package related options (including this change). Change-Id: I0a9c782ca1177ef84e4323cb1e5bfac0fb3f383c

Add mechanism for patching files in containers

2024-11-15T08:04:30+00:00

This patch adds a way to patch files in a Docker image built by Kolla. This is very useful for several reasons, specifically: - Custom modifications - The stable branch of some library has a fix but no pip package has been released - Eliminates the need to package your own pip packages - Eliminates the need to invent your own versioning to prevent upstream versioning - Eliminates the need to manage a pip server - In other words, it eliminates the need to get a wheel into the image and install it manually using any method not previously mentioned It is also highly desirable because, although Kolla can replace the source for a service with a custom URL for a tarball or its own Git repo, it cannot do this for dependencies pulled from pip. I would also like to point out that this is a feature with its own code path and works only if the user "inserts" a patch into the folder patches/docker-image/something.patch and creates an analogous series file for patch source code. Simply said, this code will never interfere with the upstream build process since this feature is not intended for use in upstream. It is rather meant for downstream users who know what they are doing. Now they just have an option to patch their images. Everything works on all layers of the Docker image and stores a report of applied patches which can then be seen in /etc. This mechanism is similar as debian patch quilt. Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d