Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2025-12-03T11:06:34+00:00 2025-12-03T11:06:34+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-12-03T09:31:30+00:00 urn:sha1:2da1676d7a861ff921936443861559f1b994f776 We switched to Valkey Change-Id: Ic40fecb87dd3eaf67eb1d3088978d462ff5b4320 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 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-11T15:22:24+00:00 Tim Shearer tshearer@advaoptical.com 2022-04-01T20:22:28+00:00 urn:sha1:1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae Explicitly set the permissions on the kolla-toolbox kolla_extend_start file. Also, since all extend_start files are sourced rather than executed, the executable bits are now cleared throughout the project. Change-Id: I5c2deb4a2e33575d57c852089f856a9acc6818d0 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 2017-07-24T13:29:20+00:00 Mathias Ewald mewald@evoila.de 2017-07-21T11:04:43+00:00 urn:sha1:4f903087e64adebe962615dadfa1f96cb6241528 Introduce base container for redis Rebase the existing redis container on the new base container Provide a container for redis-sentinel to create a highly available cluster Change-Id: I683f02930a870c01dbc71c84060a65c72a8e568e