Enable TLS for rabbitmq's replication traffic
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 28 Aug 2017 06:07:16 +0000 (09:07 +0300)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Tue, 5 Sep 2017 09:38:27 +0000 (09:38 +0000)
commit4d09ff3881b51938a71d69c713848cc8ae2c3f1d
treebc3c4e2c7f31ec7210948cdbb23466152eb434cd
parent193d275b119a406e5bbe4f2593711b3ec7723afe
Enable TLS for rabbitmq's replication traffic

This follows the RabbitMQ docs [1] for enabling TLS for the replication
traffic. It reuses the certificate that rabbitmq already has.

Unfortunately, pacemaker uses the shortname for the rabbitmq nodes, so
we are not able to do proper verification of the certificates, since we
can't allocate a certificate for shortnames. So, until pacemaker can
track the rabbit nodes through their FQDNs, we don't set any verification
options.

[1] https://www.rabbitmq.com/clustering-ssl.html

Depends on: https://github.com/voxpupuli/puppet-rabbitmq/pull/574

bp tls-via-certmonger
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
Change-Id: I265c89cb8898a6da78a606664a22c50f5e57a847
(cherry picked from commit 52404b85dc140d9ddc4605365454df0e052ee2cb)
manifests/profile/base/rabbitmq.pp