Red Hat Bugzilla – Bug 1470282
[RFE] create an OVS bridge with an IP-carrying port on top of another connection
Last modified: 2018-04-10 09:28:56 EDT
Description of problem: OVN uses an OpenVSwitch bridge named br-int to connect its ports and do its have all its smart openflow rules. br-int is created and soly controlled by OVN. br-int can delegate its outgoing traffic either to a tunnel device, or to a simple-stupid OpenVSwitch bridge, e.g. brbond0, connected to a bonding device. The administrator of the host is responsible to create the latter bridge and connect it to the proper interface. In this RFE I am asking to let NM define such an interface. Just like NM is able to create a Linux bridge and connect it to an underlying connection, it should do the same for an OVS bridge. Just like it can set an IP address on a Linux bridge, I'm requesting to create a port on a the OVS bridge, and configure the address there. RHV does the latter on itself, but I believe that it would be better to implement this once, on the platform level. Note that unlike Linux bond, OVS does not need to be connected through a vlan device in order to tag all outgoing traffic. A better implementation would be to vlan-tag the underlying interface within the OVS bridge.
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=79168a54344f8fb72fda88bf02bce908d2ce3f31
This should work but it doesn't: nmcli conn add conn.type ovs-bridge conn.interface bridge0 nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0 nmcli conn add type ethernet conn.interface eth2 conn.master port1 slave-type ovs-port it works with dummy device: nmcli conn add conn.type ovs-bridge conn.interface bridge0 nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0 nmcli conn add type dummy conn.interface dummy0 conn.master port1 slave-type ovs-port
moving back to ON_QA as it looks blocking bug is fixed: bug 1519179
few bugs filed but generally working well, automated and running in CI.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0778