Default MQ RPC/Notify credentials/vhosts to match

When the RPC and Notify service are the same, the credentials
must match - otherwise the tasks to create the user/password
will overwrite with each other.

If the two clusters are different, then the matching credentials
and vhost will not be a problem. However, if the deployer really
wishes to make sure they're different, then the vars can be
overridden.

Also, to ensure that the SSL value is consistently set in the
conf file, we apply the bool filter. We also use the 'notify'
SSL setting as the messaging system for Notifications is more
likely to remain rabbitmq in our default deployment with qrouterd
becoming the default for RPC messaging.

Change-Id: I618e393b9332eac6fd35472c58dfa2935da09a4d
This commit is contained in:
Jesse Pretorius 2018-07-30 12:58:30 +01:00 committed by Jesse Pretorius (odyssey4me)
parent 63afb90d82
commit c93be4372d
1 changed files with 3 additions and 2 deletions

View File

@ -142,8 +142,9 @@ trove_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabbit')
trove_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
trove_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
trove_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
trove_oslomsg_notify_userid: trove
trove_oslomsg_notify_vhost: /trove
trove_oslomsg_notify_userid: "{{ trove_oslomsg_rpc_userid }}"
trove_oslomsg_notify_password: "{{ trove_oslomsg_rpc_password }}"
trove_oslomsg_notify_vhost: "{{ trove_oslomsg_rpc_vhost }}"
# Rabbit vars
trove_control_exchange: trove