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: I17067d734d9388f9bb2b9b88463bc8b4e2b1c9a1
This commit is contained in:
parent
7e588c057e
commit
341f12af5b
@ -128,8 +128,9 @@ nova_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabbit')
|
||||
nova_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
|
||||
nova_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
|
||||
nova_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
|
||||
nova_oslomsg_notify_userid: nova
|
||||
nova_oslomsg_notify_vhost: /nova
|
||||
nova_oslomsg_notify_userid: "{{ nova_oslomsg_rpc_userid }}"
|
||||
nova_oslomsg_notify_password: "{{ nova_oslomsg_rpc_password }}"
|
||||
nova_oslomsg_notify_vhost: "{{ nova_oslomsg_rpc_vhost }}"
|
||||
|
||||
## RabbitMQ info
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user