IP Library Granted Patent US 11,805,051
Granted Patent B2
US 11,805,051 · App. 17/344,956 · Granted Oct 31, 2023

Allocating additional bandwidth to resources in a datacenter through deployment of dedicated gateways

Inventors: Ganesh Sadasivan (Fremont, CA); Chidambareswaran Raman (Sunnyvale, CA); Dileep K. Devireddy (San Jose, CA); Hongwei Zhu (Mountain View, CA); Sreenivas Duvvuri (San Ramon, CA)
Assignee: VMWARE, INC.
H04L45/38H04L45/24H04L45/42H04L45/44H04L45/586H04L45/72H04L45/74H04L47/762H04L47/781H04L47/801H04L47/803
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,805,051
App. No.
17/344,956
Granted
Oct 31, 2023
Kind
B2
Abstract

Some embodiments provide policy-driven methods for deploying edge forwarding elements in a public or private SDDC for tenants or applications. For instance, the method of some embodiments allows administrators to create different traffic groups for different applications and/or tenants, deploys edge forwarding elements for the different traffic groups, and configures forwarding elements in the SDDC to direct data message flows of the applications and/or tenants through the edge forwarding elements deployed for them. The policy-driven method of some embodiments also dynamically deploys edge forwarding elements in the SDDC for applications and/or tenants after detecting the need for the edge forwarding elements based on monitored traffic flow conditions.

Claims (31)

1. A method of deploying edge forwarding elements in a multi-tenant software defined datacenter (SDDC), the method comprising:

deploying, for a tenant, a first edge forwarding element to process data message flows associated with the tenant;

detecting that the data message flows associated with the tenant consume more than a threshold amount of bandwidth;

based on a policy that specifies allocation of additional bandwidth for data message flows associated with the tenant when the data message flows consume more than the threshold amount, determining that additional bandwidth needs to be allocated for the data message flows associated with the tenant in response to said detecting, wherein the additional bandwidth is for data message flows between a first set of machines in a first network and a second set of machines in a second network external to the first network and the data message flows are data message flows entering or exiting the first network; and

deploying, for the tenant, a second edge forwarding element to process at least a portion of the data message flows associated with the tenant in order to allocate more bandwidth to the tenant, wherein deploying the second edge forwarding element comprises (i) configuring the second edge forwarding element to forward a first subset of the portion of the data message flows to forwarding elements in the external second network and (ii) configuring a set of forwarding elements in the first network to forward the first subset of the data message flows from the first set of machines in the first network to the second edge forwarding element.

2. The method of claim 1 , wherein the first edge forwarding element continues to process a first set of data message flows associated with the tenant, while the second edge forwarding element processes a second set of data message flows associated with the tenant.

3. The method of claim 2 , wherein the first and second sets of data message flows are for two different machines of the tenant that execute in the SDDC.

4. The method of claim 2 , wherein the first and second sets of data message flows are for two different instances of an application that executes in the SDDC for the tenant.

5. The method of claim 2 , wherein the first and second sets of data message flows are for two different components of a multi-component application that executes in the SDDC for the tenant.

6. The method of claim 2 , wherein said deploying, detecting, and determining operations are performed by a set of one or more controllers.

7. The method of claim 1 , wherein configuring the set of forwarding elements in the first network comprises configuring the set of forwarding elements to forward to the second edge forwarding element data message flows with (i) destination IP addresses that are associated with the second edge forwarding element and (ii) source IP addresses associated with the first set of machines for which the additional bandwidth was allocated.

8. The method of claim 7 further comprising configuring a gateway of the SDDC to forward data message flows with destination IP addresses associated with the first set of machines to the second edge forwarding element.

9. The method of claim 1 , wherein:

the edge forwarding elements are edge routers; and

configuring the second edge forwarding element comprises configuring the second edge forwarding element to advertise to forwarding elements in the external, second network routes to the first set of machines.

10. The method of claim 1 , wherein:

the set of forwarding elements comprises a set of intervening routers; and

configuring the set of forwarding elements comprises providing next-hop forwarding rules to the set of intervening routers.

11. The method of claim 1 , wherein:

the set of forwarding elements comprises a set of intervening switches that implement a logical switch; and

configuring the set of forwarding elements comprises providing forwarding rules to the set of intervening switches to direct the switches to forward data messages of the first set to the second edge forwarding element through a set of tunnels that connect the set of intervening switches to the second edge forwarding element.

12. The method of claim 1 , wherein:

the SDDC is a public cloud datacenter having the external second network;

the first network is a private network that is defined in the second network to implement a virtual private cloud (VPC) for the tenant in the public cloud datacenter; and

deploying the second edge forwarding element comprises:

deploying a gateway in the public cloud datacenter to serve as the second edge forwarding element for the VPC; and

configuring a set of forwarding elements in the second network to forward a second subset of the portion of the data message flows from outside of the VPC to the deployed gateway.

13. The method of claim 1 , wherein deploying the first and second edge forwarding elements comprises deploying the first and second edge forwarding elements on different devices in the SDDC.

14. The method of claim 13 , wherein the different devices are first and second host computers on which the first and second edge forwarding elements execute.

15. The method of claim 1 , wherein the SDDC comprises a public cloud datacenter providing compute resources for a plurality of tenants.

16. The method of claim 1 , wherein the SDDC is a private datacenter of an entity and the tenants are different sub-entities associated with the entity.

Assignments (3)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
CHANGE OF NAME Recorded Feb 27, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 066692/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2021
From: SADASIVAN, GANESH; RAMAN, CHIDAMBARESWARAN; DEVIREDDY, DILEEP K.; ZHU, HONGWEI; DUVVURI, SREENIVAS
To: VMWARE, INC.
Reel/Frame 056511/0185 →