Bug 1127059

Summary:	[RFE][neutron]: Enhancement in schema of ml2 network segment table for Multi-Segment Network
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/schema-enhancement-to-support-multisegment-network
Whiteboard:	upstream_milestone_none upstream_definition_new upstream_status_implemented
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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-08-06 04:05:41 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/schema-enhancement-to-support-multisegment-network.

Description:

Currently, there is nothing in the schema that ensures segments for a network are returned in the same order they were specified when the network was created, or even in a deterministic order.

This blueprint proposes a solution to address the above mentioned problem.

Specification URL (additional information):

https://review.openstack.org/#/c/110558/