<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/cyborg/cyborg-base, 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>2024-11-15T08:04:30+00:00</updated>
<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>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>Remove footer block from intermediate images</title>
<updated>2020-11-20T12:20:21+00:00</updated>
<author>
<name>Mark Goddard</name>
<email>mark@stackhpc.com</email>
</author>
<published>2020-11-17T14:40:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=4b792b9a43bee3bfb499cea14924527550f2bce0'/>
<id>urn:sha1:4b792b9a43bee3bfb499cea14924527550f2bce0</id>
<content type='text'>
Only the final image in a hierarchy should have the footer block.

neutron-infoblox-ipam-agent image still has two footers because it
inherits from the neutron-server image. We set the user to root at the
beginning of that Dockerfile, so that headers and footers have the right
context.

Change-Id: I95e5bb5583be2a76e289749e8adfc303a4e7197a
</content>
</entry>
<entry>
<title>Ensure the confs exists for cyborg and masakari</title>
<updated>2020-05-19T15:49:01+00:00</updated>
<author>
<name>gugug</name>
<email>gu.jin@99cloud.net</email>
</author>
<published>2020-05-17T14:19:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=2e6d2f144cd2de18193d9d87d36c95dfb75fb1b7'/>
<id>urn:sha1:2e6d2f144cd2de18193d9d87d36c95dfb75fb1b7</id>
<content type='text'>
1. When cyborg images build completed, the /etc/cyborg folder is not
exits, and there is not confs, especially the api-paste.ini
2. When masakari images build completed, it's configs is missing,
this ps add them together

cyborg should keep consistence with the other images[1], this PS
to add it.

[1]: https://github.com/openstack/kolla/blob/master/docker/nova/nova-base/Dockerfile.j2#L137

Change-Id: I8a802617952f80cfb9f906398054ef6d17559589
</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>Add cyborg to kolla</title>
<updated>2019-03-27T16:19:13+00:00</updated>
<author>
<name>Bai Yongjun</name>
<email>byj994@163.com</email>
</author>
<published>2018-11-22T14:27:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=265f643295efa50b8d5c7dc716353883d645c588'/>
<id>urn:sha1:265f643295efa50b8d5c7dc716353883d645c588</id>
<content type='text'>
Because kolla not have cyborg so should add this.

Implements: blueprint add-cyborg

Change-Id: I497e67e3a754fccfd2ef5a82f13ccfaf890a6fcd
</content>
</entry>
</feed>
