Bug 1042465

Summary:	[RFE][neutron]: Quantum SDN controler improvement
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-sdn-controler-improvement
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:26:33 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-12 22:22:05 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-sdn-controler-improvement.

Description:

At this time, the OpenStack networking project is designed to be interfaced with a third party controller which handles the “control plane” (NVP, Midonet, Ryu, Big Switch, Brocade, NEC, PLUMgrid)..
Nevertheless, it is also possible to use OpenStack Networking as the “control plane” (with LinuxBridge, OpenVSwitch, Cisco, Brocade). But has OpenStack Networking been developed with this role in mind, or is it mostly an interface between the networking API and the SDN control plane?


Specification URL (additional information):

https://wiki.openstack.org/wiki/Quantum-sdn-controler-improvement