Browse code

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

Brant Knudson authored on 2015/03/15 02:28:59
Showing 1 changed files
... ...
@@ -226,12 +226,7 @@ function configure_keystone {
226 226
         iniset $KEYSTONE_CONF assignment driver "keystone.assignment.backends.$KEYSTONE_ASSIGNMENT_BACKEND.Assignment"
227 227
     fi
228 228
 
229
-    # Configure rabbitmq credentials
230
-    if is_service_enabled rabbit; then
231
-        iniset $KEYSTONE_CONF DEFAULT rabbit_userid $RABBIT_USERID
232
-        iniset $KEYSTONE_CONF DEFAULT rabbit_password $RABBIT_PASSWORD
233
-        iniset $KEYSTONE_CONF DEFAULT rabbit_host $RABBIT_HOST
234
-    fi
229
+    iniset_rpc_backend keystone $KEYSTONE_CONF DEFAULT
235 230
 
236 231
     # Set the URL advertised in the ``versions`` structure returned by the '/' route
237 232
     if is_service_enabled tls-proxy; then