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-08-29T07:19:33+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-04-30T06:45:56+00:00 urn:sha1:5781b359efc32726645a7d5d5570bcec9f0035fa 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 <mnasiadka@gmail.com> 2025-06-27T05:48:23+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-06-13T10:11:56+00:00 urn:sha1:5121ff7679f416844ef74774c825b6be1382c74b ovn is running as root, and fluentd can't read it's log files, so we need to precreate these. Closes-Bug: #2115244 Change-Id: Icb0e47cf95a67cb4585c71f863e542bc59ff5009 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 2022-04-11T06:22:21+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-08T10:38:13+00:00 urn:sha1:a1510870e86f9cde6537ac2cbbfb055337843c90 We have one install_type only now so that infra stuff is not needed anymore. Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262 2020-07-09T21:31:42+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2020-07-07T11:02:49+00:00 urn:sha1:90adc2b851461828b5051be373640911c795fc5a Defaults to 'image_prefix' for now but shows which images gets their names changed soon. Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503 2020-03-01T17:25:58+00:00 Christian Berendt berendt@betacloud-solutions.de 2020-02-19T21:39:33+00:00 urn:sha1:861f55fbfd7558d56008e6275b0c6f5993346b95 Change-Id: I9692dda817ef134d647247431565e1b58cf9da41 2019-11-14T10:58:45+00:00 Numan Siddique nusiddiq@redhat.com 2019-10-27T07:05:47+00:00 urn:sha1:b8c8fa15edcf5336a1121155cdc880a35ccf161f Using the ovn-ctl script to start the OVN ovsdb-server is the better way. This script is used to start and stop all OVN systemd services. This script takes care of creating the database from the schema, updating the database from the schema when the schema version gets updated. The present scripts - start_nb_db_server.sh and start_sb_db_server.sh doesn't take care of schema updates. With this, we don't need extend_start.sh in ovn-nb-db-server/ovn-sb-db-server to create the database from the schema. This patch also deletes kolla_ovn_extend_start from the ovn-base image as it is not required. Closes-bug: 1850025 Change-Id: I31a372d801dace92950cd85b29b308431f78bbdb 2019-01-17T15:23:41+00:00 Alex Schultz aschultz@redhat.com 2019-01-15T23:58:25+00:00 urn:sha1:ae1322ec10861678abe1137f3013030b34335bc7 This change updates the docker files to use base_package_type instead of doing specific distro checks for the rhel/deb generic cases. The base_distro is still available and is used when a specific distro needs a customization but if the differences are purely rpm vs deb, then the base_package_type can be used. Change-Id: I8d720bb185df65a0178061ccf20b1ab2265da2c5