Enable TLS in the internal network for keystone
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 13 Jul 2016 09:27:23 +0000 (12:27 +0300)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 19 Oct 2016 14:37:32 +0000 (17:37 +0300)
commit76bf2f532f9541eaf9cd7242ad2bf520f6788033
treea324b63a3e9de8e21ecc0c0e7b5368b1be726d19
parente86706f0f6c589ed8baeb9616b128a738b330a94
Enable TLS in the internal network for keystone

This optionally enables TLS for keystone in the internal network.
If internal TLS is enabled, each node that is serving the keystone
service will use certmonger to request its certificate.

This, in turn should also configure a command that should be ran when
the certificate is refreshed (which requires the service to be
restarted).

bp tls-via-certmonger
Change-Id: I303f6cf47859284785c0cdc65284a7eb89a4e039
manifests/certmonger/httpd.pp [new file with mode: 0644]
manifests/haproxy.pp
manifests/profile/base/keystone.pp