Load balancing across a group of load balancers

• US 9,531,590 B2
• Filed: 12/12/2014
• Issued: 12/27/2016
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Jain, Jayant, Sengupta, Anirban, Parthasarathy, Mohan
• Primary Examiner(s): Alia, Curtis A
• Assistant Examiner(s): Lalchinthang, Vanneilian
• Application Number:
  US14/569,249
• Publication Number:
  US 20160094453A1
• Time in Patent Office: 746 Days
• Field of Search: 370/235
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/7453 using hashing
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/6225 Fixed service order, e.g. Round Robin
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Some embodiments provide an elastic architecture for providing a service in a computing system. To perform a service on the data messages, the service architecture uses a service node (SN) group that includes one primary service node (PSN) and zero or more secondary service nodes (SSNs). The service can be performed on a data message by either the PSN or one of the SSN. However, in addition to performing the service, the PSN also performs a load balancing operation that assesses the load on each service node (i.e., on the PSN or each SSN), and based on this assessment, has the data messages distributed to the service node(s) in its SN group. Based on the assessed load, the PSN in some embodiments also has one or more SSNs added to or removed from its SN group. To add or remove an SSN to or from the service node group, the PSN in some embodiments directs a set of controllers to add (e.g., instantiate or allocate) or remove the SSN to or from the SN group. Also, to assess the load on the service nodes, the PSN in some embodiments receives message load data from the controller set, which collects such data from each service node. In other embodiments, the PSN receives such load data directly from the SSNs.

Claims

1. A load balancing system for load balancing data messages sent to a group of destination compute nodes (DCNs), the system comprising:

a load balancer (LB) group comprising a primary load balancer (PLB) and at least one secondary load balancer (SLB),

the PLB for (i) receiving new data message flows for the DCN group, (ii) using layer 2 (L2) header parameters of the data message flows to identify at least one load balancing rule including a first set of load balancing parameters to evaluate in a first-type load balancing operation to identify an LB in the LB group for each data message flow, and, (iii) using data message header parameters that are for layers higher than layer 2 to identify at least one load balancing rule including a second set of load balancing parameters evaluated in a second-type load balancing operation to identify a DCN in the DCN group for each data message flow for which the PLB identifies the PLB as the identified load balancer, and

the SLB for distributing to the DCNs the data messages of each flow for which the PLB identifies the SLB as the identified load balancer.

2. The load balancing system of claim 1,

wherein the second load balancing parameter set includes a hash table that includes a plurality of hash ranges and a DCN identifier for each hash range that identifies the DCN associated with the hash range, and

wherein the second-type load balancing operation generates a hash value for a data message flow, identifies the hash range that contains the generated hash value, and designates for the flow the DCN of the identified hash range as the DCN that should receive the data message flow.

3. The load balancing system of claim 1,

wherein the first load balancing parameter set includes a set of load balancing criteria that that the first-type load balancing operation evaluates to select LBs for the data message flows in a round-robin manner.

4. The load balancing system of claim 1,

wherein the second load balancing parameter set includes a set of load balancing criteria that the second-type load balancing operation evaluates to select DCNs for the data message flows in a round-robin manner.

5. The load balancing system of claim 1, wherein the PLB directs a data message that the SLB should process to the SLB by changing the destination media access control (MAC) address of the data message to the MAC address of the SLB.

6. The load balancing system of claim 1, wherein the PLB directs a data message that the SLB should process by changing the destination Internet Protocol (IP) address of the data message from a virtual IP (VIP) address of the LB group to the IP address of the SLB.

7. The load balancing system of claim 6, wherein the VIP address is the IP address of the PLB.

8. The load balancing system of claim 1 further comprising a front end load balancer for sending data messages of new data message flows to the PLB, for being configured by the PLB with the identity of each load balancer in the LB group that the PLB identifies to process each data message flow, and for directing the data messages of each data message flow to the identified load balancer after being configured by the PLB for the data message flow.

9. The load balancing system of claim 1, wherein the LB group further includes at least one other SLB.

10. The load balancing system of claim 9 further comprising:

a plurality of host computing devices,

wherein each load balancer includes a module that executes on a host computing device; and

wherein at least two modules of two load balancers execute on the same host computing device.

11. The load balancing system of claim 10,

wherein the module of each load balancer is a service virtual machine (SVM) that executes on a host computing device and that distributes to a DCN the data messages in each flow for which the load balancer is identified by the PLB as the load balancer that has to distribute the flow'"'"'s data messages to the DCN;

and

wherein in addition to the PLB'"'"'s SVM, the PLB further includes an inline load balancer that intercepts data messages from the data path of the PLB'"'"'s SVM and performs the first-type load balancing operation to identify a load balancer for each flow.

12. A non-transitory machine readable medium of a primary load balancing node (LBN), the medium storing a program for load balancing data messages for a group of destination compute nodes (DCNs), the program comprising sets of instructions for:

receiving a data message that is part of a data message flow;

using a first subset of header parameters of the received data message to identify a first load balancing rule including a first set of load balancing criteria to evaluate in a first-type load balancing operation to identify an LBN in an LBN group to process data messages that are in the same flow as the received data message, said group comprising the primary LBN;

when the first-type load balancing operation identifies the primary LBN for processing the received data message, using a second subset of header parameters of the received data message to identify a second load balancing rule with a second set of load balancing criteria, evaluating the second set of load balancing criteria to identify a DCN in the DCN group and directing to the identified DCN the received data message and other data messages of the data message flow; and

when the first-type load balancing operation identifies a second LBN in the LBN group for processing the received data message, directing the received data message and other data messages that are part of the data message flow to the second LBN for the second LBN to identify a DCN in the DCN group for the received data message and the other data messages of the data message flow.

13. The non-transitory machine readable medium of claim 12, wherein the program further comprises sets of instructions for configuring a set of front-end load balancers to direct data messages that are in the same data message flow as the received data message to the second LBN when the second LBN is identified as the LBN for the received data message'"'"'s flow.

14. The non-transitory machine readable medium of claim 12, wherein the set of instructions for directing the received data message flow to the second LBN comprises sets of instructions for:

replacing an address in the received data message with an address of the second LBN; and

supplying the data message to a forwarding element to forward the data message to the second LBN.

15. The non-transitory machine readable medium of claim 12,

wherein the second set of load balancing criteria includes a hash table that includes a plurality of hash ranges and a DCN identifier for each hash range that identifies the DCN associated with the hash range, and

wherein the second-type load balancing operation generates a hash value for a data message flow, identifies the hash range that contains the generated hash value, and designates for the flow the DCN of the identified hash range as the DCN that should receive the data message flow.

16. The non-transitory machine readable medium of claim 12,

wherein the first set of load balancing criteria are evaluated to select LBNs for the data message flows in a round-robin manner.

17. The non-transitory machine readable medium of claim 12,

wherein the second set of load balancing criteria are evaluated to select DCNs for the data message flows in a round-robin manner.

18. The non-transitory machine readable medium of claim 12,

wherein the LBN group further includes at least one other LBN.

19. The non-transitory machine readable medium of claim 14, wherein the set of instructions for replacing an address in the received data message with an address of the second LBN comprises a set of instructions for changing the destination media access control (MAC) address of the data message to the MAC address of the second LBN.

20. The non-transitory machine readable medium of claim 14, wherein the set of instructions for replacing an address in the received data message with an address of the second LBN comprises a set of instructions for changing the destination Internet Protocol (IP) address of the data message from a virtual IP (VIP) address of the LBN group to the IP address of the second LBN.