Data plane manipulation in a load balancer

• US 9,871,731 B2
• Filed: 09/30/2015
• Issued: 01/16/2018
• Est. Priority Date: 09/30/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Bansal, Deepak, Outhred, Geoffrey Hugh, Venkataramaiah, Narasimhan Agrahara, Agarwal, Shekhar
• Primary Examiner(s): Moore, Jr., Michael J
• Application Number:
  US14/871,645
• Publication Number:
  US 20170093724A1
• Time in Patent Office: 839 Days
• Field of Search: None
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/147 for predicting network behaviour
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• 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/1023 based on a hash applied to IP addresses or costs

Abstract

A load balancer capable of adjusting how network data is distributed to a tenant or group of tenants by manipulating the data plane. The load balancer is placed directly in the flow path of network data that is destined for a tenant or group of tenants having a tenant address. The load balancer includes a control plane and one or more data planes. Each data plane may contain one or more network traffic multiplexors. Further, each data plane may be dedicated to a tenant or group of tenants. Data planes may be added or deleted from the load balancer; additionally, multiplexors may be added or deleted from a data plane. Accordingly, network data directed towards one tenant is less likely to affect the performance of load balancing performed for another tenant.

Claims

1. A system, the system comprising:

one or more tenants, each tenant or group of tenants having a tenant address;

a source configured to receive one or more network data destined for one or more tenant addresses assigned to a tenant or group of tenants; and

a load balancer configured to receive the one or more network data from the source and to distribute the one or more network data to the tenant address assigned to the tenant or group of tenants, the load balancer being in the data flow path of the one or more network data, the load balancer comprising;

a control plane, the control plane being configured to perform one or more of the following acts;

an act of instantiating one or more data planes;

an act of deleting one or more data planes; and

an act of determining when changes are to be made to one or more data planes within a plurality of data planes; and

the plurality of data planes, the plurality of data planes including a first data plane and a second data plane, the first and second data planes each having a plurality of multiplexers (MUXes), wherein one or both of the first or second data planes performs two or more of the following acts when the control plane determines that a change is to be made;

an act of instantiating one or more MUXes within at least one of the first or second data planes;

an act of destroying one or more MUXes from within at least one of the first or second data planes;

an act of dedicating the first data plane to a first tenant or group of tenants; and

an act of dedicating the second data plane to a second tenant or group of tenants, wherein the first and second data plane provide network data isolation from each other.

2. The system in accordance with claim 1, wherein the plurality of MUXes within at least one of the first and second data planes are configured identically.

3. The system in accordance with claim 1, wherein the control plane comprises a first partition and a second partition, the first partition serving as a primary control for the first data plane and the second partition serving as a backup control for the first data plane, the first partition further serving as a backup control for the second data plane and the second partition further serving as the primary control for the second data plane.

4. The system in accordance with claim 1, wherein the source is an edge router.

5. The system in accordance with claim 1, wherein the tenant address includes a virtual IP (VIP) address.

6. The system in accordance with claim 1, wherein the first data plane may be used to sink network data for a tenant address subject to a denial of service attack.

7. The system in accordance with claim 1, wherein the number of MUXes in the first data plane is selected based on an expected load or throughput.

8. The system in accordance with claim 1, wherein the system is in a cloud computing environment.

9. The system in accordance with claim 1, wherein the system is in a distributed environment.

10. A method for a load balancer to modify a distribution of network data, the load balancer comprising a data plane having one or more multiplexers (MUXes), the data plane corresponding to a tenant or group of tenants, the corresponding data plane being placed in a data path of network data being transmitted from one or more sources to one or more tenant addresses of the corresponding tenant or group of tenants, the method comprising:

an act of monitoring a measurement of the distribution of the network data imposed by the load balancer in delivering the network data through the corresponding data plane to the tenant or group of tenants;

an act of comparing the measurement of the distribution of the network data imposed by the load balancer via the corresponding data plane with a selected distribution selected to be imposed by the load balancer in delivering the network data via the corresponding data plane to the tenant or group of tenants; and

an act of modifying the distribution of the network data imposed by the load balancer in delivering network data via the corresponding data plane to the tenant or group of tenants to compensate for at least some variation between the compared distributions of the network data by adding one or more MUXes or removing one or more MUXes to the corresponding data plane.

11. The method in accordance with claim 10, wherein the tenant address includes a virtual IP (VIP) Address.

12. The method in accordance with claim 10, wherein the one or more MUXes within the corresponding data plane are configured identically.

13. The method in accordance with claim 10, wherein the source is an edge router.

14. The method in accordance with claim 10, wherein the tenant address includes a VIP address.

15. The method in accordance with claim 10, wherein the load balancer further includes a control plane, the control plane comprising a first partition and a second partition, the first partition serving as a primary control for a first data plane and the second partition serving as a backup control for the first data plane, the first partition further serving as a backup control for a second data plane and the second partition further serving as the primary control for the second data plane.

16. A method for a load balancer to modify a distribution of network data, the load balancer comprising one or more data planes each having one or more multiplexers (MUXes), at least one of the one or more data plane corresponding to a tenant or group of tenants, the corresponding data plane being placed in a data path of network data being transmitted from one or more sources to one or more tenant addresses of the corresponding tenant or group of tenants, the method comprising:

an act of adding one or more data planes to the load balancer, each of the one or more data planes having one or more MUXes;

and act of removing one or more data planes from the load balancer, each of the one or more data planes having one or more MUXes;

an act of dedicating the added one or more data planes to a tenant or group of tenants; and

an act of routing a network data destined for the tenant or group of tenants through the newly added one or more data planes.

17. The method in accordance with claim 16, wherein the load balancer further includes a control plane, the control plane programming the one or more data planes, the control plane having a first partition and a second partition, the first partition serving as a primary control for a first data plane and the second partition serving as a backup control for the first data plane, the first partition further serving as a backup control for a second data plane and the second partition further serving as the primary control for the second data plane.

18. The method in accordance with claim 17, wherein the control plane performs one or more of the following acts:

an act of monitoring the health of the data plane;

an act of monitoring the health the MUXes within the one or more data planes; and

an act of monitoring the health of the tenant or group of tenants being load balanced.

19. The method in accordance with claim 17, wherein the control plane programs the one or more data planes to announce network routes.

20. The method in accordance with claim 16, wherein the first data plane may be used to filter network data for a tenant address.