Hide Forgot
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
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.
Updating based on upstream milestone
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.