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: I488970b695ce439c2de8fa0ad8f04b62882630ff
This commit is contained in:
parent
52c2a52727
commit
da509488d7
@ -88,8 +88,9 @@ cinder_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabbit'
|
|||||||
cinder_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
|
cinder_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
|
||||||
cinder_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
|
cinder_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
|
||||||
cinder_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
|
cinder_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
|
||||||
cinder_oslomsg_notify_userid: cinder
|
cinder_oslomsg_notify_userid: "{{ cinder_oslomsg_rpc_userid }}"
|
||||||
cinder_oslomsg_notify_vhost: /cinder
|
cinder_oslomsg_notify_password: "{{ cinder_oslomsg_rpc_password }}"
|
||||||
|
cinder_oslomsg_notify_vhost: "{{ cinder_oslomsg_rpc_vhost }}"
|
||||||
|
|
||||||
## Cinder User / Group
|
## Cinder User / Group
|
||||||
cinder_system_user_name: cinder
|
cinder_system_user_name: cinder
|
||||||
|
Loading…
Reference in New Issue
Block a user