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> 2024-12-13T19:13:08+00:00 Dawud dawud@stackhpc.com 2024-12-13T19:13:08+00:00 urn:sha1:3575d7d8bd14feef50e3e1222557a6a07158fdd4 Change-Id: Id81ce23fed7c19211aa8b15abce185d990be8389 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-06-28T00:19:10+00:00 Dawud dawud@stackhpc.com 2024-03-14T13:21:57+00:00 urn:sha1:077e0003d41746a0052564ee1487d981f125cec9 Co-authored-by: Will Szumski <will@stackhpc.com> Change-Id: I2b1c95395aeefb2ccb1d8edf415eee0f98c52190 2023-08-21T16:26:10+00:00 Dawud dawud@stackhpc.com 2023-08-21T16:20:50+00:00 urn:sha1:a97a561bab1573b0ed19d91f827a8bbde9ed8165 The grafana opensearch datasource was missing from the docker image. This commit installs the datasource plugin. Change-Id: Ia3a39c975abf815a66765f2f98c4789d6cec33d7 2023-01-18T06:39:30+00:00 Michal Nasiadka mnasiadka@gmail.com 2023-01-02T11:14:12+00:00 urn:sha1:47a9a818596b27f658fb7b40aac2130fd04b66b6 Change-Id: I08fe2827bc58baa95d396daf28de1079e3df4f77 2022-12-06T12:58:10+00:00 Michal Nasiadka mnasiadka@gmail.com 2022-12-05T14:10:50+00:00 urn:sha1:52a53927f5d390886c3940e364fe9fa888e3bc98 Monasca, kafka, storm and zookeeper have been removed in kolla-ansible [1],[2]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392 [2]: https://review.opendev.org/c/openstack/kolla-ansible/+/865029 Change-Id: I0958a9353bc4585c4f65a1d316328a0e80b0b8b7 2022-09-27T08:17:15+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-09-21T14:28:56+00:00 urn:sha1:542bbcdb6b2827812e529c29f4a44f542ec1f801 RHEL 9 refuses to use SHA1 gpg keys. Grafana team still did not handled key upgrade: https://github.com/grafana/grafana/issues/41036 Change-Id: Id963271103ce1397b7a5498d032e8f797edfcc70 2022-04-21T18:53:25+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-21T16:08:36+00:00 urn:sha1:86361d0831821830d075474b55fff705ed95c63f Kolla supports only AArch64 and x86-64 so there is no need to check for other architectures. Change-Id: I44e45492bcbdd56a5c985ba84bad66202c9fde55