Browse Prior Art Database

A method to update LV-based virtual machine template

IP.com Disclosure Number: IPCOM000237223D
Publication Date: 2014-Jun-09
Document File: 5 page(s) / 87K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a way to rapidly deploy LV-based virtual machine template image to a set of hypervisor servers in a typical HPC cluster environment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 5

A method to update LV

A method to update LV-

In high performance computing (HPC) cluster environment with cloud enabled, virtual machines are required to be rapidly deployed to run computing tasks. Surely, to achieve this, pre-defined virtual machine template image is used. The template image contains all required operating system, HPC software stack so that virtual machine could be ready immediately by cloning from the template, instead of installation process.

Typically, the purpose of deploying virtual machine is only for computing in HPC environment, so no requirement of data persistent, those machines are called stateless virtual machine. Given this, a common way to update & deploy virtual machine template is using copy-on-write storage technology - logical volume management (LVM) as virtual machine storage mechanism. This could improve I/O performance and save disk space. Because logical volume(LV) is local storage, so the virtual machine template image needs to be updated to each hypervisor server periodically or on demand once it get updated. Updating on each hypervisor server is a heavy administration work. Therefore, image server is introduced. Image server store all template images used by HPC cluster centrally.

The whole work flow as below:

1) Create a virtual machine on image server. It uses a logical volume as storage device. After operating system and related software

installed, the virtual machine is powered off. The virtual machine is defined as template virtual machine, and its image - the logic volume, is defined as template image.

2) Copy the template image to each hypervisor server: On hypervisor servers, create a new logical volume and write the template image into it by bit.

3) Now hypervisor servers have template image(LV) now. A VM could be created with storage of logical volume snapshot which is based on the template image(LV). After VMs starts, the OS and pre-installed software could work immediately. When the virtual machine is powered off, its storage devices - the logical volume snapshot is removed to save disk space.

1

--based virtual machine template

based virtual machine template



Page 02 of 5

Image Server

Hypervisor

Template VM

Template VM

Template image


(LV)

Template image


(LV)

Compress

VG

PV

Local Disk

Network File System

Hypervisor Server

Hypervisor Server

Hypervisor

VM

...

VM

Hypervisor

VM

...

VM

Template image(LV)

LVS

Template image(LV)

LVS

VG

VG

PV

PV

Local Disk

Local Disk

2



Page 03 of 5

Template image(LV)

LVS

Template image(LV)

LVS

VG

VG

PV

PV

Local Disk

Local Disk

Figure 1: Local Virtual Machine Template working process

Because LV is a local storage, so rapidly and on-line updating virtual machine templates existed in multiple hypervisors is quite a challenge. There are 2 problems to be resolved: 1) Rapidly updating/deploying LV-based virtual machine template.

2) Updating virtual machine template with no impact to existing virtual machines based on the original template.

A straightforward...