Pass hieradata for internal TLS for RabbitMQ
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Fri, 9 Dec 2016 13:22:42 +0000 (15:22 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 9 Mar 2017 11:08:41 +0000 (11:08 +0000)
commit1992282b88beed0df0a25e54b4bd92bbc3b1919f
tree42cdd6772364833cafb93d10b6fd93c506ad7864
parent1f79a5b76c0ca54eb053862dc0231e59e082d968
Pass hieradata for internal TLS for RabbitMQ

As with other services, this passes the necessary hieradata to enable
TLS for RabbitMQ. This will mean (once we set it via puppet-tripleo)
that there will only be TLS connections, as the ssl_only option is being
used.

bp tls-via-certmonger

Change-Id: I960bf747cd5e3040f99b28e2fc5873ca3a7472b5
Depends-On: Ic2a7f877745a0a490ddc9315123bd1180b03c514
environments/enable-internal-tls.yaml
overcloud-resource-registry-puppet.j2.yaml
puppet/services/pacemaker/rabbitmq.yaml
puppet/services/rabbitmq-internal-tls-certmonger.yaml [new file with mode: 0644]
puppet/services/rabbitmq.yaml