AVAILABILITY MANAGEMENT OPERATIONS IN A DISTRIBUTED COMPUTING SYSTEM

• US 20180262563A1
• Filed: 03/07/2017
• Published: 09/13/2018
• Est. Priority Date: 03/07/2017
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: MOHAMMED, YUNUS, WANG, JUN, FONTOURA, MARCUS FELIPE, RUSSINOVICH, MARK EUGENE, SIDDIQUI, MOHAMMAD ZEESHAN, PATWA, PRITESH, ZIMMERMAN, SEAN DAVID, TIAN, XIAOXIONG
• Application Number:
  US15/452,652
• Publication Number:
  US 20180262563A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 2209/503 Resource availability
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 41/0823 characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• 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 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 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Various methods and systems for implementing an availability management system for implementing an availability management, in distributed computing systems, are provided. An availability management system implements an availability manager and an availability configuration interface to meet availability guarantees for tenant infrastructure. The availability management systems operates with availability zones, computing clusters, fault and upgrade domains to allocate and de-allocate virtual machine sets of virtual machine instances to a distributed computing system based on tenant-defined availability parameters. The availability parameters are used to generate an availability profile. The availability manager is configured to, based on an availability profile, allocate the virtual machine sets based an allocation scheme. The availability manager specifically performs scaling-out, scaling-in and rebalancing operations for allocating and de-allocating the virtual machine sets. An allocation configuration that meets the availability parameters of the availability profile is determined the allocation configuration is used for allocating the virtual machine set.

Claims

1. A system for implementing availability management in distributed computing systems, the system comprising:

a plurality of availability zones, wherein an availability zone is a zone-tier isolated point of failure computing constructing with a low-latency to one or more other availability zones;

a plurality of computing clusters, wherein the one or more computing clusters are defined within a corresponding availability zone;

a plurality of fault domains associated with the plurality of computing clusters, wherein a fault domain defines a fault-tier isolated point of failure computing construct; and

an availability manager configured to;

based on an availability profile comprising availability parameters for allocating a virtual machine set,

perform scaling-out operations comprising;

allocating the virtual machine set across the plurality of availability zones and the plurality of fault domains using a virtual machine spanning availability zones allocation scheme, wherein the virtual machine spanning scheme for allocating the virtual machine set comprises performing evaluations to determine a spanned allocation configuration defined across at least two availability zones, wherein the allocation configuration meets availability zone and fault domain availability parameters in the availability profile; and

perform scaling-in operations comprising;

de-allocating the virtual machine set from the plurality of availability zones and the plurality of fault domains using the virtual machine spanning availability zones allocation scheme, wherein the virtual machine spanning scheme for de-allocating the virtual machine set comprises performing evaluations to determine a spanned de-allocation configuration defined across at least two availability zones, wherein the allocation configuration meets availability zone and fault domain availability parameters in the availability profile.

2. The system of claim 1, further comprising:

an availability configuration interface to;

generate an availability configuration interface for;

receiving availability parameters that are used to generate the availability profile, wherein the availability parameters include an allocation scheme and two or more availability isolation tiers for allocating the virtual machine set,

wherein the availability parameters are selected based on logically-defined availability zones that are mapped to physically-defined availability zones, wherein the logically-defined availability zones abstract the allocation of virtual machine sets to the physically-defined availability zones;

receiving a query for allocation configurations of virtual machines sets; and

generating visual representations of allocation configurations of virtual machine sets.

3. The system of claim 1, wherein the plurality of computing clusters are each independently managed using a corresponding cluster manager,

wherein the cluster manger, for the first virtual machine set, manages a subset of a first set of cluster-tenants in a corresponding computing cluster of the cluster manager, the first set of cluster-tenants are instantiated across the at least two availability zones, and

wherein the cluster manager, for a second virtual machine set, manages a second set of cluster-tenants in the corresponding computing cluster of the cluster manager, the second set of cluster-tenants are instantiated in only one of the at least two availability zones.

4. The system of claim 1, wherein allocating the virtual machine sets is based on a two-pass sort and filter and bucketing scheme for identifying a subset of computing cluster to prioritize for performing scaling-out operations.

5. The system of claim 1, wherein allocating the virtual machine sets is based on a predefined number of unallocated virtual machine instances that are associated with a reserved list of cluster-tenants, wherein the reserved list of cluster-tenants are identified based on determining a list of cluster-tenants to be excluded.

6. The system of claim 1, wherein de-allocating the virtual machine set further comprises traversing cluster-tenant, fault domain and update domain pairs to delete a virtual machine instance from a selected cluster-tenant, fault domain and update domain pair having a maximum virtual machine instance count.

7. The system of claim 1, wherein de-allocating the virtual machine set is based at least in part on determining a rebalancing cost for cluster-tenants, wherein the rebalancing cost is a measure of a shortest path to balanced cluster-tenants.

