Virtual machine group migration
US-2015149999-A1 · May 28, 2015 · US
US9811365B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9811365-B2 |
| Application number | US-201414274426-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 9, 2014 |
| Priority date | May 9, 2014 |
| Publication date | Nov 7, 2017 |
| Grant date | Nov 7, 2017 |
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.
A method of migrating applications from an enterprise-based network to a multi-tenant network of a compute service provider may include receiving a request to migrate an application running on a first virtual machine instance within the enterprise-based network. Dependencies of the application may be determined by identifying at least a second virtual machine instance within the enterprise-based network, where the at least second virtual machine instance associated with the application. Resource monitoring metrics associated with hardware resources used by the first virtual machine instance and the at least second virtual machine instance may be received. The first and at least second virtual machine instances may be migrated from the enterprise-based network to at least one virtual machine at a server within the multi-tenant network based on the monitoring metrics, thereby migrating the application from the enterprise-based network to the multi-tenant network.
Opening claim text (preview).
What is claimed is: 1. A method of migrating applications from an enterprise-based network to a multi-tenant network of a compute service provider, the method comprising: receiving a request to migrate an application running on a first virtual machine instance within the enterprise-based network, wherein the request is received in a migration service of the compute service provider; determining dependencies of the application by identifying at least a second virtual machine instance within the enterprise-based network, wherein the at least second virtual machine instance is associated with the application; receiving resource monitoring metrics associated with hardware resources used by the first virtual machine instance and the at least second virtual machine instance, wherein the hardware resources are associated with at least one host server computer hosting the first virtual machine instance and the at least second virtual machine instance; selecting, based on the resource monitoring metrics, a virtual machine instance type from a plurality of available virtual machine instance types at the multi-tenant network of the compute service provider for each of, at least, the first virtual machine instance and the at least second virtual machine instance; migrating the first virtual machine instance and the at least second virtual machine instance from the enterprise-based network to each of the selected virtual machine instance types, wherein the selected virtual machine instance types are hosted by a server computer within the multi-tenant network of the compute service provider, thereby migrating the application from the enterprise-based network to the multi-tenant network of the compute service provider; and configuring a network topology within the multi-tenant network of the compute service provider in which a physical, hardware-based connection topology of the enterprise-based network is at least partially emulated on the multi-tenant network of the compute service provider by the server computer within the multi-tenant network of the compute service provider, wherein configuring the network topology is controlled through client input to the migration service of the compute service provider, and wherein at least a partial network configuration of the physical, hardware-based connection topology of the enterprise-based network is preserved upon migration of the application to the multi-tenant network of the compute service provider, including preserving an internet protocol address and a host name of an enterprise-based server or preserving a virtual machine server dependency of an enterprise-based network application. 2. The method according to claim 1 , wherein the migrating comprises: migrating the first virtual machine instance from the enterprise-based network to at least a first virtual machine instance of the selected virtual machine instance type; and migrating the at least second virtual machine instance from the enterprise-based network to at least a second virtual machine instance of the selected virtual machine instance type, wherein the at least first and at least second virtual machine instances are hosted by the server computer within the multi-tenant network of the compute service provider. 3. The method according to claim 1 , wherein the enterprise-based network comprises a private network and the method further comprises: determining whether the first virtual machine instance and the at least second virtual machine instance are in a single sub-network or in separate sub-networks of the private network. 4. The method according to claim 3 , comprising: when the first virtual machine instance and the at least second virtual machine instance are in a single sub-network of the private network, creating a sub-network within the multi-tenant network of the compute service provider for at least one virtual machine instance running the migrated application; and when the first virtual machine instance and the at least second virtual machine instance are in separate sub-networks of the private network, creating at least a first sub-network and a second sub-network within the multi-tenant network of the compute service provider, wherein the first sub-network within the multi-tenant network of the compute service provider is for hosting at least a first virtual machine instance of the selected virtual machine instance type, and wherein the second sub-network within the multi-tenant network of the compute service provider is for hosting at least a second virtual machine instance of the selected virtual machine instance type. 5. The method according to claim 1 , comprising: determining a name and an IP address for the at least one host server computer hosting the first virtual machine instance and the at least second virtual machine instance within the enterprise-based network. 6. The method according to claim 5 , comprising: assigning a name and an IP address to the server computer within the multi-tenant network of the compute service provider, wherein the name and the IP address are the same as a name and an IP address associated with the at least one host server computer within the enterprise-based network. 7. A computer-readable storage medium storing instructions thereon for executing a method of migrating applications from an enterprise-based network to a multi-tenant network of a compute service provider, the method comprising: receiving a request to migrate at least one application running on a virtual machine instance hosted by a server computer within the enterprise-based network; obtaining dependency information from a migration service within the enterprise-based network, wherein the dependency information identifies one or more virtual machine instances associated with the at least one application, and wherein the one or more virtual machine instances are run within the enterprise-based network; receiving, at the multi-tenant network of the compute service provider, resource monitoring metrics associated with usage of computing resources by the at least one application running on the virtual machine instance hosted by the server computer within the enterprise-based network; selecting, based at least in part on the resource monitoring metrics, a virtual machine instance type from a plurality of available virtual machine instance types for a virtual machine instance hosted by a server computer within the multi-tenant network of the compute service provider; migrating the at least one application from the enterprise-based network to the virtual machine instance hosted by the server computer within the multi-tenant network of the compute service provider; based on client input to the compute service provider, configuring a network address for the virtual machine instance hosted by the server computer within the multi-tenant network of the compute service provider; and configuring a network topology within the multi-tenant network of the compute service provider in which a physical, hardware-based connection topology of the enterprise-based network is at least partially emulated on the multi-tenant network of the compute service provider by the server computer within the multi-tenant network of the compute service provider, wherein configuring the network topology is controlled through client input associated with the migration of the at least one application, and wherein at least a partial network configuration of the physical, hardware-based connection topology of the enterprise-based network is preserved upon migration of the at least one application to the multi-tenant network of the compute service provider, including preserving an internet protocol address and a host name of an enterprise-based server or preserving a virtual machine server
Techniques for rebalancing the load in a distributed system · CPC title
Distribution of virtual machine instances; Migration and load balancing · CPC title
Grid computing · CPC title
Hypervisor-specific management and integration aspects · CPC title
Network utilisation, e.g. volume of load or congestion level · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.