Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2026.1 2024-12-10T20:22:51+00:00 2024-12-10T20:22:51+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-11-29T11:12:42+00:00 urn:sha1:795e347853c090d0067c6d309b112414b0c7c5c7 This reverts commit 5af5febf50bc0a02422b437b16598570d0c5ffe3. Reason for revert: Epoxy cycle is on In addition to the revert skyline-apiserver aiosqlite u-c is removed until [1] is merged, designate rootwrap.conf.sample file has been renamed to rootwrap.conf and pycadf is bumped to 4.0.0. [1]: https://review.opendev.org/c/openstack/skyline-apiserver/+/935604 Change-Id: I1265633f0913b7927955564fac911a682615004a 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-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-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-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-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-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-11-18T18:41:38+00:00 Viktor Michalek viktor.michalek@ultimum.io 2019-11-15T18:41:02+00:00 urn:sha1:63bd1c9124f6480b49885d9ccea3fc6100d50420 Change-Id: I4a7bbfaf3c30c57432de056f701d8abc7992d142 Closes-Bug: 1852784