Bug 1042617

Summary:	[RFE][neutron]: Network Segment Translation
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/quantum-network-segment-translation
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:19:55 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:31:20 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-network-segment-translation.

Description:

If a Quantum network is composed of multiple different types of segments, we need a way for the provider to setup a mapping between the segments. Take for example the case of VXLAN. To map a VXLAN segment to the physical world, it's likely to have to go out a VLAN. This blueprint covers the ability for the provider to provider the intent for this VXLAN:VLAN mapping, in this example. This blueprint is not limited to any particular type of segmentation technology.

Specification URL (additional information):

None