Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2026-07-06T19:59:40+00:00 2026-07-06T19:59:40+00:00 Michal Nasiadka mnasiadka@gmail.com 2026-07-06T13:26:00+00:00 urn:sha1:db35ac8d793506bc43b62e7e39d27a75de1043ed [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> 2026-06-24T13:00:26+00:00 Michal Nasiadka mnasiadka@gmail.com 2026-06-18T15:16:08+00:00 urn:sha1:a1a3fdc1b54baf62f234ddc9dac4906e30eb5d11 The build-date label was rendered into a LABEL instruction on line 3 of every Dockerfile template, immediately after FROM. Because Docker invalidates the cache for a changed instruction and all subsequent layers, a date change caused a full rebuild of every image on each new calendar day, even when nothing else had changed. Fix this by removing build-date from the Dockerfile templates and applying it as a --label argument at build time via image.labels. Labels passed on the build command line are not part of the Dockerfile cache key, so the date is still recorded in the image metadata without affecting layer caching. Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2025-10-02T08:37:07+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-10-01T08:57:21+00:00 urn:sha1:17727e148120c43a5c7056b33e4277592376ccca 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 <mnasiadka@gmail.com> 2025-03-20T12:34:16+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-12-30T13:50:46+00:00 urn:sha1:7a0c639da31a913edb52e877fc950a928994441c It probably has been omitted in Ubuntu 24.04 introduction since aarch64 build jobs have not been stable. Removing from nova-compute since it's already in nova-base, nova-libvirt's parent is base - so updating to qemu-efi-aarch64 Change-Id: Idae2e87bfc8a556a090085e46f96d11279080f0f 2024-11-15T08:04:30+00:00 Michal Arbet michal.arbet@ultimum.io 2022-02-15T12:50:59+00:00 urn:sha1:11f65c6c1d3bfd6a12f8e71d778d46d635010449 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 2024-10-22T07:15:14+00:00 Rafal Lewandowski rafal@stackhpc.com 2024-10-10T10:17:00+00:00 urn:sha1:757cf4c14723a598ef827c3dc83aec6c3ca05324 Closes-Bug: #2067050 Change-Id: Ife426c073048ff27bdfd9f3af30aaaab8c2e4497 2024-04-29T09:44:25+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-04-29T09:41:43+00:00 urn:sha1:de7939a9754cffafb77b518f9efa8be5af91d67f openvswitch package is already installed in nova-base from CentOS NFV SIG repos - and in nova-compute we don't enable this repo - so we get openvswitch installed from RDO packages. Closes-Bug: #2064098 Change-Id: If39e045357563111219a008fa7a81a82ef906627 2024-04-22T11:03:38+00:00 Michal Wyszkowski michal.wyszkowski99@gmail.com 2024-04-22T11:03:38+00:00 urn:sha1:abb969502f75517844bd44c25e0484c7495284d2 Closes-Bug: 2062572 Change-Id: I456a5b8f66aa88a82fb54938e8df7195d127d9cd 2024-02-26T12:04:19+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-02-26T11:58:43+00:00 urn:sha1:66e27b3b0a60a5aa0122228210329889d914487f It does not exist in repos.yaml since [1]. [1]: Id585c7744ba130ad1dfc28138fb0f9e6eeae771d Change-Id: Ic74eba44fc6e5508976de24cf20a5039f3292731 2023-11-22T10:06:39+00:00 Pierre Riteau pierre@stackhpc.com 2023-11-22T05:52:05+00:00 urn:sha1:33c988a6ce9fc3fe86d32d0bb97f6cb5130bf2f2 Since change I1bc19f8198da3f9ab2ae2a8864c3349b21b0249e we install the centos-release-ceph-reef package as a dependency, but some code was still expecting the quincy package. Change-Id: I8ebcf815d80f3bead25e0078d69b34e17ad013bd