Difference between revisions of "Neutron/ServiceInsertionAndChaining"
< Neutron
m (ThierryCarrez moved page Quantum/ServiceInsertionAndChaining to Neutron/ServiceInsertionAndChaining) |
(→Overview) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
| − | + | 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. | |
== Current Design Discussions == | == Current Design Discussions == | ||
# API and Resource Model Document [[Quantum/ServiceInsertionAndChaining/API]] | # API and Resource Model Document [[Quantum/ServiceInsertionAndChaining/API]] | ||
Revision as of 20:46, 6 October 2013
Overview
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.
Current Design Discussions
- API and Resource Model Document Quantum/ServiceInsertionAndChaining/API
