IP Library Granted Patent US 11,169,893
Granted Patent B2
US 11,169,893 · App. 16/507,083 · Granted Nov 9, 2021

Reserving failover capacity in cloud computing

Inventors: Manoj Krishnan (Thrissur, IN); Gabriel Tarasuk-Levin (Palo Alto, CA)
Assignee: VMware, Inc.
G06F11/2025G06F2201/85
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,169,893
App. No.
16/507,083
Granted
Nov 9, 2021
Kind
B2
Abstract

Methods and devices for providing reserved failover capacity across a plurality of data centers are described herein. An exemplary method includes determining whether a management process is executing at a first data center corresponding to a first physical location. In accordance with a determination that the management process is not executing at the first data center corresponding to the first physical location a host is initiated at a second data center corresponding to a second physical location and the management process is executed on the initiated host at the second data center corresponding to the second physical location.

Claims (75)

1. A method for providing reserved failover capacity across a plurality of data centers, the method comprising:

determining whether a management process is executing at a first data center corresponding to a first physical location;

reserving resources equivalent to a resource requirement of the management process at a second data center corresponding to a second physical location;

in accordance with a determination that the management process is not executing at the first data center corresponding to the first physical location:

initiating a host at the second data center corresponding to the second physical location; and

executing the management process on the initiated host at the second data center corresponding to the second physical location.

2. The method of claim 1 , wherein determining whether the management process is not executing at the first data center corresponding to the first physical location includes determining if the management process is not executing due to a first failure condition or a second failure condition.

3. The method of claim 2 , further comprising:

in accordance with a determination that the management process at the first data center corresponding to the first physical location is not executing due to the second failure condition:

forgoing initiating the host at the second data center corresponding to the second location.

4. The method of claim 2 , wherein the first failure condition is a lack of failover capacity, a failure of the first data center corresponding to the first physical location, or a loss of network connection.

5. The method of claim 2 , wherein the second failure condition is a failure of a previous host or a stall of the management process.

6. The method of claim 2 , further comprising:

determining if the first failure condition has been resolved;

in accordance with a determination that the first failure condition has been resolved:

executing the management process on a host at the first data center corresponding to the first physical location;

ceasing execution of the management process on the initiated host at the second data center corresponding to the second physical location; and

removing the initiated host at the second data center corresponding to the second physical location.

7. The method of claim 1 , wherein initiating the host at the second data center corresponding to the second physical location includes initiating one or more virtual machines.

8. The method of claim 7 , wherein executing the management process on the initiated host at the second data center corresponding to the second physical location includes executing the management process on the one or more initiated virtual machines.

9. The method of claim 1 , wherein initiating the host at the second data center corresponding to the second physical location includes allocating at least one of processing resources or storage resources.

10. The method of claim 9 , wherein allocating the at least one of processing resources or storage resources includes requesting resources based on the resource requirement of the management process.

11. The method of claim 1 , wherein the management process is configured to execute in a virtual private cloud.

12. The method of claim 1 , wherein the first data center corresponding to the first physical location is associated with a first availability zone.

13. One or more non-transitory computer readable storage media storing one or more programs, the one or more programs comprising instructions for providing reserved failover capacity across a plurality of data centers, which when executed by one or more processors of an electronic device, cause the electronic device to:

determine whether a management process is executing at a first data center corresponding to a first physical location;

reserve resources equivalent to a resource requirement of the management process at a second data center corresponding to a second physical location;

in accordance with a determination that the management process is not executing at the first data center corresponding to the first physical location:

initiate a host at the second data center corresponding to the second physical location; and

execute the management process on the initiated host at the second data center corresponding to the second physical location.

14. The non-transitory computer readable storage media of claim 13 , wherein determining whether the management process is not executing at the first data center corresponding to the first physical location includes determining if the management process is not executing due to a first failure condition or a second failure condition.

15. The non-transitory computer readable storage media of claim 14 , wherein the instructions, which when executed by the electronic device, further cause the electronic device to:

determine if the first failure condition has been resolved;

in accordance with a determination that the first failure condition has been resolved:

execute the management process on a host at the first data center corresponding to the first physical location;

