Network Resource Governance in Multi-Tenant Datacenters

• US 20160094413A1
• Filed: 09/30/2014
• Published: 03/31/2016
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jain, Navendu
• Granted Patent: US 10,230,591 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/5019 Ensuring fulfilment of SLA
• CPC Class Codes: H04L 47/52 by attributing bandwidth to queues
• CPC Class Codes: H04L 47/525 by redistribution of residual bandwidth

Abstract

Bandwidth requirement specifications in a multi-tenant datacenter are implemented using resource-bundle level queues and tenant level queues. Data is transmitted via the resource-bundle level queues and the tenant level queues according to the bandwidth requirement specifications, such that minimum bandwidth requirements are maintained for data being transmitted and for data being received.

Claims

1. A method, comprising:

receiving a bandwidth requirement specification for a tenant, the tenant having one or more resource bundles; and

for an individual resource bundle of the one or more resource bundles;

implementing an inbound queue associated with the resource bundle, wherein a rate at which data is received through the inbound queue is determined according to the bandwidth requirement specification, the inbound queue being utilized to receive data; and

implementing an outbound queue associated with the resource bundle, wherein a rate at which data is sent through the outbound queue is determined according to the bandwidth requirement specification, the outbound queue being utilized to send data.

2. A method as recited in claim 1, wherein at least one resource bundle of the one or more resource bundles comprises a virtual machine.

3. A method as recited in claim 1, wherein:

the one or more resource bundles comprises a first group of resource bundles;

the bandwidth requirement specification is a first bandwidth requirement specification;

the tenant has associated therewith a second group of one or more resource bundles;

receiving a second bandwidth requirement specification for the tenant; and

for an individual resource bundle of the second group of resource bundles;

implementing an inbound queue associated with the resource bundle, wherein a rate at which data is received through the inbound queue is determined according to the second bandwidth requirement specification, the inbound queue being utilized to receive data; and

implementing an outbound queue associated with the resource bundle, wherein a rate at which data is sent through the outbound queue is determined according to the second bandwidth requirement specification, the outbound queue being utilized to send data.

4. A method as recited in claim 1, wherein:

the bandwidth requirement specification indicates a total bandwidth for the resource bundle; and

the inbound queue associated with the resource bundle and the outbound queue associated with the resource bundle are implemented such that, at any given time, a sum of a bandwidth available for use by the inbound queue associated with the resource bundle and a bandwidth available for use by the outbound queue associated with the resource bundle supports the total bandwidth for the resource bundle indicated in the bandwidth requirement specification.

5. A method as recited in claim 1, wherein:

the bandwidth requirement specification indicates a total bandwidth for the tenant; and

the inbound queues associated with each resource bundle of the one or more resource bundles and the outbound queues associated with each resource bundle of the one or more resource bundles are implemented such that, at any given time, a sum of a bandwidth available for use by the inbound queues associated with the one or more resource bundles and a bandwidth available for use by the outbound queues associated with the one or more resource bundles supports the total bandwidth for the tenant indicated in the bandwidth requirement specification.

6. A method as recited in claim 1, wherein:

the bandwidth requirement specification indicates an inbound bandwidth for the resource bundle and an outbound bandwidth for the resource bundle;

the inbound queue associated with the resource bundle is implemented such that, at any given time, a bandwidth available for use by the inbound queue associated with the resource bundle supports the inbound bandwidth for the resource bundle indicated in the bandwidth requirement specification; and

the outbound queue associated with the resource bundle is implemented such that, at any given time, a bandwidth available for use by the outbound queue associated with the resource bundle supports the outbound bandwidth for the resource bundle indicated in the bandwidth requirement specification.

7. A method as recited in claim 1, further comprising:

implementing a tenant-level inbound queue associated with the tenant for receiving data from resources not associated with the tenant; and

implementing a tenant-level outbound queue associated with the tenant for sending data to resources not associated with the tenant.

8. A method as recited in claim 7, further comprising:

receiving a request to transmit data from the resource bundle associated with the tenant to another entity;

in an event that the other entity is another resource bundle associated with the tenant, utilizing the outbound queue associated with the resource bundle to transmit the data; and

in an event that the other entity is not another resource bundle associated with the tenant, utilizing the tenant-level outbound queue to transmit the data.

9. A method as recited in claim 8, further comprising:

in the event that the other entity is another resource bundle associated with the tenant, transmitting the data to an inbound queue of the other resource bundle associated with the tenant.

10. A method as recited in claim 8, further comprising:

in the event that the other entity is not another resource bundle associated with the tenant, transmitting the data to a tenant-level inbound queue of the other entity.

11. A system, comprising:

a bandwidth specification associated with a first tenant;

one or more resource bundles associated with the first tenant; and

for individual resource bundles of the one or more resource bundles associated with the first tenant;

an inbound queue for receiving data, wherein a rate at which data may be received through the inbound queue is determined according to the bandwidth specification; and

an outbound queue for sending data, wherein a rate at which data may be sent through the outbound queue is determined according to the bandwidth specification.

12. The system as recited in claim 11, wherein at least one of the one or more resource bundles associated with the first tenant comprises a virtual machine.

13. The system as recited in claim 11, further comprising:

a tenant-level inbound queue associated with the first tenant for receiving data, wherein a rate at which data may be received through the tenant-level inbound queue is determined according to the bandwidth specification; and

a tenant-level outbound queue associated with the first tenant for sending data, wherein a rate at which data may be sent through the tenant-level outbound queue is determined according to the bandwidth specification;

14. The system as recited in claim 13, wherein:

the bandwidth specification indicates a minimum bandwidth to be enforced for the inbound queue of each resource bundle associated with the first tenant; and

a minimum bandwidth of the tenant-level inbound queue is determined based at least in part on the minimum bandwidth to be enforced for the inbound queue of each resource bundle associated with the first tenant.

15. The system as recited in claim 13, wherein:

the bandwidth specification indicates a minimum bandwidth to be enforced for the outbound queue of each resource bundle associated with the first tenant; and

a minimum bandwidth of the tenant-level outbound queue is determined based at least in part on the minimum bandwidth to be enforced for the outbound queue of each resource bundle associated with the first tenant.

16. A system, comprising:

a plurality of server computers; and

a virtual network switch to provide a logical model of resources available via the plurality of server computers, wherein the logical model includes;

one or more tenants;

for an individual tenant;

a tenant-level inbound queue;

a tenant-level outbound queue;

one or more resource bundles; and

for an individual resource bundle;

a resource bundle-level inbound queue; and

a resource bundle-level outbound queue; and

a queue management module to implement the tenant-level inbound queues, the tenant-level outbound queues, the resource bundle-level inbound queues, and the resource-level outbound queues according to one or more bandwidth requirement specifications.

17. A system as recited in claim 16, wherein the queue management module comprises an application programming interface.

18. A system as recited in claim 16, wherein the logical model further comprises:

a best effort inbound queue for receiving data at a resource bundle that does not have an associated bandwidth requirement specification; and

a best effort outbound queue for transmitting data from a resource bundle that does not have an associated bandwidth requirement specification.

19. A system as recited in claim 16, wherein the system further comprises a data traffic management module that is configured to manage data ingress and data egress through the tenant-level inbound queues, the tenant-level outbound queues, the resource bundle-level inbound queues, and the resource-level outbound queues.

20. A system as recited in claim 16, wherein the system further comprises a resource bundle placement module that is configured to physically implement a resource bundle within the plurality of server computers based, at least in part, on the one or more bandwidth requirement specifications.