Hide Forgot
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms. Description: This blueprint proposes how to incorporate VLAN aware VM:s into OpenStack. In this document a VLAN aware VM is a VM that sends and receives VLAN tagged frames over its vNIC. Specification URL (additional information): https://docs.google.com/document/d/1WEGmMJ4Vn21trgwa2_mpQ7U_a1BV2rKxlRzHqc49-9Y/edit?usp=sharing
There are two gaps in the current implementation that needs to be addressed by this blueprint: 1. API change - extending Neutron port to be able to connect to several Neutron networks. 2. OVS change - currently an instance is connected to the integration bridge (br-int) and that bridge is patched through to the bridge connected to the physical interface. OVS uses internal (local) VLAN tagging to separate traffic between different tenants on the hypervisor. As a result, any original VLAN tags that might exist on the frame before it passed to the Nova host are overwritten by OVS. Moreover, the existing OVS implementation allows to configure bridge ports in the access or trunk modes but Neutron does not know anything about port modes and ports created by Neutron have default mode which is "access". As a result, no VLAN tags are visible to VMs if they are connected through OVS bridges.
The only way to achieve this at the moment is via the linux bridge driver, with a flat provider network configuration.
This was originally cloned from the upstream blueprint. Closing for now as there is no special reason to track it on Red Hat bugzilla.