DYNAMIC SNAPSHOTS FOR SHARING NETWORK BOOT VOLUMES

• US 20170024224A1
• Filed: 07/22/2015
• Published: 01/26/2017
• Est. Priority Date: 07/22/2015
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Bakke, Mark, Kuik, Timothy, Thompson, David
• Application Number:
  US14/806,408
• Publication Number:
  US 20170024224A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

The subject technology addresses the need in the art for improving provisioning and booting of virtual machines in a cloud computing environment. Different versions of boot volume images may be shared in a storage repository accessible by one or more host computers. When a virtual machine is created, a shared boot volume image, including confirmation information for the virtual machine, may be selected for booting the virtual machine. Over time, newer version(s) of boot volume images may be stored in the storage repository and new virtual machine(s) may use the newer version of the boot volume image for booting.

Claims

1. A system, comprising:

at least one processor;

an interface;

a local storage device; and

memory including instructions that, when executed by the at least one processor, cause the system to;

store, at a shared storage device, a plurality of boot volume images corresponding to an operating system and respective configurations for a virtual machine;

select a boot volume image from the plurality of boot volume images, the boot volume image including at least configuration information for a new virtual machine;

for installing the new virtual machine using the configuration information;

load a first set of data into the memory from the selected boot volume image, the first set of data including at least a boot loader enabled to load at least a portion of the operating system into the memory and perform a boot process for the new virtual machine; and

store, using the interface, a second set of data into the local storage device, the second set of data including data for executing the operating system after performing the boot process for the new virtual machine.

2. The system of claim 1, wherein the plurality of boot volume images, stored at the shared storage device, include at least one boot volume image that includes a set of custom boot volume changes for a respective virtual machine.

3. The system of claim 1, wherein to select the boot volume image is based at least in part on a time in which each of the plurality of boot volume images was created.

4. The system of claim 1, wherein each of the plurality of boot volume images include a version of a kernel of the operating system and a set of drivers.

5. The system of claim 1, wherein the memory includes further instructions, when executed by the at least one processor, further cause the system to:

select a second boot volume image from the plurality of boot volume images, the second boot volume image being newer than the boot volume image and including at least one different set of data than the boot volume image; and

perform a boot process for a new second virtual machine using the selected second boot volume.

6. The system of claim 1, wherein the memory includes further instructions, when executed by the at least one processor, further cause the system to:

receive a read request for a block of data on a virtual disk stored in the local storage device, the virtual disk corresponding to the new virtual machine;

determine whether the read request was successful for the block of data on the virtual disk; and

responsive to the read request being unsuccessful, perform a read operation for the block of data on the selected boot volume image stored at the shared storage device.

7. The system of claim 6, wherein the memory includes further instructions, when executed by the at least one processor, further cause the system to:

perform a write operation for a second block of data on the virtual disk corresponding to the new virtual machine; and

generate, in an access log stored at the local storage device, a log entry including information corresponding to the write operation.

8. The system of claim 6, wherein the memory includes further instructions, when executed by the at least one processor, further cause the system to:

generate, in an access log stored at the local storage device, a log entry including information corresponding to the read operation.

9. The system of claim 1, wherein a hypervisor installs the new virtual machine.

10. A computer-implemented method, comprising:

storing, at a shared storage device, a plurality of boot volume images corresponding to an operating system and respective configurations for a virtual machine;

selecting a boot volume image from the plurality of boot volume images, the boot volume image including at least configuration information for a new virtual machine;

for installing the new virtual machine using the configuration information;

loading a first set of data into memory from the selected boot volume image, the first set of data including at least a boot loader enabled to load at least a portion of the operating system into the memory and perform a boot process for the new virtual machine; and

storing a second set of data into a local storage device, the second set of data including data for executing the operating system after performing the boot process for the new virtual machine.

11. The computer-implemented method of claim 10, wherein the plurality of boot volume images, stored at the shared storage device, include at least one boot volume image that includes a set of custom boot volume changes for a respective virtual machine.

12. The computer-implemented method of claim 10, wherein selecting the boot volume image is based at least in part on a time in which each of the plurality of boot volume images was created.

13. The computer-implemented method of claim 10, wherein each of the plurality of boot volume images include a version of a kernel of the operating system and a set of drivers.

14. The computer-implemented method of claim 10, further comprising:

selecting a second boot volume image from the plurality of boot volume images, the second boot volume image being newer than the boot volume image and including at least one different set of data than the boot volume image; and

performing a boot process for a new second virtual machine using the selected second boot volume.

15. The computer-implemented method of claim 10, further comprising:

receiving a read request for a block of data on a virtual disk stored in the local storage device, the virtual disk corresponding to the new virtual machine;

determining whether the read request was successful for the block of data on the virtual disk; and

responsive to the read request being unsuccessful, performing a read operation for the block of data on the selected boot volume image stored at the shared storage device.

16. The computer-implemented method of claim 15, further comprising:

performing a write operation for a second block of data on the virtual disk corresponding to the new virtual machine; and

generating, in an access log stored at the local storage device, a log entry including information corresponding to the write operation.

17. The computer-implemented method of claim 15, further comprising:

generating, in an access log stored at the local storage device, a log entry including information corresponding to the read operation.

18. The computer-implemented method of claim 10, wherein a hypervisor installs the new virtual machine.

19. A non-transitory computer-readable medium including instructions stored therein that, when executed by at least one computing device, cause the at least one computing device to:

store, at a shared storage device, a plurality of boot volume images corresponding to an operating system and respective configurations for a virtual machine;

select a boot volume image from the plurality of boot volume images, the boot volume image including at least configuration information for a new virtual machine;

for installing the new virtual machine using the configuration information;

load a first set of data into the memory from the selected boot volume image, the first set of data including at least a boot loader enabled to load at least a portion of the operating system into the memory and perform a boot process for the new virtual machine; and

store, using the interface, a second set of data into the local storage device, the second set of data including data for executing the operating system after performing the boot process for the new virtual machine.

20. The non-transitory computer-readable medium of claim 19, including further instructions that cause the at least one computing device to:

select a second boot volume image from the plurality of boot volume images, the second boot volume image being newer than the boot volume image and including at least one different set of data than the boot volume image; and

perform a boot process for a new second virtual machine using the selected second boot volume.