openstack/tricircle
Code Issues Proposed changes

Add 'extern' physical network create supported

Browse Source 
1. What is the problem
when creating an external network with provider physical
network specified as 'extern', central Neutron will complain
that the specified physical network is not found.

2. What is the solution to the problem
Add 'extern' as physical network to Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS
when init local neutron variables.

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

Change-Id: I3948bcc8b4498ad2f3a14679fbed9ce8ae3ad113
Closes-Bug: #1657634
This commit is contained in:
xiulin yin 2017-01-19 19:27:04 +08:00
parent 39ce96546b
commit fdbd26836a
3 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
devstack/local.conf.node_1.sample
View File

@ -26,7 +26,7 @@ ADMIN_PASSWORD=password
HOST_IP=10.250.201.24
Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS=(network_vlan_ranges=bridge:2001:3000)
Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS=(network_vlan_ranges=bridge:2001:3000,extern:3001:4000)
OVS_BRIDGE_MAPPINGS=bridge:br-vlan
# Specify Central Region name

5
devstack/plugin.sh
View File

@ -84,10 +84,7 @@ function init_local_neutron_variables {
local vlan_option="bridge:$TRICIRCLE_DEFAULT_VLAN_RANGE"
local ext_option="extern:$TRICIRCLE_DEFAULT_EXT_RANGE"
local vlan_ranges=(network_vlan_ranges=$vlan_option)
if [ "$TRICIRCLE_START_SERVICES" == "False" ]; then
vlan_ranges=(network_vlan_ranges=$vlan_option,$ext_option)
fi
local vlan_ranges=(network_vlan_ranges=$vlan_option,$ext_option)
Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS=$vlan_ranges
local vlan_mapping="bridge:$TRICIRCLE_DEFAULT_VLAN_BRIDGE"

10
doc/source/multi-pod-installation-devstack.rst
View File

@ -104,13 +104,17 @@ RegionOne,
(network_vlan_ranges=<physical network name>:<min vlan>:<max vlan>),
you can change physical network name, but remember to adapt your change
to the commands showed in this guide; also, change min VLAN and max vlan
to adapt the VLAN range your physical network supports::
to adapt the VLAN range your physical network supports. You need to
additionally specify the physical network "extern" to ensure the
central neutron can create "extern" physical network which located in
other pods::
Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS=(network_vlan_ranges=bridge:2001:3000)
Q_ML2_PLUGIN_VLAN_TYPE_OPTIONS=(network_vlan_ranges=bridge:2001:3000,extern:3001:4000)
- the format of OVS_BRIDGE_MAPPINGS is <physical network name>:<ovs bridge name>,
you can change these names, but remember to adapt your change to the
commands showed in this guide::
commands showed in this guide. You do not need specify the bridge mapping
for "extern", because this physical network is located in other pods::
OVS_BRIDGE_MAPPINGS=bridge:br-vlan