8. The system of claim 1, further comprising the availability manager configured to perform rebalancing operations, wherein performing the rebalancing operations comprise:

receiving an indication to perform rebalancing for the virtual machine set, wherein the indication is received based on an occurrence of a triggering event;

determining the type of triggering event, wherein the type of trigger event indicate how to rebalance the virtual machine set in computing clusters; and

rebalancing the virtual machine set based on the type of trigger event, wherein rebalancing the virtual machine set comprises deleting and creating new virtual machine instances based on the availability profile of the corresponding virtual machine set.

9. The system of claim 1, wherein the allocation scheme determines an allocation configuration score for different allocation configurations for the virtual machine set in the availability zones such that the allocation configuration of the virtual machine set is selected based on the allocation configuration score, wherein the allocation configuration score is determined based on a current virtual machine instance count of a cluster-tenant, a remaining virtual machine instance to be allocated count and a maximum supported virtual machine count of the cluster-tenant.

10. One or more computer storage media having computer-executable instructions embodied thereon that, when executed, by one or more processors, causes the one or more processors to perform a method implementing availability management in distributed computing systems, the method comprising:

accessing a virtual machine set associated an availability profile for allocating a set of virtual machine instances associated with a virtual machine set in a plurality of availability zones and a plurality of fault domains; and

allocating the virtual machine set across the plurality of availability zones and the plurality of fault domains using a virtual machine spanning availability zones allocation scheme, wherein the virtual machine spanning scheme for allocating the virtual machine set comprises performing evaluations to determine a spanned allocation configuration defined across at least two availability zones, wherein the allocation configuration meets availability zone and fault domain availability parameters in the availability profile.

11. The media of claim 10, wherein allocating the virtual machine sets is based on a two-pass sort and filter and bucketing scheme for identifying a subset of computing cluster to prioritize for performing scaling-out operations.

12. The media of claim 10, wherein allocating the virtual machine sets is based on a predefined number of unallocated virtual machine instances that are associated with a reserved list of cluster-tenants, wherein the reserved list of cluster-tenants are identified based on determining a list of cluster-tenants to be excluded.

13. The media of claim 10, wherein allocating the virtual machine set further comprises allocating virtual machine instances to availability zones having a least number of virtual machine instances count, and wherein cluster-tenants are configured with a maximum virtual machine instance count limit such that virtual machine instances of the virtual machine set are allocated to the cluster-tenants instantiated on the plurality of computing clusters across the at least two availability zones.

14. The media of claim 10, wherein allocating the virtual machine set comprises allocating the virtual machine set across the plurality of availability zones, the plurality of fault domains, and a plurality of update domains, wherein an update domain defines an update-tier isolated point of failure relative to the fault-tier and the zone-tier.

15. A computer-implemented method for implementing availability management in distributed computing systems, the method comprising:

accessing a virtual machine set associated with an availability profile for de-allocating at least a subset of virtual machine instances of the virtual machine set from a plurality of availability zones and a plurality of fault domains; and

de-allocating the subset of virtual machine instances from the plurality of availability zones and the plurality of fault domains using the virtual machine spanning availability zones allocation scheme, wherein the virtual machine spanning scheme for de-allocating the virtual machine set comprises performing evaluations to determine a spanned de-allocation configuration defined across at least two availability zones, wherein the allocation configuration meets availability zone and fault domain availability parameters in the availability profile.

16. The method of claim 15, wherein de-allocating the virtual machine set further comprises traversing cluster-tenant, fault domain and update domain pairs to delete a virtual machine instance from a selected cluster-tenant, fault domain and update domain pair having a maximum virtual machine instance count.

17. The method of claim 16, wherein traversing cluster-tenant, fault domain and update domain pairs comprises:

determining a virtual machine instance count in each cluster-tenant, fault domain and update domain pair; and

deleting one or more virtual machines from a cluster-tenant, fault domain and update domain pair that has the maximum virtual machine instance count.

18. The method of claim 16, traversing cluster-tenant, fault domain and update domain pairs comprises:

determining that a virtual machine count for cluster-tenant, fault domain and update domain pair is greater than virtual machine count to be deleted;

selecting a fault domain with a maximum virtual machine instance count for fault domains;

in the fault domain, selecting an update domain with a maximum supported virtual machine count for update domains; and

deleting a virtual machine instance from the update domain.

19. The method of claim 15, wherein de-allocating the virtual machine set is based at least in part on determining a rebalancing cost for cluster-tenants, wherein the rebalancing cost is a measure of a shortest path to balanced cluster-tenants.

20. The method of claim 15, wherein de-allocating the virtual machine set comprises de-allocating the virtual machine set across the plurality of availability zones, the plurality of fault domains, and a plurality of update domains, wherein an update domain defines an update-tier isolated point of failure relative to the fault-tier and the zone-tier.