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.