openstack/kolla.git/docker/swift/swift-rsyncd, branch master

Remove swift container images

2025-03-21T09:37:17+00:00

Change-Id: I05a96f27b47a0f87bcf435872dd08ec0927232e3

Add mechanism for patching files in containers

2024-11-15T08:04:30+00:00

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

Adjust permissions on _extend_start files.

2022-04-11T15:22:24+00:00

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

Add block labels to all Dockerfiles

2020-03-01T17:25:58+00:00

Change-Id: I9692dda817ef134d647247431565e1b58cf9da41

swift-rsyncd: don't recursively chown /srv/node at startup

2019-11-05T14:12:46+00:00

Instead of doing a recursive chown on /srv/node, chown only /srv/node and any immediate subdirectory under /srv/node. Change-Id: I8fd93fa77ba9fc63910360300b8783a34bd4e6d5 Closes-Bug: #1851169

Use base_package_type

2019-01-17T15:23:41+00:00

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

Revert the patch set "Apply Swift rolling upgrade"

2018-08-06T09:18:30+00:00

Due to there is no way to execute swift graceful shutdown commands from swift-bootstrap container to swift service containers, so we need to revert the patch set at [1]. [1] https://review.openstack.org/#/c/560248/ Change-Id: I3363895347c535054584d63e22284c211ca38ad6

Apply Swift rolling upgrade

2018-07-13T03:26:36+00:00

Apply Swift rolling upgrade based on recommendations from Swift PTL John Dickinson at [1] [1]https://www.swiftstack.com/blog/2013/12/20/upgrade-openstack-swift-no-downtime/ Co-Authored-By: Duong Ha-Quang Co-Authored-By: Ha Manh Dong Change-Id: Ic59a2d2dda3469af5d4259e020d22b619ff7d603 Implements: blueprint apply-service-upgrade-procedure

Update swift for replication issues

2017-11-28T13:59:43+00:00

There are corresponding ansible changes to go with these image changes - add nc to swift image, and create dir for lock files. nc allows for rsync replication to easily target {{ swift_rsync_port }} change the lock file location for swift user to access - see bug for more details. Change-Id: I78826aeee35601ff65cbe50932482ef2f68346ae Closes-Bug: #1733851

Override image's meta info.

2017-05-03T02:08:17+00:00

centos based images have wrong label info, these changes fix own image's name and build-date. Change-Id: I1d13f8f386c8db12b5fbe5f8ecbbf9e3fbb4ba1c Closes-Bug: #1680341