Keystone RPC backend config consistency
lib/keystone was setting up rabbit config directly rather than using the iniset_rpc_backend function that other projects use. Change-Id: Ic368f102c808cdbd2e4cbc1ff457cdf17a681332
This commit is contained in:
parent
f6fd39f974
commit
5dfecc8966
@ -226,12 +226,7 @@ function configure_keystone {
|
||||
iniset $KEYSTONE_CONF assignment driver "keystone.assignment.backends.$KEYSTONE_ASSIGNMENT_BACKEND.Assignment"
|
||||
fi
|
||||
|
||||
# Configure rabbitmq credentials
|
||||
if is_service_enabled rabbit; then
|
||||
iniset $KEYSTONE_CONF DEFAULT rabbit_userid $RABBIT_USERID
|
||||
iniset $KEYSTONE_CONF DEFAULT rabbit_password $RABBIT_PASSWORD
|
||||
iniset $KEYSTONE_CONF DEFAULT rabbit_host $RABBIT_HOST
|
||||
fi
|
||||
iniset_rpc_backend keystone $KEYSTONE_CONF DEFAULT
|
||||
|
||||
# Set the URL advertised in the ``versions`` structure returned by the '/' route
|
||||
if is_service_enabled tls-proxy; then
|
||||
|
Loading…
Reference in New Issue
Block a user