Bug 1104931

Summary:	[RFE][neutron]: VLAN trunking networks for NFV - API change (not available in OVS)
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	Brent Eagles <beagles>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	chrisw, huhuang, jraju, jschluet, lpeer, markmc, nyechiel, oblaut, rpai, tfreger, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	x86_64
OS:	Linux
URL:	https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-neutron-2015.1.0-11.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:12:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-06-05 04:08:33 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks.

Description:

Enable creation of VLAN transparent networks, a major blocker for NFV use cases

Specification URL (additional information):

None

Comment 1 Nir Yechiel 2015-02-16 16:35:04 UTC

Two specs were filed for Kilo trying to address the VLAN trunk into a VM use case. This one that got approved is talking only about the ability to flag (in the network API) a network to indicate that a transparent transport is required. 

Other blueprints propose solutions to decomposing trunks into networks from its individual VLANs, address management on trunk networks (i.e., using sub-ports), and so on. This makes no attempt to address anything other than the simple L2 properties of networks. This spec addresses different use cases to those that deal with management of ports by OpenStack - specifically, the case where two VLAN-aware VMs wish to talk to each other over a number of VLANs, possibly with tags that change over time, and without informing OpenStack at each stage of which VLANs and addresses are in use.

This solution is not compatible with current Open vSwitch implementation, and does not seem to address any specific implementation other than the API change.

Comment 2 Toni Freger 2015-05-03 06:55:40 UTC

Feature still not available in OVS.
Unable to test API changes.

Comment 5 Eran Kuris 2015-07-20 07:13:55 UTC

Verified in 
# rpm -qa |grep openstack-neutron
openstack-neutron-common-2015.1.0-12.el7ost.noarch
openstack-neutron-ml2-2015.1.0-12.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-2015.1.0-12.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-12.el7ost.noarch
[root@puma15 ~(keystone_admin)]# 

The new code exist

Comment 7 errata-xmlrpc 2015-08-05 13:12:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548