MySQL: Use conditional instead of nested stack for TLS-specific bits
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 27 Mar 2017 11:00:46 +0000 (14:00 +0300)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 27 Mar 2017 11:00:46 +0000 (14:00 +0300)
commit3bd4a3f94b471ec210630e85877a9eebabb69e72
treeb94ae85adf78733034980cebb7f90b7439d7f695
parent7d0f27980dd60f4274f353fe7594905d1de45b13
MySQL: 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: Ib7151d67982957369f7c139a3b01274a1a746c4a
environments/enable-internal-tls.yaml
overcloud-resource-registry-puppet.j2.yaml
puppet/services/database/mysql-internal-tls-certmonger.yaml [deleted file]
puppet/services/database/mysql.yaml