Merge "Fix issues of multi-region devstack environment setup"

devstack/plugin.sh

@@ -60,6 +60,8 @@ function init_local_neutron_conf {
     iniset $NEUTRON_CONF DEFAULT core_plugin tricircle.network.local_plugin.TricirclePlugin
     iniset $NEUTRON_CONF DEFAULT service_plugins tricircle.network.local_l3_plugin.TricircleL3Plugin
 
+    iniset $NEUTRON_CONF client auth_url http://$KEYSTONE_SERVICE_HOST:5000/v3
+    iniset $NEUTRON_CONF client identity_url http://$KEYSTONE_SERVICE_HOST:35357/v3
     iniset $NEUTRON_CONF client admin_username admin
     iniset $NEUTRON_CONF client admin_password $ADMIN_PASSWORD
     iniset $NEUTRON_CONF client admin_tenant demo
@@ -89,10 +91,8 @@ function init_local_neutron_variables {
 
         local vlan_mapping="bridge:$TRICIRCLE_DEFAULT_VLAN_BRIDGE"
         local ext_mapping="extern:$TRICIRCLE_DEFAULT_EXT_BRIDGE"
-        OVS_BRIDGE_MAPPINGS=$vlan_mapping
-        if [ "$TRICIRCLE_START_SERVICES" == "False" ]; then
-            OVS_BRIDGE_MAPPINGS=$vlan_mapping,$ext_mapping
-        fi
+        OVS_BRIDGE_MAPPINGS=$vlan_mapping,$ext_mapping
+
     fi
 }
 

doc/source/multi-pod-installation-devstack.rst

@@ -204,6 +204,19 @@ In pod2 in node2 for OpenStack RegionTwo,
 
 - 6 After DevStack successfully starts, the setup is finished.
 
+.. note:: In the newest version of codes, we may fail to boot an instance in
+   node2. The reason is that Apache configuration file of Nova placement API
+   doesn't grant access right to the placement API bin folder. You can use
+   "screen -r" to check placement API is working well or not. If placement API
+   is in stuck status, manually update "/etc/apache2/sites-enabled/placement-api.conf"
+   placement API configuration file in node2 to add the following section::
+
+       <Directory /usr/local/bin>
+           Require all granted
+       </Directory>
+
+   After update, restart Apache service first, and then placement API.
+
 How to play
 ^^^^^^^^^^^