Add support for existing bridges in data-port config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
In Progress
|
Undecided
|
Michael Skalka |
Bug Description
Currently the data port option does not allow support for existing bridges. With the current behavior NG will add the supplied bridge to OVS without checking if it is used or not, which results in a loss of network connectivity unexpectedly. This behavior is undesirable in circumstances where there are a limited number of physical interfaces available.
This can be worked around by instead adding a veth pair using an existing bridge and the desired OVS bridge and adding the veth-<existing-
For example, using the data-port config "br-data:br-bond0" where br-bond0 exists on the NG node would result in the following OVS configuration:
Bridge br-data
Controller "tcp:127.
fail_mode: secure
Port br-data
Port "veth-br-bond0"
Port phy-br-data
The OVS charm already supports this functionality through charmhelpers/
Changed in charm-neutron-gateway: | |
assignee: | nobody → Michael Skalka (mskalka) |
tags: | added: cpe-onsite |
Changed in charm-neutron-gateway: | |
status: | New → In Progress |
This was previously addressed in https:/ /bugs.launchpad .net/charms/ +source/ neutron- openvswitch/ +bug/1635067 however the implementation was never carried over to the NG charm. Additionally the fix has since broken, as reported in https:/ /bugs.launchpad .net/charm- helpers/ +bug/1761840