OVS without specifying separate bridge interfaces (ports) per vlan

[xed]

Hello,

I'm trying to configure a new system with the following properties:

1. One NIC exclusively for management, only gets untagged traffic (not used by VMs)
2. One 10G NIC used as a trunk for the VMs (no need to have an IP associated with it for the host)
3. One 10G NIC used as a storage/clustering link (not used by VMs)

I would like to take advantage of OVS to leverage things like span ports/mirroring and other features I (AFAIK) would not be supported by Linux bridges in the same fashion as OVS does (please correct me if I am wrong).

My ideal setup that I am trying to accomplish is:

• Ability to use all VLANs coming into the 10G trunk port without creating VLAN ports manually (because this requires reboots)
  • I want to be able to use the Tag field in the UI/API whenever I create guests or containers and have it work out of the box.
• Ability to mirror any of the ports associated with guests for the VLANs (I understand this might require me to "hard define" the port as a OVS bridge in /etc/network/interfaces)

Is this feasible? If it is, how can I adapt my configuration to make it work (or where can I get the information to learn this):

auto lo
iface lo inet loopback


iface eno2 inet manual


auto vmbr0
iface vmbr0 inet dhcp
        bridge-ports eno2
        bridge-stp off
        bridge-fd 0


iface eno1 inet manual


iface eno7 inet manual


# 10G trunk (no storage)
iface eno8 inet manual
        ovs_bridge vmbr1
        ovs_type OVSPort
        ovs_options tag=4522 vlan_mode=native-untagged


allow-ovs vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports eno8