Bug 1118131

Summary:	[RFE][neutron]: ML2 Hierarchical Port Binding
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	lpeer <lpeer>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	chrisw, markmc, nyechiel, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 11:48:50 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-07-10 04:04:02 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding.

Description:

Support hierarchical network topologies by binding ports to ML2 mechanism drivers and network segments at each necessary level of the hierarchy. For example, one mechanism driver might bind to a static VXLAN segment of the network, causing a ToR switch to expose that network as a dynamically allocated VLAN to the compute node(s) connected to that switch, while a second mechanism driver, such as OVS, would bind the compute node to that VLAN.

Specification URL (additional information):

None

Comment 1 Nir Yechiel 2015-03-19 11:48:50 UTC

This RFE was automatically opened to track status of upstream development. At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.