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: I8e917033595660bf30c0b897f07db1bdfc2ff6d8
This commit is contained in:
parent
52444d4d97
commit
595af4fe6a
@ -235,8 +235,9 @@ ironic_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabbit'
|
||||
ironic_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
|
||||
ironic_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
|
||||
ironic_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
|
||||
ironic_oslomsg_notify_userid: ironic
|
||||
ironic_oslomsg_notify_vhost: /ironic
|
||||
ironic_oslomsg_notify_userid: "{{ ironic_oslomsg_rpc_userid }}"
|
||||
ironic_oslomsg_notify_password: "{{ ironic_oslomsg_rpc_password }}"
|
||||
ironic_oslomsg_notify_vhost: "{{ ironic_oslomsg_rpc_vhost }}"
|
||||
|
||||
# Auth
|
||||
ironic_service_user_name: "ironic"
|
||||
|
Loading…
Reference in New Issue
Block a user