Hi Henry,
thanks for your answer. However if I run networking-sfc in OS with ODL
as backend, how can it work with two interfaces (ingress/egress) per vm?
Currently ODL does not support it, as per Manuel's answer.
BR,
Miguel Ángel.
On 14/11/17 16:46, Henry Fourie wrote:
Miguel
OpenStack networking-sfc does support SFs with separate ingress and egress
Neutron ports. A port-pair consists of an
ingress Neutron port and an egress Neutron port. Multiple port-pairs (SFs) with
similar functionality may be included
in a port-pair-group which is one stage in a SFC (port-chain). Each port-pair
group provides LB functionality across the SFs in the PPG.
Multiple PPGs make up a port-chain. Networking-sfc supports different back-end
implementations including OVS, ONOS, ODL.
https://docs.openstack.org/networking-sfc/latest/
- Louis
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Miguel Angel Muñoz
Sent: Monday, November 13, 2017 9:38 AM
To: [email protected]
Subject: [sfc-dev] More than one interface/data plane per SF
Hi everyone
I have a running demo of ODL with SFC where every SF has one single
network interface that connects it to one or several chains.
Is it possible to have a SF with two interfaces (egress/ingress) and have the
traffic in the chain being sent through one of them and received through the
other?
+---------+ +---------+
| Current | | Desired |
| | => | |
| | | |
+---------+ +---------+
| | |
| | |
+ + +
XXX XXXXXXX
XX XX XX XX
SC XXXXX XXXXX XXXX XXXX
The purpose of this is to allow a firewall to be placed as Service Function. In
this type of devices we need the traffic flowing from one interface to a
different one. I know this was not possible some months ago, but maybe this
feature has been already added recently?
I'm also curious to know why this is different to OpenStack + NetworkingSFC +
ODL: In this deployment openstack allows the SF to have an ingress and egress
port which can be placed on different interfaces/data plane locator.
Thank you very much,
Best Regards,
Miguel Ángel.
*** Please note that this message and any attachments may contain confidential
and proprietary material and information and are intended only for the use of
the intended recipient(s). If you are not the intended recipient, you are
hereby notified that any review, use, disclosure, dissemination, distribution
or copying of this message and any attachments is strictly prohibited. If you
have received this email in error, please immediately notify the sender and
destroy this e-mail and any attachments and all copies, whether electronic or
printed. Please also note that any views, opinions, conclusions or commitments
expressed in this message are those of the individual sender and do not
necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are
not binding on Fortinet and only a writing manually signed by Fortinet's
General Counsel can be a binding commitment of Fortinet to Fortinet's customers
or partners. Thank you. ***
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
