tripleo-heat-templates/deployment/glance
Giulio Fidente c8a828aab2 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
2021-03-11 12:36:10 +01:00
..
glance-api-container-puppet.yaml Fix start order for {swift_proxy,glance_api}_tls_proxy 2021-03-11 12:36:10 +01:00
glance-api-edge-container-puppet.yaml Remove DefaultPasswords interface 2021-02-12 11:38:44 +05:30