<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/fluentd, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=master</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2026-07-06T19:59:40+00:00</updated>
<entry>
<title>Migrate to pyproject.toml</title>
<updated>2026-07-06T19:59:40+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-07-06T13:26:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=db35ac8d793506bc43b62e7e39d27a75de1043ed'/>
<id>urn:sha1:db35ac8d793506bc43b62e7e39d27a75de1043ed</id>
<content type='text'>
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.

Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.

Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>kolla-build: fix build-date LABEL invalidating Docker layer cache</title>
<updated>2026-06-24T13:00:26+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-06-18T15:16:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=a1a3fdc1b54baf62f234ddc9dac4906e30eb5d11'/>
<id>urn:sha1:a1a3fdc1b54baf62f234ddc9dac4906e30eb5d11</id>
<content type='text'>
The build-date label was rendered into a LABEL instruction on line
3 of every Dockerfile template, immediately after FROM.

Because Docker invalidates the cache for a changed instruction and
all subsequent layers, a date change caused a full rebuild of every
image on each new calendar day, even when nothing else had changed.

Fix this by removing build-date from the Dockerfile templates and
applying it as a --label argument at build time via image.labels.

Labels passed on the build command line are not part of the
Dockerfile cache key, so the date is still recorded in the image
metadata without affecting layer caching.

Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77
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>bump td-agent lts from v4 to v5</title>
<updated>2023-11-30T07:07:31+00:00</updated>
<author>
<name>Sven Kieske</name>
<email>kieske@osism.tech</email>
</author>
<published>2023-09-13T17:38:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=c0aee4adb69e25f0e75fc9f907cf962ef024f358'/>
<id>urn:sha1:c0aee4adb69e25f0e75fc9f907cf962ef024f358</id>
<content type='text'>
notice that the td-agent command got renamed to fluentd.
see also the upgrade notes at[0].

for more details, refer to the changelog[1].

[0]: https://web.archive.org/web/20231006084137/https://www.fluentd.org/blog/upgrade-td-agent-v4-to-v5
[1]: https://github.com/fluent/fluent-package-builder/blob/b4b7017c09d78f2c404db62612733b40f69668a6/CHANGELOG.md#release-v500---20230729

Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/901509
Change-Id: I5e95363c6c180e330945fe3d98e97c7049bbd6f7
Signed-off-by: Sven Kieske &lt;kieske@osism.tech&gt;
</content>
</entry>
<entry>
<title>fluentd: Add labels for transition to v5</title>
<updated>2023-11-29T18:08:08+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2023-11-20T22:04:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=30fd4b00eeb3aaabb615473df96aead9b34d0f0f'/>
<id>urn:sha1:30fd4b00eeb3aaabb615473df96aead9b34d0f0f</id>
<content type='text'>
Change-Id: Ibe0eb9ada69db3ef8042306fdec44bfda1dd9ce0
</content>
</entry>
<entry>
<title>Merge "Drop elasticsearch, kibana and logstash"</title>
<updated>2022-12-07T13:30:25+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2022-12-07T13:30:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=d5886bc3b8e3fe03f3485f6533d471082ffa89c6'/>
<id>urn:sha1:d5886bc3b8e3fe03f3485f6533d471082ffa89c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Drop elasticsearch, kibana and logstash</title>
<updated>2022-12-06T14:57:51+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2022-12-06T13:06:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=e221ac8f2704a21461f9b36134816329a43272cc'/>
<id>urn:sha1:e221ac8f2704a21461f9b36134816329a43272cc</id>
<content type='text'>
Support has been dropped in kolla-ansible, the upgrade path is opensearch.

Change-Id: I6f32aacb4e0b7dd1eb7206e02425b16f5beae4f0
</content>
</entry>
<entry>
<title>Remove monasca, kafka, storm and zookeeper.</title>
<updated>2022-12-06T12:58:10+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2022-12-05T14:10:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=52a53927f5d390886c3940e364fe9fa888e3bc98'/>
<id>urn:sha1:52a53927f5d390886c3940e364fe9fa888e3bc98</id>
<content type='text'>
Monasca, kafka, storm and zookeeper have been removed in kolla-ansible [1],[2].

[1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392
[2]: https://review.opendev.org/c/openstack/kolla-ansible/+/865029

Change-Id: I0958a9353bc4585c4f65a1d316328a0e80b0b8b7
</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>
</feed>