cease execution of the management process on the initiated host at the second data center corresponding to the second physical location; and

remove the initiated host at the second data center corresponding to the second physical location.

16. The non-transitory computer readable storage media of claim 14 , wherein the instructions, which when executed by the electronic device, further cause the electronic device to:

in accordance with a determination that the management process at the first data center corresponding to the first physical location is not executing due to the second failure condition:

forgo initiating the host at the second data center corresponding to the second location.

17. The non-transitory computer readable storage media of claim 14 , wherein the first failure condition is a lack of failover capacity, a failure of the first data center corresponding to the first physical location, or a loss of network connection.

18. The non-transitory computer readable storage media of claim 14 , wherein the second failure condition is a failure of a previous host or a stall of the management process.

19. The non-transitory computer readable storage media of claim 13 , wherein initiating the host at the second data center corresponding to the second physical location includes initiating one or more virtual machines.

20. The non-transitory computer readable storage media of claim 19 , wherein executing the management process on the initiated host at the second data center corresponding to the second physical location includes executing the management process on the one or more initiated virtual machines.

21. The non-transitory computer readable storage media of claim 13 , wherein initiating the host at the second data center corresponding to the second physical location includes allocating at least one of processing resources or storage resources.

22. The non-transitory computer readable storage media of claim 21 , wherein allocating the at least one of processing resources or storage resources includes requesting resources based on the resource requirement of the management process.

23. The non-transitory computer readable storage media of claim 13 , wherein the management process is configured to execute in a virtual private cloud.

24. The non-transitory computer readable storage media of claim 13 , wherein the first data center corresponding to the first physical location is associated with a first availability zone.

25. A system, comprising:

one or more processors; and

memory storing one or more programs configured to be executed by the one or more processors for providing reserved failover capacity across a plurality of data centers, the one or more programs including instructions for:

determining whether a management process is executing at a first data center corresponding to a first physical location;

reserving resources equivalent to a resource requirement of the management process at a second data center corresponding to a second physical location;

in accordance with a determination that the management process is not executing at the first data center corresponding to the first physical location:

initiating a host at the second data center corresponding to the second physical location; and

executing the management process on the initiated host at the second data center corresponding to the second physical location.

26. The system of claim 25 , wherein determining whether the management process is not executing at the first data center corresponding to the first physical location includes determining if the management process is not executing due to a first failure condition or a second failure condition.

27. The system of claim 26 , the one or more programs further including instructions for:

determining if the first failure condition has been resolved;

in accordance with a determination that the first failure condition has been resolved:

executing the management process on a host at the first data center corresponding to the first physical location;

ceasing execution of the management process on the initiated host at the second data center corresponding to the second physical location; and

removing the initiated host at the second data center corresponding to the second physical location.

28. The system of claim 26 , the one or more programs further including instructions for:

in accordance with a determination that the management process at the first data center

corresponding to the first physical location is not executing due to the second failure condition:

forgoing initiating the host at the second data center corresponding to the second location.

29. The system of claim 26 , wherein the first failure condition is a lack of failover capacity, a failure of the first data center corresponding to the first physical location, or a loss of network connection.

30. The system of claim 26 , wherein the second failure condition is a failure of a previous host or a stall of the management process.

31. The system of claim 25 , wherein initiating the host at the second data center corresponding to the second physical location includes initiating one or more virtual machines.

32. The system of claim 31 , wherein executing the management process on the initiated host at the second data center corresponding to the second physical location includes executing the management process on the one or more initiated virtual machines.

33. The system of claim 25 , wherein initiating the host at the second data center corresponding to the second physical location includes allocating at least one of processing resources or storage resources.

34. The system of claim 33 , wherein allocating the at least one of processing resources or storage resources includes requesting resources based on the resource requirement of the management process.

35. The system of claim 25 , wherein the management process is configured to execute in a virtual private cloud.

36. The system of claim 25 , wherein the first data center corresponding to the first physical location is associated with a first availability zone.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0314 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2021
From: KRISHNAN, MANOJ; TARASUK-LEVIN, GABRIEL
To: VMWARE, INC.
Reel/Frame 054815/0920 →