<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/masakari, 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>Merge "kolla-build: fix build-date LABEL invalidating Docker layer cache"</title>
<updated>2026-06-29T14:52:12+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2026-06-29T14:52:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=00d2e9671d38a147f77b639e8fcf1cb8903aea25'/>
<id>urn:sha1:00d2e9671d38a147f77b639e8fcf1cb8903aea25</id>
<content type='text'>
</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>Remove cgi-bin creation in gnocchi and masakari</title>
<updated>2026-06-18T14:37:22+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-06-18T08:01:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=88b659d9886fb04749e2c4e43bb6b0ddbe786576'/>
<id>urn:sha1:88b659d9886fb04749e2c4e43bb6b0ddbe786576</id>
<content type='text'>
This is no longer required

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

Change-Id: I20a2ff0a97b9fad86b6103ec488a39e42cdba091
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>Merge "masakari: Add crmadmin and cibadmin to monitors sudoers"</title>
<updated>2026-06-02T10:59:50+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2026-06-02T10:59:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=cbdbd894b06b049e36ecd4fab4d0ecc3a49e0c00'/>
<id>urn:sha1:cbdbd894b06b049e36ecd4fab4d0ecc3a49e0c00</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove httpd_setup calls from api containers</title>
<updated>2026-04-28T11:22:25+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-04-28T07:28:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=929df04f10273cbbdae0bd1cc75f24f49963bc83'/>
<id>urn:sha1:929df04f10273cbbdae0bd1cc75f24f49963bc83</id>
<content type='text'>
We have dropped mod_wsgi support from services in [1].

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

Change-Id: Ie5da8427706dfb74bad4e174c990355a6870114c
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>masakari: Add crmadmin and cibadmin to monitors sudoers</title>
<updated>2026-03-13T06:53:06+00:00</updated>
<author>
<name>Kim soo</name>
<email>popododo0720@naver.com</email>
</author>
<published>2026-03-13T06:53:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=364b9f418c31b93b916a2328344b737bd68856e6'/>
<id>urn:sha1:364b9f418c31b93b916a2328344b737bd68856e6</id>
<content type='text'>
The hostmonitor calls crmadmin and cibadmin with run_as_root=True,
but the sudoers file only includes crm_mon. Since the container runs
as the masakari user, sudo calls to crmadmin and cibadmin fail with
"password required", causing the hostmonitor to skip all host
monitoring every cycle.

This completely breaks automatic instance evacuation in HCI
(hyper-converged) deployments where all nodes run the full pacemaker
stack instead of pacemaker-remote. In separated deployments, the
crmadmin code path is skipped because pacemaker_remote_status=True,
which is why this bug has gone undetected.

Closes-Bug: #2144074
Change-Id: I22bbaa1f1fd1f3d53de48ec7c0099d028118448b
Signed-off-by: Kim soo &lt;popododo0720@naver.com&gt;
</content>
</entry>
<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>masakari: Ensure log files are owned by masakari user</title>
<updated>2025-07-14T08:10:11+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-07-14T05:33:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=edd9933fdef22202d45da04c53cf739958ecaa27'/>
<id>urn:sha1:edd9933fdef22202d45da04c53cf739958ecaa27</id>
<content type='text'>
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/954903

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