openstack/kolla.git/docker/openvswitch/openvswitch-base, branch stable/2026.1

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

Remove RDO/Delorean

2025-08-29T07:19:33+00:00

RDO has staffing problems and has decided to only support SLURP releases - let's drop reliance on that repository. Change-Id: I56f86a1c5262e3ee2bcbb52cae53c3b2655ed87f Signed-off-by: Michal Nasiadka

openvswitch: Fix logs dir permission

2025-01-13T15:21:16+00:00

Closes-Bug: #1795609 Change-Id: Iedfb2df027c0cefc45668a76d45ce62193aba9ef

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

openvswitch: Add ovs_wrapper for handling TERM

2024-03-23T15:10:16+00:00

Partial-Bug: #2048130 Change-Id: I81eba2644eda6edd38c541f798bead04c2fa6578

Adjust permissions on _extend_start files.

2022-04-11T15:22:24+00:00

Explicitly set the permissions on the kolla-toolbox kolla_extend_start file. Also, since all extend_start files are sourced rather than executed, the executable bits are now cleared throughout the project. Change-Id: I5c2deb4a2e33575d57c852089f856a9acc6818d0

drop infra_image_prefix

2022-04-11T06:22:21+00:00

We have one install_type only now so that infra stuff is not needed anymore. Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262

move to Debian 'bullseye'

2021-04-26T18:01:28+00:00

Bullseye is now in hard freeze cycle and goes for release. https://release.debian.org/bullseye/freeze_policy.html Co-Authored-By: Michal Nasiadka Change-Id: I543965a2741cebfa759576a4c75669a7bacd4208

centos: enable repos where needed

2021-04-13T11:21:39+00:00

With RDO use we did not disabled some repositories. This patch disable them and enable where needed. Change-Id: Ia9d537fe9c1ad54789d2bfb4027254fbb3defe7e

introduce 'infra_image_prefix' for infra images

2020-07-09T21:31:42+00:00

Defaults to 'image_prefix' for now but shows which images gets their names changed soon. Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503