From 15f7775800b3b3b17c31d3492ba2b7c924c26a14 Mon Sep 17 00:00:00 2001 From: Jesse Pretorius Date: Mon, 30 Jul 2018 12:44:13 +0100 Subject: [PATCH] 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: Id94e6337032807ee5baa79945e043c9282e17263 --- defaults/main.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/defaults/main.yml b/defaults/main.yml index 3650cce..34ff650 100644 --- a/defaults/main.yml +++ b/defaults/main.yml @@ -91,8 +91,9 @@ designate_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabb designate_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}" designate_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}" designate_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}" -designate_oslomsg_notify_userid: designate-notify -designate_oslomsg_notify_vhost: /designate +designate_oslomsg_notify_userid: "{{ designate_oslomsg_rpc_userid }}" +designate_oslomsg_notify_password: "{{ designate_oslomsg_rpc_password }}" +designate_oslomsg_notify_vhost: "{{ designate_oslomsg_rpc_vhost }}" ## RabbitMQ info