[openstack-dev] [neutron] Query about re-directing incoming traffic.

Vikram Choudhary vikschw at gmail.com
Tue Dec 29 10:29:01 UTC 2015


On Tue, Dec 29, 2015 at 3:08 PM, Neil Jerram <Neil.Jerram at metaswitch.com>
wrote:

> On 28/12/15 16:16, Vikram Choudhary wrote:
> > Hi All,
> >
> > We want to redirect all / some specific incoming traffic to a
> > particular neutron port, where a network function is deployed.
> > [Network function could be DPI, IDS, Firewall, Classifier, etc]. In
> > this regard, we have few queries:
>
> Isn't that what SFC is?  (Service Function Chaining.)
>
Vikram: Kind-off. SFC chains neutron ports but our requirement is to route
all the incoming traffic to a particular VM port before it can take it's
normal forwarding logic. In other words neutron router got to steer the
traffic to a VM and then to it's normal forwarding behaviour.

An important use-case could be deploying a separate classifier at the
ingress which filters traffic and then route to respective service chains
depending upon some logic [May be SF-ID can be stamped in packet as part of
NSH header or by some other means.]


> Regards,
>     Neil
>
> >
> > 1. How we can achtieve this?
> >
> > 2. Do we have well-defined NBI's for such use-case?
> >
> > Any thought / suggestion will be appreciated.
> >
> > Thanks
> > Vikram
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151229/c23a3f73/attachment.html>


More information about the OpenStack-dev mailing list