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: Idf152f2d62466ea53959619c60dd62062d590382
This commit is contained in:
parent
4dd27f67f8
commit
53efcc8798
@ -79,8 +79,9 @@ octavia_oslomsg_notify_transport: rabbit
|
||||
octavia_oslomsg_notify_servers: 127.0.0.1
|
||||
octavia_oslomsg_notify_port: 5672
|
||||
octavia_oslomsg_notify_use_ssl: False
|
||||
octavia_oslomsg_notify_userid: octavia
|
||||
octavia_oslomsg_notify_vhost: /octavia
|
||||
octavia_oslomsg_notify_userid: "{{ octavia_oslomsg_rpc_userid }}"
|
||||
octavia_oslomsg_notify_password: "{{ octavia_oslomsg_rpc_password }}"
|
||||
octavia_oslomsg_notify_vhost: "{{ octavia_oslomsg_rpc_vhost }}"
|
||||
|
||||
## octavia User / Group
|
||||
octavia_system_user_name: octavia
|
||||
|
Loading…
Reference in New Issue
Block a user