tricircle/devstack
xiulin yin f6cd0e5061 Fix issues of multi-region devstack environment setup
1. What is the problem
(1) Currently we only add bridge mapping for br-extern in RegionTwo by
default in plugin.sh, so if we only have one node for the tempest
test, we can not test the cases that network is created in physical
network of "extern".
(2) Keystone url is not configured explicitly in tricircle local
Neutron plugin configuration so local Neutron plugin may fail to connect
to central Neutron.
(3) In multi-pod installation, Nova services in node2 fail to talk to
placement API due to placement API configuration problem, which leads
to instance booting error.

2. What is the solution to the problem
(1) Add bridge mapping for br-extern both in RegionOne and RegionTwo
by default.
(2) Configure two options client.identity_url and client.auth_url in
plugin.sh to make sure local Neutron server can correctly connect to
central Neutron server.
(3) Update multi-pod installation guide to add a workaround for the
placement API problem.

3. What the features need to be implemented to the Tricircle
No new features.

Change-Id: I0925ee976a3bc7ce16b5ac19865c08dedb2de423
2017-02-15 16:39:26 +08:00
..
admin-openrc.sh Merge the verify scripts 2016-03-26 08:10:45 +00:00
local.conf.node_1.sample Add 'extern' physical network create supported 2017-01-22 15:44:47 +08:00
local.conf.node_2.sample Use tempest and tricircle in Devstack samples 2017-01-13 17:55:02 -06:00
local.conf.sample Use tempest and tricircle in Devstack samples 2017-01-13 17:55:02 -06:00
plugin.sh Fix issues of multi-region devstack environment setup 2017-02-15 16:39:26 +08:00
settings Remove cmd folder 2017-02-14 17:14:54 +08:00
verify_cross_pod_install.sh Clean useless tables in Tricircle after splitting 2017-01-05 09:53:45 +08:00
verify_top_install.sh Clean useless tables in Tricircle after splitting 2017-01-05 09:53:45 +08:00