<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/kuryr, branch stable/2025.2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2025-10-02T08:37:07+00:00</updated>
<entry>
<title>Move repo enablement to respective rpm blocks</title>
<updated>2025-10-02T08:37:07+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-10-01T08:57:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=17727e148120c43a5c7056b33e4277592376ccca'/>
<id>urn:sha1:17727e148120c43a5c7056b33e4277592376ccca</id>
<content type='text'>
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 &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>Remove RDO/Delorean</title>
<updated>2025-08-29T07:19:33+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-04-30T06:45:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=5781b359efc32726645a7d5d5570bcec9f0035fa'/>
<id>urn:sha1:5781b359efc32726645a7d5d5570bcec9f0035fa</id>
<content type='text'>
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 &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>Add mechanism for patching files in containers</title>
<updated>2024-11-15T08:04:30+00:00</updated>
<author>
<name>Michal Arbet</name>
<email>michal.arbet@ultimum.io</email>
</author>
<published>2022-02-15T12:50:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=11f65c6c1d3bfd6a12f8e71d778d46d635010449'/>
<id>urn:sha1:11f65c6c1d3bfd6a12f8e71d778d46d635010449</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>docker: implement macros to alter upper-constraints.txt</title>
<updated>2023-04-21T12:13:24+00:00</updated>
<author>
<name>Marcin Juszkiewicz</name>
<email>marcin.juszkiewicz+kolla@linaro.org</email>
</author>
<published>2023-03-27T14:55:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=19e40f160852a3519f3e58043b9b5555ca87f87d'/>
<id>urn:sha1:19e40f160852a3519f3e58043b9b5555ca87f87d</id>
<content type='text'>
upper_constraints_remove() macro allows to remove line
upper_constraints_version_change() allows to change versions

This way we have cleaner way to alter u-c in those images which need it.

Change-Id: I8fc354b8aa4d03fcd3ecfb9cbfe75de67492a0e3
</content>
</entry>
<entry>
<title>Fix writable rootwrap/privsep config</title>
<updated>2022-10-10T15:06:05+00:00</updated>
<author>
<name>Radosław Piliszek</name>
<email>radoslaw.piliszek@gmail.com</email>
</author>
<published>2022-08-29T18:13:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=2daf4331a648cc2df6982c1a6ec47a705e038255'/>
<id>urn:sha1:2daf4331a648cc2df6982c1a6ec47a705e038255</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>flatten images a bit</title>
<updated>2022-04-21T18:53:14+00:00</updated>
<author>
<name>Marcin Juszkiewicz</name>
<email>marcin.juszkiewicz+kolla@linaro.org</email>
</author>
<published>2022-04-21T16:21:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=e21aeb5ae955671937055baf57836120af8d4312'/>
<id>urn:sha1:e21aeb5ae955671937055baf57836120af8d4312</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Adjust permissions on _extend_start files.</title>
<updated>2022-04-11T15:22:24+00:00</updated>
<author>
<name>Tim Shearer</name>
<email>tshearer@advaoptical.com</email>
</author>
<published>2022-04-01T20:22:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae'/>
<id>urn:sha1:1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>docker: drop binary parts</title>
<updated>2022-04-09T15:44:26+00:00</updated>
<author>
<name>Marcin Juszkiewicz</name>
<email>marcin.juszkiewicz+kolla@linaro.org</email>
</author>
<published>2022-04-01T11:41:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=1749da2fbf6b395b1a2cd77f349e0bea5d2f4a5e'/>
<id>urn:sha1:1749da2fbf6b395b1a2cd77f349e0bea5d2f4a5e</id>
<content type='text'>
Big patch drops all mentions of binary images support. Suggestions are
welcome how to split it into parts or handle better.

Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3
</content>
</entry>
<entry>
<title>centos: enable repos where needed</title>
<updated>2021-04-13T11:21:39+00:00</updated>
<author>
<name>Marcin Juszkiewicz</name>
<email>marcin@juszkiewicz.com.pl</email>
</author>
<published>2021-04-12T12:32:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=38fcd184e872bf460a1a65e3342e9806e9b7a05a'/>
<id>urn:sha1:38fcd184e872bf460a1a65e3342e9806e9b7a05a</id>
<content type='text'>
With RDO use we did not disabled some repositories. This patch disable
them and enable where needed.

Change-Id: Ia9d537fe9c1ad54789d2bfb4027254fbb3defe7e
</content>
</entry>
<entry>
<title>Remove support for CentOS 7</title>
<updated>2020-04-15T09:32:06+00:00</updated>
<author>
<name>Marcin Juszkiewicz</name>
<email>marcin.juszkiewicz@linaro.org</email>
</author>
<published>2020-03-09T16:44:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=53443c5c712f4ec23b859105e94bcd90abc27762'/>
<id>urn:sha1:53443c5c712f4ec23b859105e94bcd90abc27762</id>
<content type='text'>
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
</content>
</entry>
</feed>
