Bug 1042458

Summary:	[RFE][neutron]: Neutron Services Insertion, Chaining, and Steering
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aortega, chrisw, derekh, lpeer, markmc, nyechiel, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering
Whiteboard:	upstream_milestone_none upstream_status_needs-code-review upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 11:05:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1093835

Description RHOS Integration 2013-12-12 22:20:57 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering.

Description:

In Havana we took a significant step forward with addition of multiple advance network services. Currently we have support for FWaaS, LBaaS, and VPNaaS. However the association of these services with other neutron constructs either happens implicitly or to a virtual router. In other words there is no generic service insertion mechanism to facilitate L3, L2, bump-in-the-wire, and tap insertion modes. Moreover, with more than one service it becomes relevant to explore the model of how multiple services can be requested and sequenced in a chain.

Work items
- Defining the resource abstractions and CRUD operations
- SQLAlchemy data model

More details on the design specification in this document:
https://docs.google.com/document/d/1fmCWpCxAN4g5txmCJVmBDt02GYew2kvyRsh0Wl3YF2U/edit#

Specification URL (additional information):

https://wiki.openstack.org/wiki/Quantum/ServiceInsertionAndChaining

Comment 2 lpeer 2014-01-23 17:42:44 UTC

After looking into this topic it seems like the service insertion can wait as there are much more urgent issues to handle for Icehouse cycle.

Comment 3 Nir Yechiel 2014-03-09 09:32:54 UTC

Updating based on upstream milestone

Comment 4 Nir Yechiel 2015-03-19 11:05:57 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.