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 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-21T18:53:14+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-21T16:21:42+00:00 urn:sha1:e21aeb5ae955671937055baf57836120af8d4312 As we have one type of images now some RUN calls could be merged so we will have less layers in resulting images. Change-Id: I5178c58fbd8c65efe825dc249c0f1368ef0fe8e0 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 2021-03-01T13:30:59+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2021-03-01T13:14:59+00:00 urn:sha1:8d70e3f0cc3681c6f786ccbe076cd6a028998857 1. stop pinning networking-hyperv Pike release was long time ago so maybe it is time to unpin it? commit 6dc8e978462fd08122133e273ae956721997d3af Author: Dan Ardelean <dardelean@cloudbasesolutions.com> Date: Mon Aug 28 12:56:25 2017 +0300 Change networking-hyperv version for Pike 2. stop install vmware-nsxlib as a plugin vmware-nsx is a plugin and we install it already vmware-nsxlib can be fetched from Pypi Solves: INFO:kolla.common.utils.neutron-server:The conflict is caused by: INFO:kolla.common.utils.neutron-server: The user requested vmware-nsxlib 15.0.8.dev129 (from /plugins/vmware-nsxlib-15.0.8.dev129) INFO:kolla.common.utils.neutron-server: vmware-nsx 15.0.1.dev424 depends on vmware-nsxlib>=17.0.0 Change-Id: I6ef344d463333e5cdc3a0850c8e068218779fdbd 2020-09-30T16:45:03+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-30T16:45:03+00:00 urn:sha1:faaa38f9c4320e90a8ecd199f7610ed343e25f74 It seems I mixed up the order when commenting/uncommenting. Neutron base has to go first. Change-Id: Ib2bf51d4c6e2a574b98671a699777cd8a9a22768 2020-09-23T08:24:29+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-23T08:24:29+00:00 urn:sha1:7261c3b1704590f492206096df4625f9abb871c6 For details see [1]. Note this will also be amended on the Kolla-Ansible side to squash [2] as well. [1] https://review.opendev.org/750075 [2] https://bugs.launchpad.net/kolla-ansible/+bug/1894380 Change-Id: Id47ea8a5ea5318a69cf6814162db2115b40c7e6f 2020-09-05T17:42:22+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-05T15:49:35+00:00 urn:sha1:2725ed9d842622078e31165d91718e58d07620e0 1) makes bifrost unbuildable as it evolves rapidly at the moment 2) makes neutron bootstrap/upgrade only the core service [1] 1) will be reverted 2) will be made more flexible [1] https://bugs.launchpad.net/bgpvpn/+bug/1894056 Change-Id: I1eefcfceded985b5f61ee8d796f9d8994c9ee97c 2020-06-18T22:12:05+00:00 Alfredo Moralejo amoralej@redhat.com 2020-06-18T14:03:55+00:00 urn:sha1:d3742fb9d819b6be3818842ba990bf4739d59051 FWaaS is being retired upstream [1][2] in V cycle. [1] https://review.opendev.org/#/c/735838/ Change-Id: I45679c8596844780565644e52034bd3de0915ff4