Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2026.1 2026-03-26T13:01:45+00:00 2026-03-26T13:01:45+00:00 Piotr Milewski vurmil@gmail.com 2026-03-26T09:01:12+00:00 urn:sha1:0989434a050bbbf5bec7f428585f22598de89fc7 Change-Id: I3374810166f10c67df88e97e8bf10a692cfab2cf Signed-off-by: Piotr Milewski <vurmil@gmail.com> 2025-08-29T07:19:33+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-04-30T06:45:56+00:00 urn:sha1:5781b359efc32726645a7d5d5570bcec9f0035fa RDO has staffing problems and has decided to only support SLURP releases - let's drop reliance on that repository. Change-Id: I56f86a1c5262e3ee2bcbb52cae53c3b2655ed87f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2025-05-20T16:54:46+00:00 Michal Arbet michal.arbet@ultimum.io 2025-05-20T16:54:46+00:00 urn:sha1:0006320d98fa7e594fbd17ade36d2572ca3231ed Change-Id: I5295bba1e11f84217bb2b28ea4d92cb47812b778 2025-03-27T13:12:48+00:00 Zuul zuul@review.opendev.org 2025-03-27T13:12:48+00:00 urn:sha1:cba22d42356faac9904d3636e03b35d81dbe7c52 2025-02-18T08:41:17+00:00 Andriy Kurilin andr.kurilin@gmail.com 2024-09-17T11:49:32+00:00 urn:sha1:cfa266a3a2fd2f29ba48ecb93018197af5510649 Commit 79a234239516b94b1b79c7ddafcc4fbe4e3ba155 introduced an ability to build 'in-house'/'not-built-in' projects with Kolla. This commits extends this feature with an ability to use configure_user macro for 'not-built-in' users. The implementation is done the same way as for 'sources', i.e. engine after registers new section structure as soon as it finds unknown '<project>-user' section. In addition, the documentation and CI are extended to cover ``--docker-dir`` option. Change-Id: I690d9f3829083f2493bf286a1c45764b9699219b 2025-02-05T15:36:52+00:00 Seunghun Lee seunghun@stackhpc.com 2024-11-12T10:19:54+00:00 urn:sha1:4cab35b1a81055c3696e5fa42d794d6fc96076e6 Users can override the upper-constraints.txt by setting the source of openstack-base in kolla-build.conf. However, bifrost-base Dockerfile so far doesn't pass overridden upper-constraints file to Bifrost install playbook resulting the playbook not acknowledging it and just use upstream one. This change sets the source of Bifrost upper-constraints to use upper-constraints of openstack-base for consistency among all Kolla images With this, change the environment variable UPPER_CONSTRAINTS_FILE is only affecting kolla-toolbox image. Therefore, moved UPPER_CONSTRATINS_FILE variable example to the ``kolla_toolbox_pip_conf`` block of kolla-toolbox Dockerfile. Additionally, updated 'Python packages build options' section of documentation to represent latest method of changing Python package related options (including this change). Change-Id: I0a9c782ca1177ef84e4323cb1e5bfac0fb3f383c 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 2024-06-28T18:23:49+00:00 Zuul zuul@review.opendev.org 2024-06-28T18:23:49+00:00 urn:sha1:603f58cac55dd3081bcb5b7104e902f216089646 2024-06-28T00:19:10+00:00 Dawud dawud@stackhpc.com 2024-03-14T13:21:57+00:00 urn:sha1:077e0003d41746a0052564ee1487d981f125cec9 Co-authored-by: Will Szumski <will@stackhpc.com> Change-Id: I2b1c95395aeefb2ccb1d8edf415eee0f98c52190 2024-02-08T00:16:05+00:00 Tadas Sutkaitis tadasas@gmail.com 2023-07-20T21:44:37+00:00 urn:sha1:3ee1a82d8761902a75e075ccbcd8e9e02a226051 The main goal is to be able to build ARM images on standard x86 hardware. Add simple functions supported by python-py and podman-py to enable creation of container images on emulated architectures. Change-Id: I1526b460f6e271c2ec63ab3a3b1dc348d742e96d