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-03-24T12:37:43+00:00 Piotr Milewski vurmil@gmail.com 2025-02-12T12:53:14+00:00 urn:sha1:47a6ad020d7a52b14106938e03e27d65280999cb When building an image, the RUN command grants permissions which causes the previous layer to be copied. During the test, the image was reduced from 2.84GB to 1.57GB Closes-Bug: #2104007 Change-Id: I7d2367d4c277287f4db2885f5720a35d934f94b7 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-09-27T09:11:28+00:00 Bartosz Bezak bartosz@stackhpc.com 2024-09-27T09:11:28+00:00 urn:sha1:c862b076f71643bd9062ed6f8131e0570edfd441 This reverts commit 3c49991a86cb26dd0447fa748d1df9df5aed92bb. Reason for revert: bug fixed upstream https://github.com/opensearch-project/OpenSearch-Dashboards/pull/8097 Change-Id: Icc810554dc877c9dedaf26609d59a93059a38ba7 2024-08-21T08:53:28+00:00 Mark Goddard mark@stackhpc.com 2024-08-19T10:29:06+00:00 urn:sha1:3c49991a86cb26dd0447fa748d1df9df5aed92bb OpenSearch Dashboards 2.16.0 discover page hangs after initial deployment due to an upstream bug [1]. This change fixes the issue by pinning OpenSearch Dashboards to 2.15. Note that it seemed safer not to pin OpenSearch to fix this issue, to avoid breaking deployments that have already deployed 2.16. [1] https://github.com/opensearch-project/OpenSearch-Dashboards/issues/7626 Closes-Bug: #2077319 Change-Id: I0de9928b2657ab5f31580325e866bff28f2b5510 2024-04-16T18:33:55+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-04-16T18:33:43+00:00 urn:sha1:340350a387cbbe417eff9385156d665c3edd683d This reverts commit 19a004e0a500ea4839fa1e089e1c50c953cec3b3. Reason for revert: Fixed Change-Id: I5491adef46fe0cec013a597cb05018d8d7e862f0 2024-04-16T18:05:03+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-04-16T11:10:47+00:00 urn:sha1:7c098bdd3cac73505851d4c97d7f39e966f00e1b Since 2.13 OpenSearch and OpenSearch-Dashboards packages install files in /usr/share/opensearch and /usr/share/opensearch-dashboards with root:root ownership instead of using opensearch/opensearch-dashboards user. Closes-Bug: #2061877 Change-Id: I3831d8ab76c8c7136ce7869db3d0d1e05b4ba8f8 2024-04-12T13:51:05+00:00 Sven Kieske kieske@osism.tech 2024-04-09T12:11:54+00:00 urn:sha1:19a004e0a500ea4839fa1e089e1c50c953cec3b3 pin opensearch and opensearch-dashboards to 2.12. for now Closes-Bug: #2060668 Related-Bug: #2060306 Change-Id: I3df4823d78474d94e138ff73f0f577bd247bdad0 Signed-off-by: Sven Kieske <kieske@osism.tech> 2023-06-23T10:08:50+00:00 Michal Nasiadka mnasiadka@gmail.com 2023-06-20T13:20:38+00:00 urn:sha1:b33167972d6e17b2eaab85e72043e3b4efa4b789 Change-Id: Id6db7ffb22b3f63e9a406455d52078b76071672f