Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2 2024-11-15T08:04:30+00:00 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 2023-01-31T06:41:29+00:00 Michal Nasiadka mnasiadka@gmail.com 2023-01-31T06:41:01+00:00 urn:sha1:f7436ee60256687a71a3a89fac2e15b61e9e4859 Closes-Bug: #1980328 Change-Id: I29dde2696ff81f3f48effdd6821d94d0d84ff536 2022-04-22T09:34:55+00:00 Marcin Juszkiewicz marcin@juszkiewicz.com.pl 2022-04-22T09:34:55+00:00 urn:sha1:016c5ed30c0fe6c46004731d13ec0748daa6c70c Tim Shearer started it in 1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae. Since all extend_start files are sourced rather than executed, the executable bits are now cleared throughout the project. Change-Id: Ia1797c32fc6a35f9f077c673abf4d8e16e51a760 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 2021-07-28T16:04:21+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2021-04-09T07:33:15+00:00 urn:sha1:bd90b02708d8c6b88692ec7308a41229fdcdaf22 As a project we never built RHEL based images so support for them was not tested. Change-Id: I27dfe34ade088228d71f6857ec4f3ab28ee63915 2021-02-16T12:36:05+00:00 Alexander Evseev alevseev@sbercloud.ru 2021-02-16T12:32:01+00:00 urn:sha1:6585332a63b277ff0d63c6c7bd0e77d640579a0a kolla-ansible runs ovs-dpdkctl.sh inside container, and ovs-dpdkctl.sh requires crudini. Change-Id: Iad84dd12432befe9250c50d4094b1e5e2e0cf8ee 2020-11-20T12:20:21+00:00 Mark Goddard mark@stackhpc.com 2020-11-17T14:40:32+00:00 urn:sha1:4b792b9a43bee3bfb499cea14924527550f2bce0 Only the final image in a hierarchy should have the footer block. neutron-infoblox-ipam-agent image still has two footers because it inherits from the neutron-server image. We set the user to root at the beginning of that Dockerfile, so that headers and footers have the right context. Change-Id: I95e5bb5583be2a76e289749e8adfc303a4e7197a 2020-09-21T12:10:57+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2020-07-07T11:05:33+00:00 urn:sha1:87730f8f7c02e5d295ccde2925c8b7b14e4ef693 There is small subset of images where we need to know which install_type or install_metatype is used. So add them only there (and their children). Change-Id: Ib7d5e36b958d6c8daf2989df32e29fa24b46c62a Implements: blueprint infra-images 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