Browse code

Don't configure neutron metadata agent for neutron API access

Metadata agent now talks to neutron-server thru AMQP, so there is no use
for API access configuration.

Change-Id: I8f81eea91fe3448d5098e77312f64f2eaba68a68
Depends-On: I254c575c66214f50fb93a94c46c4c9caebfc2937
Closes-Bug: #1502947

Ihar Hrachyshka authored on 2015/10/07 01:09:07
Showing 1 changed files
... ...
@@ -1050,11 +1050,6 @@ function _configure_neutron_metadata_agent {
1050 1050
     if [[ "$Q_USE_ROOTWRAP_DAEMON" == "True" ]]; then
1051 1051
         iniset $Q_META_CONF_FILE AGENT root_helper_daemon "$Q_RR_DAEMON_COMMAND"
1052 1052
     fi
1053
-
1054
-    # Configures keystone for metadata_agent
1055
-    # The third argument "True" sets auth_url needed to communicate with keystone
1056
-    _neutron_setup_keystone $Q_META_CONF_FILE DEFAULT True
1057
-
1058 1053
 }
1059 1054
 
1060 1055
 function _configure_neutron_ceilometer_notifications {
... ...
@@ -1212,17 +1207,10 @@ function _neutron_setup_rootwrap {
1212 1212
     fi
1213 1213
 }
1214 1214
 
1215
-# Configures keystone integration for neutron service and agents
1215
+# Configures keystone integration for neutron service
1216 1216
 function _neutron_setup_keystone {
1217 1217
     local conf_file=$1
1218 1218
     local section=$2
1219
-    local use_auth_url=$3
1220
-
1221
-    # Configures keystone for metadata_agent
1222
-    # metadata_agent needs auth_url to communicate with keystone
1223
-    if [[ "$use_auth_url" == "True" ]]; then
1224
-        iniset $conf_file $section auth_url $KEYSTONE_SERVICE_URI/v2.0
1225
-    fi
1226 1219
 
1227 1220
     create_neutron_cache_dir
1228 1221
     configure_auth_token_middleware $conf_file $Q_ADMIN_USERNAME $NEUTRON_AUTH_CACHE_DIR $section