Generate internal TLS hieradata for apache services
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 26 Sep 2016 15:34:10 +0000 (15:34 +0000)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 20 Oct 2016 09:22:42 +0000 (12:22 +0300)
commitdebbfbbf8fe8702fd3202f75e049496ee9bb3ddf
tree1f9fa5dff8468427fbac54ef35bb80a2377f4eb9
parent81aa47d3143bf58cffdb0bd9fbacfd0e05e195e4
Generate internal TLS hieradata for apache services

This adds an environment file that can be used to enable TLS in
the internal endpoints via certmonger if used. This will include
a nested stack that will create the hash that will be used to
create the certmonger certificates.

When setting up a service over apache via puppet, we used to disable
explicitly ssl (which sets modd_ssl-related fields for that vhost).
We now make this depend on the EnableInternalTLS flag. This has only
been done for keystone, but more services will be added as the
puppet code lands

bp tls-via-certmonger

Depends-On: I303f6cf47859284785c0cdc65284a7eb89a4e039
Change-Id: I12e794f2d4076be9505dabfe456c1ca6cfbd359c
environments/enable-internal-tls.yaml
overcloud-resource-registry-puppet.j2.yaml
puppet/services/apache-internal-tls-certmonger.yaml [new file with mode: 0644]
puppet/services/apache.yaml
puppet/services/keystone.yaml