SYSTEM FOR MIGRATING VIRTUAL MACHINE AND METHOD THEREOF

• US 20150113531A1
• Filed: 10/10/2014
• Published: 04/23/2015
• Est. Priority Date: 10/18/2013
• Status: Abandoned Application

• Current Assignee: Power-All Networks Limited
• Original Assignee: Power-All Networks Limited
• Inventors: LV, JUN, XU, YUN-JIE, HUANG, MENG-MING, ZHANG, JIAN-PING
• Application Number:
  US14/512,196
• Publication Number:
  US 20150113531A1
• Time in Patent Office: Days
• US Class Current: 718/1
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence

Abstract

A method for migrating a virtual machine (VM) includes: receiving a migrate request to migrate a VM of a first cloud node, obtaining configuration information of the VM of the first node and a target address, and generating a parameter file including the configuration information of the VM; obtaining system information of the VM of the first node, and creating an image file according to the system information; packeting the parameter file and the image file of the VM of the first node to obtain a packet file, and storing the packet file into a storage server of the first cloud node; transmitting the packet file to a storage server of a second cloud node according to the target address; and creating a new VM in a platform server of the second cloud node according to the configuration information and restoring the image file to the created VM.

Claims

1. A system for migrating a virtual machine (VM) comprising:

one or more processing units;

a plurality of modules which are collections of instructions executed by the processing unit, the plurality of modules comprising;

a parameter file generating module configured to receive a migrate request to migrate a VM of a first cloud node, and obtain configuration information of the VM of the first cloud node and a target address in response to the migrate request, and generate a parameter file comprising at least the configuration information of the VM of the first cloud node;

an image file creation module configured to obtain system information of the VM of the first cloud node, and create an image file according to the system information, wherein the system information comprises at least information of an operating system, applications, and user data of the VM of the first node; and

a storage controlling module configured to packet the parameter file and the image file of the VM of the first node to obtain a packet file, and store the packet file into a storage server of the first cloud node;

a data transmission module configured to transmit the packet file to a storage server of a second cloud node according to the target address, wherein the target address is a network address of the storage server of the second cloud node; and

a restoring module configured to create a new VM in a platform server of the second cloud node according to the configuration information included in the packet file and restore the image file included in the packet file to the created VM, thus to migrate the VM of the first cloud to the platform server of the second cloud node.

2. The system according to claim 1, wherein the migrate request comprises a unique identifier of the VM of the first cloud node and the target address, the parameter file generating module obtains the unique identifier of the VM of the first cloud node and the target address included in the migrate request, and obtains the configuration information of the VM of the first cloud node corresponding to the unique identifier of the VM from a cloud platform management server which stores a number of configuration information corresponding to different unique identifiers.

3. The system according to claim 2, wherein the image file creation module obtains the system information of the VM of the first cloud node according to the unique identifier of the VM of the first cloud node from the cloud platform management server which further stores a number of system information corresponding to different unique identifiers.

4. The system according to claim 1, wherein modules further comprise a template installation module configured to install a template file on the VM of the first cloud node before migrating the VM of the first cloud node, wherein the template file packets a number of drive files supporting different virtual platforms;

after the restoring module creates the new VM in the platform server of the second cloud node and restores the image file included in the packet file to the created VM, the template file is installed in the VM already migrated to the platform server of the second cloud node;

if the VM is being started up, the restoring module further determines which virtual platform is applied by the platform server of the second cloud node, and obtain a drive file supporting the determined virtual platform from the template file, and then starts up and run the VM migrated to the platform server of the second cloud node according to the determined drive file.

5. The system according to claim 1, wherein the modules further comprises a deleting module configured to delete the packet file stored in the storage servers of the first cloud node and the second cloud device after the VM of the first cloud device is migrated to the second cloud node.

6. A method for migrating a virtual machine (VM) comprising:

receiving a migrate request to migrate a VM of a first cloud node, obtaining configuration information of the VM of the first cloud node and a target address in response to the migrate request, and generating a parameter file at least comprising the configuration information of the VM of the first cloud node;

obtaining system information of the VM of the first cloud node, and creating an image file according to the system information, wherein the system information at least comprises information of an operating system, applications, and user data of the VM of the first cloud node;

