Hi, On Mon, 2017-11-13 at 18:38 +0100, Miguel Angel Muñoz wrote: > 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 don't think this feature is currently available, but I might be wrong > > 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. The e2e integration requires that ODL supports it and as I said above, I don't think it does. Therefore, it should not work even if it is available in the networking-sfc API. > > 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
