Hi everyone,
in last week's meeting I took the action point to explain a bit about
the load balancing stuff I was referring to.
So, again the best reference we can take is RFC 7655 [1]. To my
knowledge the load balancing is performed by the network, that is, the
SFFs. There is no load balancing service function deployed. If you have
a look to sf3 in the picture below, it is deployed on several different
network points, attached to different sffs. This means that if you have
a Compute node 100% fully loaded of sf3 functions, you will be able to
spawn a new sf3 to a different Compute host, and load will be balanced
accordingly (criteria is dependent on the controller or the OpenFlow
rules deployed to SFFs).
Compare this schema with other alternatives such as having a Load
Balancer as Service Function. In this latter case this LB will become
single point of access for all the traffic, and if it gets loaded at
100% you will not be able to scale any more since all your traffic has
to go over this single LB.
+---+ +---+ +---+ +---+ +---+ +---+
|sf2| |sf2| |sf3| |sf3| |sf4| |sf4|
+---+ +---+ +---+ +---+ +---+ +---+
| | | | | |
+-----+-----+ +-----+-----+
| |
+ +
+----+ +----+ +----+ +----+ +----+
source+-->|sff1|+-->|sff2|+--->|sff3|+--->|sff4|+-->|sff5|+-->destination
+----+ +----+ +----+ +----+ +----+
+ + +
| | |
+---+ +---+ +---+
|sf1| |sf3| |sf5|
+---+ +---+ +---+
Figure 5: Load Balancing
Hope this helps.
Thanks,
Best Regards,
Miguel Ángel.
[1]https://tools.ietf.org/html/rfc7665
*** 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
