Giulio Fidente eb61c80549 Fix start order for {swift_proxy,glance_api}_tls_proxy ... In stack updates adding TLS to Swift would not work because swift_proxy_tls_proxy is started when the pre-existing swift_proxy container is still up and listening on the TCP port which should instead be used by swift_proxy_tls_proxy This change ensures swift_proxy_tls_proxy and glance_api_tls_proxy containers are started after the actual swift_proxy and glance_api containers are started. Co-Authored-By: Michele Baldessari <michele@acksyn.org> Change-Id: I980dfc54b799c6b1d648489a727a590dd26fa502 Closes-Bug: 1918642 (cherry picked from commit c8a828aab2) (cherry picked from commit a6c7ba02a9) (cherry picked from commit 33b47f4792)		2021-03-17 08:11:00 +00:00
..
releasenotes/notes	Refresh Swift ring files without restarting containers	2021-01-13 16:45:18 +01:00
external-swift-proxy-baremetal-puppet.yaml	Make ExternalSwift*Url parameters optional	2021-02-03 23:00:01 +01:00
swift-base.yaml	flatten the swift service configurations	2019-01-26 17:10:27 -05:00
swift-dispersion-baremetal-puppet.yaml	flatten the swift service configurations	2019-01-26 17:10:27 -05:00
swift-proxy-container-puppet.yaml	Fix start order for {swift_proxy,glance_api}_tls_proxy	2021-03-17 08:11:00 +00:00
swift-ringbuilder-container-puppet.yaml	Fix swift containers idempotency	2021-01-13 16:46:03 +01:00
swift-storage-container-puppet.yaml	Use ansible_facts instead	2021-03-01 14:57:11 -07:00