Code Review / apex-tripleo-heat-templates.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 82db6ab) | patch
Rabbitmq: Use conditional instead of nested stack for TLS-specific bits
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 27 Mar 2017 09:11:27 +0000 (12:11 +0300)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 27 Mar 2017 10:33:12 +0000 (13:33 +0300)
commit69c213e3e3e9ba6635cbda055ec1542ac0b53d30
tree71cec1db620ec7c751355c9e47358be4ee3abca3tree | snapshot
parent82db6ab608b29e455fb2036aeb36537148b97cf9commit | diff
Rabbitmq: Use conditional instead of nested stack for TLS-specific bits

Usually a nested stack is used that contains the TLS-everywhere bits
(config_settings and metadata_settings). Nested stacks are very
resource intensive. So, instead of doing using nested stacks, this patch
changes that to use a conditional, and output the necessary
config_settings  and metadata_settings this way in an attempt to save
resources.

Change-Id: Ic25f84a81aefef91b3ab8db2bc864853ee82c8aa
environments/enable-internal-tls.yaml diff | blob | history
overcloud-resource-registry-puppet.j2.yaml diff | blob | history
puppet/services/rabbitmq-internal-tls-certmonger.yaml [deleted file] blob | history
puppet/services/rabbitmq.yaml diff | blob | history