Neutron Services Insertion, Chaining, and Steering
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:/
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Medium
- Drafter:
- Sumit Naiksatam
- Direction:
- Needs approval
- Assignee:
- Sumit Naiksatam
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Needs Code Review
- Milestone target:
- None
- Started by
- Thierry Carrez
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
August-22 (mestery): This is an umbrella BP with no code, moving out of Juno to clean things up per discussion with ttx last week.
15-July (mestery): Moving this to Juno-3 as this is the umbrella BP and has no code associated with it.
27-May (mestery): Moving to Juno-2, this is unlikely to land in Juno-1.
6-Mar (markmcclain): Deferring to Juno
Sumit (Dec-13) - Updated the google doc based on feedback during the summit, and per discussion with Nachi. Major change, not modeling the insertion_context as a separate resource, but as an attribute for each logical service instance.
Gerrit topic: https:/
Addressed by: https:/
Implements: blueprint fwaas-service-
Sumit (Feb 19): currently the service context insertion is being addressed. Service chain will be a follow up patch but won't make it for Icehouse3
Gerrit topic: https:/
Addressed by: https:/
Advanced Services Common Framework
Work Items
Dependency tree
* Blueprints in grey have been implemented.