tripleo-heat-templates/deployment/glance
Giulio Fidente a6c7ba02a9 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)
2021-03-12 11:24:37 +00:00
..
glance-api-container-puppet.yaml Fix start order for {swift_proxy,glance_api}_tls_proxy 2021-03-12 11:24:37 +00:00
glance-api-edge-container-puppet.yaml DCN: use FQDN in glance endpoint with internal TLS 2020-08-31 09:16:44 -07:00