System and method for storage and deployment of virtual machines in a virtual server environment

• US 9,563,469 B2
• Filed: 01/26/2015
• Issued: 02/07/2017
• Est. Priority Date: 07/10/2009
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Lent, Arthur F., Morrissette, Peter M., Clayton-Luce, Timothy J.
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US14/605,235
• Publication Number:
  US 20150339157A1
• Time in Patent Office: 743 Days
• Field of Search: 709/226
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1824 implemented using Network-attached Storage [NAS] architecture distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/4868 with creation or replication
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals

Abstract

Described herein are systems and methods for storage and deployment of VMs in a virtual server environment. A VM deployment module executing on a server may produce VM container objects representing VMs, a VM container object comprising VM data describing a VM and vdisk configuration data. The VM deployment module may also later produce VMs on a server using the VM container objects. The VM deployment module may do so by producing a vdisk from a VM container object, the vdisk comprising the VM and vdisk configuration data. Rather than configuring the vdisk as typically done to make the vdisk useable to the server, the vdisk configuration data is used to make the vdisk useable and the VM data on the vdisk immediately accessible to the server. As such, the VM data may be immediately read to produce a VM on the server, thus providing rapid deployment of VMs.

Claims

1. A system for producing a virtual machine (VM) on a server, the system comprising:

a VM manager engine configured for;

producing a virtual disk (vdisk) from a container object comprising VM data and vdisk configuration data, the vdisk comprising the VM data and vdisk configuration data, the VM data describing a VM;

exporting the vdisk to the server;

using the vdisk configuration data on the vdisk for making the VM data on the vdisk accessible to the server; and

producing the VM on the server using the VM data.

2. The system of claim 1, further comprising:

producing a second vdisk from the container object, the second vdisk comprising the VM data and the vdisk configuration data from the container object;

making the VM data of the second vdisk immediately accessible by an operating system of the server before producing the VM associated with the container object on the server; and

producing the VM on the server using the VM data from the second vdisk.

3. The system of claim 2, wherein VM data on the second vdisk is made accessible to the server without configuring the second vdisk.

4. The system of claim 1, wherein:

the VM produced on the server comprises a separate instance of a separate operating system distinct from an operating system of the server, and one or more applications that execute on the server.

5. The system of claim 1, wherein:

the VM data describing the VM specifies hardware or software resources used by the VM; and

the vdisk configuration data comprises partitioning data specifying partitioning of the vdisk or formatting data specifying file system formatting for the vdisk.

6. The system of claim 1, wherein the system is further configured for:

deleting the first vdisk after storing the vdisk configuration data and VM data to the first vdisk.

7. The system of claim 1, further comprising:

a client system connected with the server and interfacing with the VM on the server to access client data of the storage system, wherein the storage system is operatively coupled to the server for storing client data.

8. The system of claim 1, wherein the VM manager engine is further configured for receiving a request from the storage system to create the container object before receiving a request from the storage system to produce the first vdisk from the container object, the created container object being initially empty.

9. A non-transitory computer readable medium having instructions stored thereon for execution by a processor, the computer readable medium comprising sets of instructions for:

producing a virtual disk (vdisk) from a container object comprising VM data and vdisk configuration data, the vdisk comprising the VM data and vdisk configuration data, the VM data describing a VM;

exporting the vdisk to server;

using the vdisk configuration data on the vdisk for making the VM data on the vdisk accessible to the server; and

producing the VM on the server using the VM data.

10. The medium of claim 9, further comprising:

producing a second vdisk from the container object, the second vdisk comprising the VM data and the vdisk configuration data from the container object;

making the VM data of the second vdisk immediately accessible by an operating system of the server before producing the VM associated with the container object on the server; and

producing the VM on the server using the VM data from the second vdisk.

11. The medium of claim 10, wherein VM data on the second vdisk is made accessible to the server without configuring the second vdisk.

12. The medium of claim 9, wherein:

the VM produced on the server comprises a separate instance of a separate operating system distinct from an operating system of the server, and one or more applications that execute on the server.

13. The medium of claim 9, wherein:

the VM data describing the VM specifies hardware or software resources used by the VM; and

the vdisk configuration data comprises partitioning data specifying partitioning of the vdisk or formatting data specifying file system formatting for the vdisk.

14. The medium of claim 9, further storing instructions for:

deleting the first vdisk after storing the vdisk configuration data and VM data to the first vdisk.

15. The medium of claim 9, further storing instructions for:

receiving a request from the storage system to create the container object before receiving a request from the storage system to produce the first vdisk from the container object, the created container object being initially empty.

18. The method of claim 15, wherein VM data on the second vdisk is made accessible to the server without configuring the second vdisk.

19. The method of claim 15, wherein:

the VM produced on the server comprises a separate instance of a separate operating system distinct from an operating system of the server, and one or more applications that execute on the server.

20. The method of claim 15, wherein:

the VM data describing the VM specifies hardware or software resources used by the VM; and

the vdisk configuration data comprises partitioning data specifying partitioning of the vdisk or formatting data specifying file system formatting for the vdisk.

16. A method comprising:

producing a virtual disk (vdisk) from a container object comprising VM data and vdisk configuration data, the vdisk comprising the VM data and vdisk configuration data, the VM data describing a VM;

exporting the vdisk to a server;

using the vdisk configuration data on the vdisk for making the VM data on the vdisk accessible to the server; and

producing the VM on the server using the VM data.

17. The method of claim 16, further comprising:

producing a second vdisk from the container object, the second vdisk comprising the VM data and the vdisk configuration data from the container object;

making the VM data of the second vdisk immediately accessible by an operating system of the server before producing the VM associated with the container object on the server; and

producing the VM on the server using the VM data from the second vdisk.