<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/nova/nova-compute-ironic, 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 genisoimage package to nova-compute-ironic</title>
<updated>2025-12-09T14:07:58+00:00</updated>
<author>
<name>Rafal Lewandowski</name>
<email>rafal@stackhpc.com</email>
</author>
<published>2025-12-09T11:01:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=96b54022857ccef8dc6bb11789abe32119827109'/>
<id>urn:sha1:96b54022857ccef8dc6bb11789abe32119827109</id>
<content type='text'>
Closes-Bug: #2132960
Change-Id: I672f625e445bd1a2db1c4994baa7c44c20723a62
Signed-off-by: rafal Lewandowski &lt;rafal@stackhpc.com&gt;
</content>
</entry>
<entry>
<title>Move to CentOS Stream 10</title>
<updated>2025-07-16T14:05:50+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-05-20T09:21:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=9e36b8976657e5aaf285f4ab9f65603ab475fd89'/>
<id>urn:sha1:9e36b8976657e5aaf285f4ab9f65603ab475fd89</id>
<content type='text'>
Known missing packages:
- mod_auth_mellon - missing SAML support in Keystone/Horizon - built in Kolla COPR
- glusterfs-fuse in manila-share - built in Kolla COPR
- collectd/telegraf - no opstools repository
- redis - needs a switch to valkey
- python3-ethtool - not required for neutron-mlnx-agent since 6 years [1]

Building packages in Kolla COPR is a temporary solution until these show up
in EPEL10.

[1]: Id2cae3ac9ff049e9fc8225551f99e1e99a87fc65

Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/951751

Change-Id: I7074fabcf95184fcfd2561648ae1e05acfb0bc11
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: 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>Ensure nvme-cli is present in nova-compute images</title>
<updated>2021-12-07T15:02:03+00:00</updated>
<author>
<name>Pierre Riteau</name>
<email>pierre@stackhpc.com</email>
</author>
<published>2021-12-07T15:02:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=30eddf72f6d5380bb6078481581e47b0eec84982'/>
<id>urn:sha1:30eddf72f6d5380bb6078481581e47b0eec84982</id>
<content type='text'>
The nvme-cli package is required to get the nvme command executed by
os-brick, which is used by nova-compute.

We don't need to explicitely install it for centos binary images, as it
is required by os-brick which is required by openstack-nova-common, but
all other types of images were missing it.

Change-Id: I754939da7636c57d2a8d5b83debb5d8a58e38432
Closes-Bug: #1953509
</content>
</entry>
<entry>
<title>Add block labels to all Dockerfiles</title>
<updated>2020-03-01T17:25:58+00:00</updated>
<author>
<name>Christian Berendt</name>
<email>berendt@betacloud-solutions.de</email>
</author>
<published>2020-02-19T21:39:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=861f55fbfd7558d56008e6275b0c6f5993346b95'/>
<id>urn:sha1:861f55fbfd7558d56008e6275b0c6f5993346b95</id>
<content type='text'>
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
</content>
</entry>
<entry>
<title>Use base_package_type</title>
<updated>2019-01-17T15:23:41+00:00</updated>
<author>
<name>Alex Schultz</name>
<email>aschultz@redhat.com</email>
</author>
<published>2019-01-15T23:58:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=ae1322ec10861678abe1137f3013030b34335bc7'/>
<id>urn:sha1:ae1322ec10861678abe1137f3013030b34335bc7</id>
<content type='text'>
This change updates the docker files to use base_package_type instead
of doing specific distro checks for the rhel/deb generic cases. The
base_distro is still available and is used when a specific distro needs
a customization but if the differences are purely rpm vs deb, then the
base_package_type can be used.

Change-Id: I8d720bb185df65a0178061ccf20b1ab2265da2c5
</content>
</entry>
<entry>
<title>Add nvme-cli to nova compute packages</title>
<updated>2018-08-20T23:13:52+00:00</updated>
<author>
<name>Hamdy Khader</name>
<email>hamdyk@mellanox.com</email>
</author>
<published>2018-08-16T10:25:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=332a0a9601d3038538ef52189da97880a2ed8cfa'/>
<id>urn:sha1:332a0a9601d3038538ef52189da97880a2ed8cfa</id>
<content type='text'>
Change-Id: I7688a1c2065ed9183e5eeaaade8e31e0f76b4467
</content>
</entry>
</feed>
