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: I0293fef6effefb1e3e7b74e11a10421eb1621b39
This commit is contained in:
Jesse Pretorius 2018-07-30 12:49:17 +01:00
parent 026b355afc
commit 57d0caf087
1 changed files with 3 additions and 2 deletions

View File

@ -133,8 +133,9 @@ keystone_oslomsg_notify_transport: "{{ oslomsg_notify_transport | default('rabbi
keystone_oslomsg_notify_servers: "{{ oslomsg_notify_servers | default('127.0.0.1') }}"
keystone_oslomsg_notify_port: "{{ oslomsg_notify_port | default('5672') }}"
keystone_oslomsg_notify_use_ssl: "{{ oslomsg_notify_use_ssl | default(False) }}"
keystone_oslomsg_notify_userid: keystone
keystone_oslomsg_notify_vhost: /keystone
keystone_oslomsg_notify_userid: "{{ keystone_oslomsg_rpc_userid }}"
keystone_oslomsg_notify_password: "{{ keystone_oslomsg_rpc_password }}"
keystone_oslomsg_notify_vhost: "{{ keystone_oslomsg_rpc_vhost }}"
## Role info
keystone_role_name: admin