aboutsummaryrefslogtreecommitdiff
path: root/docker/swift/swift-rsyncd/extend_start.sh
AgeCommit message (Collapse)AuthorFilesLines
2025-03-21Remove swift container imagesMichal Nasiadka1-4/+0
Change-Id: I05a96f27b47a0f87bcf435872dd08ec0927232e3
2019-11-05swift-rsyncd: don't recursively chown /srv/node at startupMartin Chlumsky1-1/+1
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
2018-08-06Revert the patch set "Apply Swift rolling upgrade"Ha Manh Dong1-9/+0
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
2018-07-13Apply Swift rolling upgradeconfi-surya1-0/+9
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 <duonghq@vn.fujitsu.com> Co-Authored-By: Ha Manh Dong <donghm@vn.fujitsu.com> Change-Id: Ic59a2d2dda3469af5d4259e020d22b619ff7d603 Implements: blueprint apply-service-upgrade-procedure
2017-11-28Update swift for replication issuesJames McCarthy1-0/+1
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
2016-04-21Configures swift-rsyncd to use non-default portSerguei Bezverkhi1-1/+1
This PS configures swift-rsyncd process to use non-default port from the range above 1024. Change-Id: I7c37c548a5185a2ffac789383fe012619e401131 Closes-Bug: #1573137
2016-02-02Fix Swift for multinode P+ACO deploymentQiu Yu1-0/+3
Current Swift playbook is based on the preassumption of AIO setup. However, if one goes with default multinode setup (ansible/inventory/multinode), it follows the P + ACO deployment model, which proxy-server runs on controller nodes where ACO (account/container/object services) run on storage nodes. It will break because swift proxy-server no longer has access (it shouldn't have) to /srv/node path. This change ensure disk mounting part only happens on storage node. It also moves chown from proxy-server Dockerfile to rsyncd because no matter with PACO, P+ACO or P+A+C+O model, rsyncd is always running on each storage node. Change-Id: I3aa20454902caa9c84d3901bb91e4e4c93ac5f34 Partially-Implements: blueprint swift-physical-disk Closes-Bug: #1537544
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 23:56:31 +0000