From what I could gather looking at devstack/lib/neutron, if the following code lines in function “create_neutron_initial_netowrk"(shown below) are bypassed when $PUBLIC_BRIDGE is not set, it won’t bring up the bridge “br-ex” in the host running q-l3. It seems all the required steps needed to associate the l3-agent with user defined “external” network are there in devstack/lib/neutron.
Bypassing these two steps is all that is probably needed in devstack to take care of this bug? Is my assessment correct?
I am assuming users who want to use “external net” for connectivity to external world, would not set PUBLIC_BRIDGE variable in “local.conf”.
Lines of code:
function create_neutron_initial_network {
: sudo ip addr add $EXT_GW_IP/$CIDR_LEN dev $PUBLIC_BRIDGE sudo ip link set $PUBLIC_BRIDGE up
:
From what I could gather looking at devstack/ lib/neutron, if the following code lines in function “create_ neutron_ initial_ netowrk" (shown below) are bypassed when $PUBLIC_BRIDGE is not set, it won’t bring up the bridge “br-ex” in the host running q-l3. It seems all the required steps needed to associate the l3-agent with user defined “external” network are there in devstack/ lib/neutron.
Bypassing these two steps is all that is probably needed in devstack to take care of this bug? Is my assessment correct?
I am assuming users who want to use “external net” for connectivity to external world, would not set PUBLIC_BRIDGE variable in “local.conf”.
Lines of code:
function create_ neutron_ initial_ network {
sudo ip addr add $EXT_GW_ IP/$CIDR_ LEN dev $PUBLIC_BRIDGE
sudo ip link set $PUBLIC_BRIDGE up
:
: