Bug 1470282 - [RFE] create an OVS bridge with an IP-carrying port on top of another connection
[RFE] create an OVS bridge with an IP-carrying port on top of another connection
Status: ON_QA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.3
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Lubomir Rintel
Desktop QE
: FutureFeature
Depends On:
Blocks: 1470965 1477926 1491326
  Show dependency treegraph
 
Reported: 2017-07-12 12:04 EDT by Dan Kenigsberg
Modified: 2017-11-08 04:56 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1491326 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Kenigsberg 2017-07-12 12:04:31 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.

Note You need to log in before you can comment on or make changes to this bug.