Distributed data center

Patent metadata

Field	Value
Publication number	US-12541386-B2
Application number	US-202117507672-A
Country	US
Kind code	B2
Filing date	Oct 21, 2021
Priority date	Oct 21, 2021
Publication date	Feb 3, 2026
Grant date	Feb 3, 2026

Abstract

A system can maintain a first data center in a first physical location that comprises first compute hardware, and a second data center in a second physical location that comprises second compute hardware. The system can establish an overlay network that spans the first data center and the second data center. The system can establish a group of virtualized volume identifiers that spans the first data center and the second data center, and that virtualizes physical storage volumes. The system can determine whether to process a customer virtualized workload on the first data center or on the second data center to produce a selected location, wherein the customer virtualized workload is configured to be processed on the first data center and to be processed on the second data center. The system can process the customer virtualized workload at the selected location.

First claim

What is claimed is:

1 . A system, comprising:
at least one processor; and at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations, comprising:
maintaining a first data center in a first physical location that comprises first compute hardware;
maintaining a second data center in a second physical location that comprises second compute hardware;
establishing an overlay network that spans the first data center and the second data center, and that virtualizes physical network resources of the first data center and the second data center;
establishing a group of virtualized volume identifiers that spans the first data center and the second data center, and that virtualizes physical storage volumes of the first data center and the second data center;
determining whether to process a first customer virtualized workload on the first data center or on the second data center to produce a selected location that identifies one of the first data center or the second data center, wherein the first customer virtualized workload is configured to be processed on one data center at a time of the first data center or on the second data center, wherein the first customer virtualized workload is configured to be processed on the first data center independently of the second data center, and wherein the first customer virtualized workload is configured to be processed on the second data center independently of the first data center;
processing the first customer virtualized workload at the selected location, wherein the first customer virtualized workload accesses physical storage volumes of the selected location by referencing the virtualized volume identifiers, and wherein respective virtualized volume identifiers of the virtualized volume identifiers differ from respective physical storage volume identifiers of the physical storage volumes; and
in response to determining that a first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via application programming interface calls satisfies a first frequency criterion, or that a second rate at which the first customer virtualized workload and the second customer virtualized workload access a same database satisfies a second frequency criterion, running the second customer virtualized workload at the selected location.

2 . The system of claim 1 , wherein the first data center and the second data center are active concurrently.

3 . The system of claim 1 , wherein the first data center has a first group of processing capabilities, wherein the second data center has a second group of processing capabilities, and wherein the first group of processing capabilities differs from the second group of processing capabilities.

4 . The system of claim 1 , wherein the first data center comprises storage resources, and wherein the second data center omits the storage resources.

5 . The system of claim 1 , wherein the determining that the first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via the application programming interface calls satisfies the first frequency criterion, or that the second rate at which the first customer virtualized workload and the second customer virtualized workload access the same database satisfies the second frequency criterion comprises determining that the second customer virtualized workload shares an affinity with the first customer virtualized workload, and wherein the operations further comprise:
obtaining, from a cloud management platform that is separate from the first data center and the second data center, information that indicates that the second customer virtualized workload shares the affinity with the first customer virtualized workload.

6 . The system of claim 5 , wherein the cloud management platform determined the affinity based on communicating with a virtualization management component operated by the first data center and the second data center.

7 . The system of claim 1 , wherein respective virtualized volume identifiers of the virtualized volume identifiers comprise respective worldwide names.

8 . The system of claim 1 , wherein the virtualized volume identifiers spoof the physical storage volume identifiers.

9 . A method, comprising:
maintaining, by a system comprising at least one processor, a first data center and a second data center; facilitating, by the system, establishing an overlay network that spans the first data center and the second data center; facilitating, by the system, establishing virtualized volume identifiers that span the first data center and the second data center, and that virtualize physical storage volumes of the first data center and the second data center; determining, by the system, whether to execute a first customer virtualized workload on the first data center or on the second data center to produce a selected location that identifies one of the first data center or the second data center, wherein the first customer virtualized workload is configured to be executed on the first data center independently of the second data center, and wherein the customer virtualized workload is configured to be executed on the second data center independently of the first data center; executing, by the system, the first customer virtualized workload at the selected location, wherein the first customer virtualized workload accesses selected physical storage volumes of the selected location by referencing the virtualized volume identifiers, and wherein respective virtualized volume identifiers of the virtualized volume identifiers differ from respective physical storage volume identifiers of the physical storage volumes; and in response to determining that a first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via application programming interface calls satisfies a first frequency criterion, or that a second rate at which the first customer virtualized workload and the second customer virtualized workload access a same database satisfies a second frequency criterion, executing, by the system, the second customer virtualized workload at the selected location.

10 . The method of claim 9 , wherein the first data center and the second data center are part of a group of data centers that comprises at least two data centers, and wherein the group of data centers are presented as a unified data center to a customer account.

11 . The method of claim 9 , wherein a cloud management platform is separate from the first data center and the second data center, and wherein the cloud management platform manages the first data center and the second data center.

12 . The method of claim 9 , wherein the first data center comprises primary storage and secondary storage.

13 . The method of claim 9 , wherein portions of respective computing resources of the first data center and the second data center are reserved for individual customers.

14 . The method of claim 9 , wherein the overlay network abstracts physical network resources of the first data center and the second data center.

15 . The method of claim 9 , wherein the determining that the first rate at which the first customer virtualized workload and the second customer virtualized workload call each other via application programming interface calls satisfies the first frequency criterion, or that the second rate at which the first customer virtualized workload and the second customer virtual

Assignees

• Emc Ip Holding Co Llc

Inventors

• Shemer Jehuda
• Lotosh Valerie
• Sharvit Erez

Classifications

• G06F2009/45595

  Network integration; Enabling network access in virtual machine instances · CPC title

• G06F2009/45579

  I/O management, e.g. providing access to device drivers or storage · CPC title

• G06F9/45558 Primary

  Hypervisor-specific management and integration aspects · CPC title

• G06F2009/4557

  Distribution of virtual machine instances; Migration and load balancing · CPC title