Workload migration across cloud providers and data centers
US-2017024260-A1 · Jan 26, 2017 · US
US12405819B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12405819-B2 |
| Application number | US-201916240858-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 7, 2019 |
| Priority date | Jan 7, 2019 |
| Publication date | Sep 2, 2025 |
| Grant date | Sep 2, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some examples, a system migrates, responsive to a request, a workload comprising components and relationships among the components as represented by a topology model, the migrating comprising migrating the workload from the source infrastructure to a target infrastructure, and migrating components of the workload from the source infrastructure to the target infrastructure.
Opening claim text (preview).
What is claimed is: 1. A non-transitory machine-readable storage medium comprising instructions that upon execution cause a system to: discover, responsive to receiving a migration request, a topology model by analyzing service model configuration information describing one or more previously instantiated and provisioned service instances of a workload of a corresponding service model previously instantiated and provisioned by a source infrastructure, the one or more previously instantiated and provisioned service instances comprising multiple related service components of the corresponding service model and comprising resources and tasks and the topology model representing dependency relationships among the multiple related service components; and migrate, responsive to the discovery of the topology model and based on the topology model, the workload from the source infrastructure to a target infrastructure different from the source infrastructure, and the multiple related service components of the workload from the source infrastructure to the target infrastructure. 2. The non-transitory machine-readable storage medium of claim 1 , wherein the corresponding service model comprises one of Topology and Orchestration Standard for Cloud Application (TOSCA), HCM Sequential, topology and universal models, CloudFormation, OpenStack Heat, OpenStack Python provisioning, and Terraforms, wherein the topology model comprises a graph of interconnected nodes, each interconnected node representing a respective service component, with interconnections representing an operational relationship between the interconnected nodes, wherein the topology model comprises information regarding which network address(es) is/are to be reconfigured if a migration of the workload occurs, and wherein the instructions upon execution cause a system to: interrogate, by an application programming interface, the workload to collect the service model configuration information; and deploy the workload on the source infrastructure by a cloud controller based on the topology model. 3. The non-transitory machine-readable storage medium of claim 1 , wherein the one or more previously instantiated and provisioned service instances of the workload comprises plural Day-2 operations of the corresponding service model, wherein the topology model comprises a declarative or prescriptive blueprint, wherein the instructions upon execution cause a system to: burst the workload from the source infrastructure to the target infrastructure, whereby the workload is maintained at the source infrastructure and one or more new service instances of the workload at the target infrastructure provides a workload contribution that scales the workload. 4. The non-transitory machine-readable storage medium of claim 1 , wherein the multiple related service components of the workload comprise an arrangement of resources and resource executable service code, wherein the migrating is performed by a migration controller as a service, wherein the migrating involves orchestrating all components of a topology of the workload to be migrated and provisioning resources on the target infrastructure to support the workload once migrated, and further comprising instructions that upon execution cause the system to: after migrating, deploy one or more new service instances of the workload at the target infrastructure; and after migrating, delete the one or more previously instantiated and provisioned service instance of the workload at the source infrastructure. 5. The non-transitory machine-readable storage medium of claim 4 , wherein instantiation of the workload comprises creating a concrete instance of a service, wherein provisioning of the workload comprises subscribing to one or more resources, services, and/or workloads, wherein the multiple related service components of the workload comprise an arrangement of virtual machines, and wherein the instructions that upon execution cause a system to: before, during, or after the migrating, perform at least one of: synchronization of data in a database, reconfiguring network addresses of components, or load balancing between components. 6. The non-transitory machine-readable storage medium of claim 1 , wherein the topology model refers to one or more service models, wherein migrating the workload comprises: copying the workload from the source infrastructure to the target infrastructure as part of scaling out the workload, wherein, during the migration, dependency relationships among the multiple related service components are maintained among the multiple related service components according the topology model. 7. A system comprising: a processor; and a non-transitory machine-readable storage medium storing instructions executable on the processor to: derive, responsive to receiving a migration request, a topology model by analyzing service model configuration information describing one or more previously instantiated and provisioned service instances of a workload of a corresponding service model previously instantiated and provisioned by a source infrastructure, the one or more previously instantiated and provisioned workload service instances comprising multiple related service components of the corresponding service model and comprising resources and tasks and the topology model represents dependency relationships among the multiple related service components; and migrate, responsive to the derivation and based on the topology model, the workload represented by the topology model from the source infrastructure to a target infrastructure different from the source infrastructure, wherein migrating the workload comprises migrating multiple related service components of the workload from the source infrastructure to the target infrastructure. 8. The system of claim 7 , wherein the topology model comprises a graph of interconnected nodes, each interconnected node representing a respective service component, with interconnections representing an operational relationship between the interconnected nodes, wherein the topology model comprises information regarding which network address(es) is/are to be reconfigured if a migration of the workload occurs, and wherein the source infrastructure comprises a data center or a cloud, and the target infrastructure comprises a data center or a cloud different from the data center or the cloud of the source infrastructure. 9. The system of claim 7 , wherein the corresponding service model comprises one of Topology and Orchestration Standard for Cloud Application (TOSCA), HCM Sequential, topology and universal models, CloudFormation, OpenStack Heat, OpenStack Python provisioning, and Terraforms, wherein the topology model comprises a graph of interconnected nodes, each interconnected node representing a respective service component, with interconnections representing an operational relationship between the interconnected nodes, wherein the topology model comprises information regarding which network address(es) is/are to be reconfigured if a migration of the workload occurs, and wherein the instructions are executable on the processor to: interrogate, by an application programming interface, the workload to collect the service model configuration information; and deploy the workload on the source infrastructure based on the topology model. 10. The system of claim 7 , wherein the one or more previously instantiated and provisioned service instances of the workload comprises plural Day-2 operations of the corresponding service model, wherein the topology model comprises a declarative or prescriptive blueprint, wherein the instructions are executable on the processor to: burst the workload from the source infra
for accessing one among a plurality of replicated servers · CPC title
considering the load · CPC title
resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence) · CPC title
Grid computing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.