Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2025-03-21T09:37:17+00:00 2025-03-21T09:37:17+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-03-20T14:56:14+00:00 urn:sha1:f2fba3842cd520161f5c136297d806e9fe4d7521 Change-Id: I05a96f27b47a0f87bcf435872dd08ec0927232e3 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-09T15:44:26+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-01T11:41:14+00:00 urn:sha1:1749da2fbf6b395b1a2cd77f349e0bea5d2f4a5e Big patch drops all mentions of binary images support. Suggestions are welcome how to split it into parts or handle better. Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3 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 2020-01-20T12:21:11+00:00 Dincer Celik hello@dincercelik.com 2020-01-19T19:47:10+00:00 urn:sha1:190a6f7a264c1ea8c0c565d2b75fb73fdc29d500 Replaces 'swift-object' package with 'swift-object-expirer' package. Change-Id: I8fa3fcad88b35743e042d8a62ccee722b08af673 Closes-Bug: #1859607 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 2017-06-09T06:27:43+00:00 Martin André m.andre@redhat.com 2017-06-09T06:27:43+00:00 urn:sha1:f0f4e70f1e440382482e45c14c3df1ebf9508780 The rational for packaging swift-object-expirer in openstack-swift-proxy is detailed in https://bugzilla.redhat.com/show_bug.cgi?id=1382921 It is a conscious packaging choice and not a bug, and as so update the comment in swift-object-expirer image. Change-Id: Ibccfa1482d3aeccf86a57603d9dedecbcc7d097c 2017-05-03T02:08:17+00:00 Jawon Choo jawon.choo@sk.com 2017-05-02T07:23:09+00:00 urn:sha1:31259fa595392c25a5e21d03c13e8896648a7695 centos based images have wrong label info, these changes fix own image's name and build-date. Change-Id: I1d13f8f386c8db12b5fbe5f8ecbbf9e3fbb4ba1c Closes-Bug: #1680341 2017-04-20T07:50:05+00:00 Chen dstbtgagt@foxmail.com 2017-04-18T08:20:03+00:00 urn:sha1:8c463a47a9c988df70046f7d343af0441bf29f4d Use LABEL instruction instead of MAINTAINER (deprecated) instruc- tion as suggested by Docker's official dockerfile guide. docs.docker.com/engine/reference/builder/#maintainer-deprecated Closes-Bug: #1683652 Change-Id: Ie87a1ddf31aefcd0b623fd2837d78de420e76898 2017-04-04T20:48:18+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2017-02-12T17:36:51+00:00 urn:sha1:69fef5cd59286b5eeaa4deaf9da97511413ed653 Debian support is not maintained in Kolla so it got a bit behind Ubuntu one. This changeset enables Debian for all images. Jessie (even with backports) may be too old for some images though. Also unify distro check to ['debian', 'ubuntu'] to keep alphabetical order like it is done for RPM distributions. Partially-Implements: blueprint multiarch-and-arm64-containers Change-Id: I056233fbfa277e0e2360c07c3f80d9558c554357