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> 2026-03-17T09:33:01+00:00 Piotr Milewski vurmil@gmail.com 2025-11-04T09:55:19+00:00 urn:sha1:1b14eb8df7f1a34edd41e945df33ffb8f1c56b79 Change-Id: Id6684e4356f68e4348c0f8c1c0c1e5397553397e Signed-off-by: Piotr Milewski <vurmil@gmail.com> Signed-off-by: Bartosz Bezak <bartosz@stackhpc.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-07-04T10:32:41+00:00 Bartosz Bezak bartosz@stackhpc.com 2025-06-30T12:40:54+00:00 urn:sha1:512d8928c4c82ec54619da74716765e0544cc665 Previous apt preference missed the epoch and sub-packages, so no pinning was applied. Closes-Bug: #2115893 Change-Id: I5c765db0508a2ffec90ba149bb5ea9b90dd31bc8 Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com> 2025-06-11T13:25:39+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-06-11T08:50:28+00:00 urn:sha1:bbe23bd107c16d4990b26e9aca5eb888f98cc781 We've seen multiple occassions of all these healthcheck commands not being able to be executed in 30s after the switch to RMQ 4.1. Let's put more information in the Docker/Podman healthcheck logs. Change-Id: I4b1b54983144f5514a6703c255d2cb4fa052a0fb 2025-05-20T11:50:52+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-05-20T11:49:02+00:00 urn:sha1:c9b665fa8a1ba38f6798349019714ae174b9b85b Change-Id: I4f852176918531ea19210961fd1b4fa63bc0ecca 2025-04-11T08:35:39+00:00 Zuul zuul@review.opendev.org 2025-04-11T08:35:39+00:00 urn:sha1:a0af54161e1734ab150dd5d7aea22947eadf0b91 2025-04-10T14:52:45+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-11-12T12:58:33+00:00 urn:sha1:74843405decb2a22abc9dfb8f4fe0aa524312e51 Change-Id: If15ba52acfd305aa9bbae382fe7429c11041e93f 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