feature: support use of bridges via veth pairs for openvswitch data port configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
In Progress
|
Medium
|
Unassigned | ||
OpenStack Neutron Gateway Charm |
Fix Released
|
Medium
|
James Page | ||
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Medium
|
Aymen Frikha | ||
neutron-openvswitch (Juju Charms Collection) |
Invalid
|
Medium
|
Aymen Frikha |
Bug Description
When configuring vlan provider networks in neutron, it is currently required to set data-port=
Some users don't have an additional interface to leave unconfigured to use as data-port.
When using neutorn vlan provider networks which are trunked to the management interface, we found that the neutron-openvswitch charm runs 'ovs-vsctl add-port br-ex bond0', but that command fails with 'device busy'
We found the following solution which creates a veth pair between veth-br-bond0 and veth-tenant which allows both containers to br-bond0 but also neutron vlan provider networks to function.
on each compute node
# create veth pair between br-bond0 and veth-tenant
ip l add name veth-br-bond0 type veth peer name veth-tenant
# set mtu if needed on veth interfaces and turn up
#ip l set dev veth-br-bond0 mtu 9000
#ip l set dev veth-tenant mtu 9000
ip l set dev veth-br-bond0 up
ip l set dev veth-tenant up
# add br-bond0 as master for veth-br-bond0
ip l set veth-br-bond0 master br-bond0
juju set neutron-openvswitch data-port=
Should something like this be added to the neutron-openvswitch charm to allow neutron vlan provider networks on the management interface?
Related branches
- Jorge Niedbalski (community): Approve
- Matt Rae (community): Needs Resubmitting
- James Page: Needs Fixing
- Billy Olsen: Needs Fixing
- Edward Hope-Morley: Pending requested
-
Diff: 104 lines (+69/-1)2 files modifiedcharmhelpers/contrib/network/ovs/__init__.py (+49/-1)
tests/contrib/network/test_ovs.py (+20/-0)
tags: | added: cpec |
Changed in neutron-openvswitch (Juju Charms Collection): | |
assignee: | nobody → Aymen Frikha (aym-frikha) |
Changed in neutron-openvswitch (Juju Charms Collection): | |
status: | New → Confirmed |
Changed in neutron-openvswitch (Juju Charms Collection): | |
status: | Confirmed → In Progress |
tags: | added: openstack sts |
Changed in neutron-openvswitch (Juju Charms Collection): | |
importance: | Undecided → Medium |
summary: |
- sharing management interface with vlan provider networks + feature: support use of bridges via veth pairs for openvswitch data port + configuration |
Changed in charm-helpers: | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in neutron-openvswitch (Juju Charms Collection): | |
milestone: | none → 17.01 |
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → Aymen Frikha (aym-frikha) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in neutron-openvswitch (Juju Charms Collection): | |
status: | In Progress → Invalid |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 17.08 |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
tags: |
added: cpe-onsite removed: cpec |
Changed in charm-neutron-gateway: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → James Page (james-page) |
Changed in charm-neutron-gateway: | |
milestone: | none → 18.05 |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
I also tested it with flat provider network, and it seems that we have the same issue. The solution provided by Matt works for me also. It seems that the OVS bridge can't use an interface which is already connected to a linuxbridge.