Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2026.1 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 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 2021-08-12T07:00:52+00:00 Mark Goddard mark@stackhpc.com 2021-07-06T08:56:29+00:00 urn:sha1:928c4648a4c2cf08c616d74f340c675418ba3385 Packages are available for focal and bullseye. Change-Id: I61623748d1149adb1b096adf2fffb5a902df3181 2020-04-15T09:32:06+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2020-03-09T16:44:54+00:00 urn:sha1:53443c5c712f4ec23b859105e94bcd90abc27762 With the move to RHEL/CentOS 8 we no longer have Python 2 in our images so there is no need for checking which Python version (2.x or 3.x) is used inside of containers. We also no longer have to support yum as a value for distro_package_manager. Partially-Implements: blueprint centos-rhel-8 Change-Id: Ie45cf3465fedddbde7856961527421883ba3d5c9 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-03-12T17:48:18+00:00 Alex Schultz aschultz@redhat.com 2019-01-21T19:58:19+00:00 urn:sha1:3e5d8e2653db1c6c28cb428f81cd0bc332c623c3 RDO is currently working on python3 support for the next version of CentOS/RHEL based systems. This package uses the distro_python3 flag that was added as part of I4028991bad92c0e8e21066cc4173c06ce5eba393 to use the python3 specific package names. This change only adds python3 package names for RHEL systems. Conflicts-With: https://review.openstack.org/#/c/636457/ Change-Id: Iad6b70b433a0dd1b0f8ae6790fd280594517661a Related-Blueprint: python3-support 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 2018-07-26T18:51:41+00:00 Jon Schlueter jschluet@redhat.com 2018-07-26T18:50:39+00:00 urn:sha1:2b023ba13ef0f11757fef029a4a6ed5a2468700e Fixed up 5 Dockerfile.j2 files that had the issue Change-Id: I8a5551050a75d64712c36d53573437a18777a82f 2018-03-21T11:01:50+00:00 Harald Jensas hjensas@redhat.com 2018-02-19T16:13:14+00:00 urn:sha1:d0546485f6d16418eb645e7474965eaefc376953 * Adding Dockerfile to build image with ironic-neutron-agent. * Add ``neutron-base-plugin-networking-baremetal`` in kolla/common/config.py to enable building neutron with baremetal plugin. Since the ML2 mechanism driver and L2 Agent is in the same python package, the source install will include the ironic-neutron-agent as part of neutron-base. Change-Id: I232dcf44c8a56c268610053cf362714d52e6cb93