Inject TLS certificate and keys for the Overcloud
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Tue, 3 Nov 2015 13:19:18 +0000 (15:19 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 23 Nov 2015 09:55:26 +0000 (11:55 +0200)
commit97b12afbadeadac0be348b7cc263b090f6e6f0b8
tree2861d938b7f27a97441b3c38d667fdb952df9370
parentf6093f3081d70496ca99a358a2e484a85ff02926
Inject TLS certificate and keys for the Overcloud

This is a first implementation of adding TLS termination to the load
balancer in the controllers. The implementation was made so that the
appropriate certificate/private key in PEM format is copied to the
appropriate controller(s) via a software deployment resource.

And the path is then referenced on the HAProxy configuration, but this
part was left commented out because we need to be able to configure the
keystone endpoints in order for this to work properly.

Change-Id: I0ba8e38d75a0c628d8132a66dc25a30fc5183c79
environments/enable-tls.yaml [new file with mode: 0644]
overcloud-resource-registry-puppet.yaml
overcloud-without-mergepy.yaml
puppet/controller.yaml
puppet/extraconfig/tls/no-tls.yaml [new file with mode: 0644]
puppet/extraconfig/tls/tls-cert-inject.yaml [new file with mode: 0644]