packeting the parameter file and the image file of the VM of the first cloud node to obtain a packet file, and storing the packet file into a storage server of the first cloud node;

transmitting the packet file to a storage server of a second cloud node according to the target address, wherein the target address is a network address of the storage server of the second cloud node; and

creating a new VM in a platform server of the second cloud node according to the configuration information included in the packet file and restoring the image file included in the packet file to the created VM to migrate the VM of the first cloud node to the platform server of the second cloud node.

7. The method according to claim 6, wherein the migrate request comprises a unique identifier of the VM of the first node and the target address, the step of obtaining configuration information of the VM of the first node and a target address in response to the migrate request comprises:

obtaining the unique identifier of the VM and the target address included in the migrate request; and

obtaining the configuration information of the VM corresponding to the unique identifier of the VM from a cloud platform management server which stores a number of configuration information corresponding to different unique identifiers.

8. The method according to claim 7, wherein the step of obtaining system information of the VM of the first node comprises:

obtains the system information of the VM of the first node according to the unique identifier of the VM from the cloud platform management server which further stores a number of system information corresponding to different unique identifiers.

9. The method according to claim 6, further comprising:

installing a template file on the VM of the first cloud node prior to migrate the VM of the first cloud node, wherein the template file packets a number of drive files supporting different virtual platforms;

determining which virtual platform is applied by the platform server of the second cloud node when the VM is being started up after the VM of the first cloud node is migrated to the platform server of the second cloud node;

obtaining a drive file supporting the determined virtual platform from the template file; and

starting up and running the VM migrated to the platform server of the second cloud node according to the determined drive file.

10. The method according to claim 6, further comprising:

deleting the packet file stored in the storage servers of the first cloud node and the second cloud device after the VM of the first cloud device is migrated to the second cloud node.

11. A non-transitory storage medium having stored thereon instructions that, when executed by at least one processor, causes the least one processor to execute instructions of a method for automatically migrating a virtual machine (VM) from a first cloud node to a second cloud node, the method comprising:

receiving a migrate request to migrate the VM of the first cloud node, obtaining configuration information of the VM of the first node and a target address in response to the migrate request, and generating a parameter file at least comprising the configuration information of the VM;

obtaining system information of the VM of the first node, and creating an image file according to the system information, wherein the system information at least comprises information of an operating system, applications, and user data of the VM of the first node;

packeting the parameter file and the image file of the VM of the first node to obtain a packet file, and storing the packet file into a storage server of the first cloud node;

transmitting the packet file to a storage server of the second cloud node according to the target address, wherein the target address is a network address of the storage server of the second cloud node; and

creating a new VM in a platform server of the second cloud node according to the configuration information included in the packet file and restoring the image file included in the packet file to the created VM to migrate the VM of the first node to the platform server of the second cloud node.

12. The non-transitory storage medium according to claim 11, wherein the migrate request comprises a unique identifier of the VM of the first node and the target address, the step of obtaining configuration information of the VM of the first node and a target address in response to the migrate request comprises:

obtaining the unique identifier of the VM and the target address included in the migrate request; and

obtaining the configuration information of the VM corresponding to the unique identifier of the VM from a cloud platform management server which stores a number of configuration information corresponding to different unique identifiers.

13. The non-transitory storage medium according to claim 12, wherein the step of obtaining system information of the VM of the first node comprises:

obtains the system information of the VM of the first node according to the unique identifier of the VM from the cloud platform management server which further stores a number of system information corresponding to different unique identifiers.

14. The non-transitory storage medium according to claim 11, the method further comprising:

installing a template file on the VM of the first cloud node prior to migrate the VM of the first cloud node, wherein the template file packets a number of drive files supporting different virtual platforms;

determining which virtual platform is applied by the platform server of the second cloud node when the VM is being started up after the VM of the first cloud node is migrated to the platform server of the second cloud node;

obtaining a drive file supporting the determined virtual platform from the template file; and

starting up and running the VM migrated to the platform server of the second cloud node according to the determined drive file.

15. The non-transitory storage medium according to claim 11, the method further comprising:

deleting the packet file stored in the storage servers of the first cloud node and the second cloud device after the VM of the first cloud device is migrated to the second cloud node.