Bug 1042639

Summary:	[RFE][neutron]: VLAN aware VMs
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	chrisw, markmc, nyechiel, sgordon, yeylon
Target Milestone:	rc	Keywords:	FutureFeature, ZStream
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
Whiteboard:	upstream_milestone_newton-rc1 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-24 10:49:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-13 00:35:24 UTC

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

Comment 3 Nir Yechiel 2014-06-10 10:14:06 UTC

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.

Comment 4 Nir Yechiel 2014-08-27 13:04:56 UTC

The only way to achieve this at the moment is via the linux bridge driver, with a flat provider network configuration.

Comment 6 Nir Yechiel 2015-09-24 10:49:23 UTC

This was originally cloned from the upstream blueprint. Closing for now as there is no special reason to track it on Red Hat bugzilla.