1. Proposed title of this feature request
Handle machine network VLAN tagging using OVS

2. What is the nature and description of the request?

Many customers want to share their default host interface between management and VM traffic. This traffic is typically isolated by VLANs. Setting this up is non-trivial, as there are many different solutions to the issue, depending on the combination of interfaces and VLANs. This RFE suggests an enhancement to OVN Kubernetes, to make it VLAN aware, and enable us to have a single solution for all VLAN setups.

Users who want to connect their machine network to a VLAN need to define a VLAN interface and use it as a port of br-ex:

This however prevents localnet users from using br-ex to access other VLANs. To allow that, an additional OVS bridge must be created:

This could be avoided (no additional bridge, no VLAN interface), if OVN Kubernetes allowed us to define a VLAN tag it should use to access physical network. With that we would be able to achieve the following:

3. Why does the customer need this? (List the business requirements here)
To simplify host network setup. This kind of configuration with shared NIC for machine and VM network is usually requested by OpenShift Virtualization customers. This RFE is special in that the machine network is not using the native VLAN.

4. List any affected packages or components.
OVN Kubernetes
Host network configuration