Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2026.1 2025-10-02T08:37:07+00:00 2025-10-02T08:37:07+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-10-01T08:57:21+00:00 urn:sha1:17727e148120c43a5c7056b33e4277592376ccca Currently we are enabling repos irrespective of rpm/deb statement blocks and not failing in the method used if a repository is missing. Downside is - we might be producing one more layer, but it probably is a more logical approach. This is required for adding rpm support in repos.yaml that will also include failing on missing repositories. Change-Id: I5479c5c935760f00fe4cd307366f261deee3199f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 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-12-06T14:57:51+00:00 Michal Nasiadka mnasiadka@gmail.com 2022-12-06T13:06:55+00:00 urn:sha1:e221ac8f2704a21461f9b36134816329a43272cc Support has been dropped in kolla-ansible, the upgrade path is opensearch. Change-Id: I6f32aacb4e0b7dd1eb7206e02425b16f5beae4f0 2022-10-10T15:06:05+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2022-08-29T18:13:34+00:00 urn:sha1:2daf4331a648cc2df6982c1a6ec47a705e038255 Fixes a hypothetical security issue related to privilege escalation via rootwrap/privsep. A potential vulnerable service could previously allow writes to its rootwrap/privsep config and thus allow for more commands to be run with root privileges via rootwrap/privsep. For a succesful attack, this would also require the service to allow to run arbitrary commands via rootwrap/privsep. Thus far, no such vulnerabilities have been reported and thus this fix is simply strengthening the container images against such an issue in the future. Change-Id: I92c81c77e6a16570a108cde8031f7977930fb02a Closes-Bug: #1874298 2022-09-27T07:40:06+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-05T14:53:34+00:00 urn:sha1:878b00013b01e3d02a704ce7c9fac1629cd1a705 OpenStack 'zed' requires Python 3.8+ so RHEL 8 family has to go. This changeset moves to CentOS Stream 9 while move to RockyLinux 9 is planned as final solution. CI moved to CentOS Stream 9 nodes. Depends-on: https://review.opendev.org/c/openstack/kolla-ansible/+/839715 Change-Id: I113b9984294cf8663d3fc0c8840320e1d40ea731 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-02-04T20:39:17+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-02-04T16:15:27+00:00 urn:sha1:941d021e091567d2709bbb868768c6dc4a3372e0 Change-Id: Iad7e7ebb1fbf4d14f20960d6257345db71d0e214 2022-02-03T15:13:59+00:00 Michal Nasiadka mnasiadka@gmail.com 2022-02-03T14:52:19+00:00 urn:sha1:405fca90f2c8d3763ac56ce8b925611d136bba6c Since CentOS Linux 8 repository retirement from CentOS mirrors - we need to use CentOS Stream 8 version of Opstools repo. Listed below packages are missing from the repo, and according to the maintainer dpdk_telemetry is not going to show up at all (it's basically dead). The rest of the packages might show up at a later stage - but it's not a priority for the maintainer. - collectd-dpdk_telemetry - collectd-libpod-stats - collectd-sensubility - python3-sqlalchemy-collectd Change-Id: I5f446fc276e245c1e6974ceeb6ff3dccd84ee502 2021-05-11T10:45:16+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2021-04-20T16:25:56+00:00 urn:sha1:0506ede84f97159a8156ad51aea395d0868e6141 We do not test support for ppc64le on CI or other systems. In previous cycles it was used by TripleO and now they have own way. Change-Id: Ibd955869a6f9485dfa4d08a8ad2f4b28b7d59c15 2020-08-05T20:20:33+00:00 pleimer pfbleimer@gmail.com 2020-08-05T19:57:08+00:00 urn:sha1:094a49d41dd1f071cf5f6ac4220611e0ddd69c40 This patch adds the installation of collectd-libpod-stats as part of the collectd image. The package is available in the centos-opstools repo. Collectd-libpod-stats monitors resource usage of running containers on a host, specifically those managed by the libpod library. Upstream: https://github.com/pleimer/collectd-libpod-stats Change-Id: I12efbaae9c0795f29c2f68158127509fd1b543b0 Signed-off-by: pleimer <pfbleimer@gmail.com>