KR20170105858A - Apparatus for accelerating virtual machine provisioning by use of bws and apparatus for managing the virtual machine and method thereof - Google Patents

Abstract

According to the present invention, in an apparatus for accelerating virtual machine provisioning by the use of a boot working set, and an apparatus and method for managing a virtual machine, the booting set that can boot the virtual machine when the virtual machine is provisioned is preliminarily distributed to all the compute nodes in a cloud system. After that, virtual machine provisioning speed can be accelerated by booting the virtual machine using the boot working set at each compute node without going through a network when the virtual machine is provisioned. In addition, by using a pre-stored boot-working set, even when multiple virtual machines are provisioned at the same time, network usage is significantly reduced so that a boot storm as a network bottleneck can be alleviated. The apparatus includes a boot working set generation part, and a boot working set management part.

Description

[0001] DESCRIPTION [0002] APPARATUS FOR ACCELERATING VIRTUAL MACHINE PROVISIONING BY USE OF BWS AND APPARATUS FOR MANAGING THE VIRTUAL MACHINE AND METHOD THEREOF [0003]

In particular, the present invention relates to a virtual machine, and particularly, a booting set capable of booting a virtual machine when a virtual machine is provisioned in a cloud system is previously distributed to all compute nodes in a cloud system and stored, By booting a virtual machine using a boot working set (BWS) on each compute node without going through it, it can accelerate the speed of virtual machine provisioning, and by using pre-stored boot working sets, And more particularly, to a virtual machine provisioning accelerator and a virtual machine management apparatus and method using a booting set that mitigates a bootstorm, which is a network bottleneck, because network usage is significantly reduced even when machines are provisioned at the same time.

In general, virtualization refers to a technology that can use one physical device as if it exists, and collecting the resources required for a computing environment is called a virtual machine.

At this time, the process of creating the above virtual machine and providing the operating system to the user is called provisioning. Hereinafter, the operation of provisioning the virtual machine will be briefly described.

First, when the virtual machine is provisioned, it sends the image to boot to the target compute node. Then, when the transfer is completed, create a virtual machine disk that backs up the image and boot using it. Then, the I / O for the image may be performed locally within the compute node. Also, if provisioning for the same image is later provisioned for the same image, additional network transmission is unnecessary by using the image transmitted to the compute node. However, when provisioning is performed simultaneously on a plurality of compute nodes, the network usage increases and a boot storm occurs.

Next, there is a method of provisioning a virtual machine from a volume other than provisioning a virtual machine from an image. In this method, the volume is created on the storage node and the boot image is written to the volume using iSCSI or other methods to make the created volume bootable. After this, you will be provisioned using that volume. However, in order to boot at this time, it takes much more time to provision the virtual machine from the image, since each booting volume requires a boot image.

One way to solve this problem is to create a volume on the storage node that backs up the boot image stored in the Image node when creating the volume, and provision it using this volume. This eliminates the need to write data to the volume at the time of creation, and allows the volume to be provisioned and used immediately.

However, when creating and provisioning a new volume, the volume portion is stored locally on the compute node during virtual machine provisioning because it is stored on the remote storage node. In this situation, when a large number of virtual machines are provisioned, the network usage in the cloud system increases and a boot storm occurs. This will affect the overall virtual machine provisioning speed as well as the performance of existing virtual machines.

On the other hand, the rate of virtual machine provisioning in the cloud system is an important factor in evaluating user satisfaction. When provisioning a virtual machine from a volume, simply write the boot image to the volume using iSCSI to create the volume on the storage node and make it bootable for all created volumes, and then use the virtual machine Provisioning can result in severe performance degradation when provisioning large volumes because the network is used without provisioning.

Also, to solve this problem, when creating a volume that backs up the boot image on the image node and provisioning the virtual machine, the time to create a bootable volume is reduced, but when the virtual machine is provisioned, Is provisioned using the network, so if a large number of virtual machines are provisioned, the network usage will increase and the virtual machine provisioning performance will be lowered.

(Patent Literature)

Republic of Korea Publication No. 10-2009-0065126 (Published date June 22, 2009)

Accordingly, in the present invention, a booting set capable of booting a virtual machine when a virtual machine is provisioned in a cloud system is previously distributed to all the compute nodes in the cloud system and stored, and then, when the virtual machine is provisioned, By booting a virtual machine using a bootstrapping set on a compute node, the speed of virtual machine provisioning can be accelerated. Moreover, even if multiple virtual machines are provisioned simultaneously by using a pre-stored booting set, the network usage can be significantly reduced And a bootstroke set that can mitigate a bootstorm, which is a network bottleneck phenomenon, to a virtual machine provisioning acceleration device and a virtual machine management apparatus and method.

The present invention relates to a virtual machine provisioning accelerator, wherein when a disk image of at least one virtual machine created in at least one compute node in a cloud system is registered, data necessary for booting the virtual machine among the disk images And a BWS manager for distributing the BWS to the compute node and controlling the virtual machine to boot at the compute node using the BWS.

Also, the BWS generator may check the data used during the booting of the disk image while booting the virtual machine using the disk image, and generate the BWS based on only the confirmed data.

The BWS generator may cause the compute node allocated to generate the BWS in the cloud system to generate the BWS.

The present invention also provides a virtual machine provisioning method comprising the steps of: receiving a disk image of a virtual machine to be created in at least one compute node in a cloud system; Generating a BWS, distributing the BWS to the compute node, and controlling the virtual node to boot using the BWS in the compute node.

In addition, the present invention provides a virtual machine management apparatus, wherein when a provisioning of a virtual machine is requested to a compute node in a cloud system, the BWS consisting of data necessary for booting the virtual machine among the disk images of the virtual machine is used, A virtual machine provisioning unit for booting the machine; and a data writing / reading unit for writing / reading data to / from the virtual machine, Determining whether the requested data is in the BWS or in the virtual disk of the virtual machine by referring to a hash table storing a hash value of the data and storing the requested data in the BWS or the virtual disk according to the determination result; (Input / Ou < RTI ID = 0.0 > tput) management section.

The I / O management unit may include an I / O processing unit for receiving the data request from the virtual machine, searching the BWS or the virtual disk for the requested data, and providing the requested data to the virtual machine, A determination unit for determining whether the requested data is in the BWS or the virtual disk and providing the determination result to the I / O processing unit, And a BWS reader unit for retrieving the requested data from the BWS when the data request is received from the I / O processing unit and providing the requested data to the I / O processing unit.

The hash value may be an offset value of a sector in which data is written on the virtual disk.

According to another aspect of the present invention, there is provided a virtual machine provisioning method comprising the steps of: booting a virtual machine using a BWS composed of data necessary for booting the virtual machine among disk images of a virtual machine at a compute node in a cloud system; Receiving a data request for reading or writing data from a virtual machine that has been written in the virtual machine, referring to a hash table storing a hash value of data written in the virtual machine, Determining whether the virtual disk exists in the virtual disk of the virtual machine, and searching the requested data in the BWS or the virtual disk according to the determination result and providing the requested data to the virtual machine.

According to the present invention, a virtual machine provisioning accelerator using a booting set, and a booting set capable of booting a virtual machine when a virtual machine is provisioned in a virtual machine management apparatus, are preliminarily distributed and stored in all the compute nodes in the cloud system There is an advantage in that the virtual machine provisioning speed can be accelerated by booting the virtual machine using the boot working set immediately at each compute node without going through the network during the virtual machine provisioning. In addition, by using the pre-stored booting set, even when multiple virtual machines are provisioned at the same time, the network usage is significantly reduced, which is advantageous in mitigating the bootstorm as a network bottleneck.

1 is a network configuration diagram of a virtual machine provisioning system according to an embodiment of the present invention;
FIG. 2 is a conceptual diagram of generating a BWS of a virtual machine in a virtual machine provisioning acceleration device according to an embodiment of the present invention and distributing the BWS to each compute node on a cloud system; FIG.
3 is a conceptual diagram for generating a BWS in a virtual machine management apparatus of a BWS generating node according to an embodiment of the present invention;
4 is a detailed configuration diagram of a virtual machine management apparatus according to an embodiment of the present invention;
5 illustrates an example of a hash table according to an embodiment of the present invention,
FIG. 6 is a flowchart illustrating a write operation for virtual machine provisioning in a virtual machine management apparatus according to an embodiment of the present invention. FIG.
FIG. 7 is a flow chart of a process for a read operation when a virtual machine is provisioned in a virtual machine management apparatus according to an embodiment of the present invention. FIG.

Hereinafter, the operation principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention, and these may be changed according to the intention of the user, the operator, or the like. Therefore, the definition should be based on the contents throughout this specification.

FIG. 1 illustrates a network configuration of a virtual machine provisioning system according to an embodiment of the present invention. The network includes a control node 100, a boot working set (BWS) node 130, A compute node 150, a block storage node 160, a storage node 170, and the like.

Hereinafter, operation of each node of the virtual machine provisioning system according to the embodiment of the present invention will be described in detail with reference to FIG.

First, the control node 100 receives a virtual machine creation request from a user via a network, controls the corresponding virtual machine to be provisioned in the compute node 150, And can manage the machine 152. That is, the control node 100 instructs provisioning of the virtual machine to each of the compute nodes 150 connected to the network on the cloud system. If there is such a virtual machine provisioning command, The machine 152 is provisioned.

The components controlled by the control node 100 may include a compute node management unit 102, a block storage node management unit 104, an image service unit 106, and the like.

The compute node management unit 102 manages virtual machine provisioning in the compute node 150 and resources used in each compute node 150. The block storage node management unit 104 is provided with the operation of the block storage node 160 and the provision of each of the compute nodes 150 on a storage device such as a virtual disk 162 provided in the block storage node 160 Information on the virtual disk resource of the virtual machine 152, and the like.

The image service 106 registers a disk image for the virtual machine 152 and performs booting of the virtual machine 152 from each compute node 150 when the virtual machine is provisioned. And a disk image for provisioning, if requested. At this time, the disk image may be stored in the virtual disk 162 on the block storage node 160 shared by the compute node 150.

When a disk image of a new virtual machine is registered on the image service unit 108, the virtual machine provisioning accelerator 106 extracts data necessary for booting the disk image, and sends a boot working set (BWS) And distributes the generated BWS to each of the compute nodes 150 in the cloud system in advance.

Accordingly, when provisioning the virtual machine 152 in each compute node 150, the virtual machine is booted using the BWS 138 that is distributed in advance to each compute node 150 without going through the network Thereby accelerating the virtual machine provisioning speed. In addition, by using the pre-deployed BWS 138, even when multiple virtual machines are provisioned at the same time, the network usage is significantly reduced and the boot storm, which is a network bottleneck, can be mitigated. In this case, the above-mentioned network usage amount refers to a network usage amount generated when all of the compute nodes 150 access the disk image of the virtual machine 152 stored in the block storage node 160 via the network , But is not limited thereto.

The compute node 150 refers to a node that has provisioned the virtual machine 152 requested by the user and processes the requested operation on the provisioned virtual machine 152.

When the BWS 138 for a newly registered virtual machine disk image is distributed to the image service unit 106 through the virtual machine provisioning accelerator 108 according to the embodiment of the present invention, The BWS 138 can be stored in a specific disk area.

In addition, each compute node 150 may provision the virtual machine 152 in response to a command from the control node 100. In provisioning the virtual machine 152 in each compute node 150, The virtual machine 152 is booted using the BWS 138 previously stored in the area so that the user can use the virtual machine 152. After the virtual machine 152 is booted, each of the compute nodes 150 accesses the entire disk image of the corresponding virtual machine 152 stored in the block storage node 160 for the rest of operations for provisioning of the virtual machine 152 To perform a virtual machine provisioning operation.

At this time, the provisioning operation of the virtual machine 152 may be performed by a virtual machine management apparatus (hypervisor) 154 installed in each compute node 150. The virtual machine management device 154 can read data from the booted virtual machine 152 as the BWS 138 is previously distributed and stored in each compute node 150 according to the embodiment of the present invention O manager for controlling the access to the virtual disk 162 allocated to the corresponding virtual machine 152 on the BWS 138 and the block storage node 160 for a write request or a write request 156). The I / O manager 156 manages the BWS 138 when it receives a data request from the virtual machine 152 after booting the virtual machine 152 as the BWS 138 is pre-deployed according to an embodiment of the present invention. Or the data access to the virtual disk 162 on the block storage node 160 so that data access can be performed more efficiently.

That is, the virtual machine management device 154 sends the BWS 138 for booting of the virtual machine 152 distributed from the virtual machine provisioning acceleration device 108 on the control node 100 to the specific By booting the virtual machine 152 quickly with the BWS 138 when an instruction to store the virtual machine 152 in the disk area and request to provision the virtual machine 152 from the control node 100 is received, So that the user can use the virtual machine 152 even before.

Then, when there is a data request from the virtual machine 152 after the virtual machine 152 has been booted, the virtual machine management device 154 sends the BWS () to the local area such as the memory of the compute node 150 138 can be read from the BWS 138 and read from the BWS 138 and read from the virtual disk 162 of the remote storage block 160, Provision virtual machines from disk images and improve the performance of virtual machine provisioning from volumes, mitigating bootstorm problems that can occur when multiple virtual machines are provisioned at the same time.

The BWS generating node 130 is a node that generates the BWS 138 for the virtual machine 132 in response to a command of the virtual machine provisioning accelerator 108. The virtual machine management apparatus 134 And similarly to the operation in the compute node 150, the disk image is downloaded from the image service unit 106 and the virtual machine 132 is provisioned. In addition, the BWS generation node 130 may generate the BWS 138 by extracting data used at the time of booting the virtual machine 132 in the provisioning process of the virtual machine 132. At this time, the virtual machine 132 provisioned in the BWS generation node 130 is transferred to the BWS generation node 130 in order to generate the BWS 138 of the virtual machine 152 requested to be created in the compute node 150 But is not limited to, a virtual machine 132 for provisioning in advance.

The block storage node 160 is a node having storage resources shared by each computer node 150 on the cloud system and is provided with a provisioning function for each compute node 150 using a storage device such as a hard disk The virtual machine 152 stores the disk image of the virtual machine 152 in the virtual machine 152 and allocates the virtual disk 162 to the virtual machine 152 to generate To the corresponding virtual disk 162. In this case,

The storage node 170 is a mass storage device such as a hard disk. The storage node 170 stores general data stored in each compute node 150 in the cloud system, and stores image files and the like before the virtual machine 152 is provisioned. It can also be saved.

Figure 2 illustrates the concept of creating a BWS 138 of a virtual machine 152 in a virtual machine provisioning accelerator 106 and distributing it to each compute node 150 on a cloud system in accordance with an embodiment of the present invention .

Hereinafter, the operation of generating the BWS 138 of the virtual machine 150 in the virtual machine provisioning accelerator 108 and distributing it to each compute node 150 on the cloud system will be described in more detail with reference to FIG. 2 .

First, the virtual machine provisioning accelerator 108 may include a BWS generator 200, a BWS manager 202, and the like.

The BWS generator 200 generates a BWS 138 for the disk image when the disk image of the new virtual machine 152 is registered in the image service unit 106. At this time, the BWS generating unit 200 may instruct the BWS generating node 130 to generate the BWS 138 for the disk image of the newly registered virtual machine 152. The BWS generator 200 generates the BWS 138 in the BWS generating node 130 by transmitting the BWS generating command to the BWS generating node 130 in the generation of the BWS 138. However, But is not limited thereto. That is, the BWS generating unit 200 may be configured to generate the BWS 138 for the newly registered virtual machine 152 directly.

When the BWS 138 of the virtual machine 152 newly registered in the image service unit 106 is generated in the BWS generating node 130 or the like according to the operation of the BWS generating unit 200, The BWS 138 is distributed to each compute node 150 on the cloud system so that the corresponding virtual machine 152 can be accessed by using the BWS 138 without accessing the block storage node 160 on the network from the specific compute node 150. [ ) So that the virtual machine 152 can be booted quickly.

Next, in operation, when a disk image for a new virtual machine 152 is registered in the image service unit 106 on the control node 100, the BWS generation unit 200 of the virtual machine provisioning acceleration device 108 And instructs the BWS generation node 130 to generate the BWS 138 for the newly registered disk image.

At this time, the BWS generating node 130 is a node that generates the BWS 138 for the virtual machine 152 in response to a command of the virtual machine provisioning accelerator 108, and similarly to the compute node 150, And the virtual machine 152 is provisioned by downloading the disk image from the image service unit 106 in the same manner as the operation in the compute node 150. [

That is, when the virtual machine creation command is received, the virtual machine management device 134 of the BWS generation node 130 downloads the disk image of the virtual machine 152 from the image service unit 106 and receives the solid state disk (SSD) 136 and provision the virtual machine 152 using the disk image stored in the SSD 136. [

At this time, the virtual machine management device 134 creates a BWS 138 in which data for backing up the disk image is empty, and reads the read image data from the virtual machine 152 of the BWS generating node 130 ), The virtual machine 152 is booted using the disk image stored in the SSD 136 according to the request (S200), and the data read from the disk image in the booting process is copied to the BWS 138 in the copy-on-read manner And generates the BWS 138 (S202). Then, the virtual machine management device 134 can distribute the created BWS 138 to each of the compute nodes on the cloud system under the control of the BWS management unit 202 (S204).

3 illustrates a concept of generating a BWS 138 in a virtual machine management device 134 of a BWS generation node 130 according to an embodiment of the present invention.

3, when a read request for a disk image is received from the virtual machine 152 (S300), the virtual machine management device 134 sends back a disk image 300 to be booted in the SSD 136 to the backing (BWS image 302) formatted as a blank (for example, a virtual disk (Qcow2, etc.) that supports Copy-on-Write) pointing to a backing file and a copy-on- And boot (S302). Thus, the BWS 138, in which the data to be read to boot the virtual machine 152 on the disk image 300 is copied to the BWS image 302 and consists only of the data used at boot time of the virtual machine 152, (S304). At this time, the data read from the disk image 300 is provided to the virtual machine 152 through the virtual machine management device 134 (S306), and the provisioning of the virtual machine 152 is performed.

That is, the virtual machine management device 134 generates the empty BWS image 302 as described above, and creates a blank Copy-on-Write (Qcow2, etc.) format It is possible to create the BWS 138 naturally by writing the portion read from the original disc image 300 to the BWS image 302 of the BWS image 302. [

When the BWS 138 is created as described above, the BWS management unit 202 of the virtual machine accelerator 108 transmits the BWS 138 of the virtual machine 152 generated in the BWS generation node 130 to the respective computers The BWS 138 is stored in each compute node 150 in the case where there is a provisioning request for the corresponding virtual machine 152 from the user To boot the virtual machine 152 so that the virtual machine provisioning can be performed quickly.

FIG. 4 illustrates a detailed configuration of a virtual machine management device 154 according to an embodiment of the present invention, and may include a virtual machine provisioning unit 155, an I / O management unit 156, and the like.

Hereinafter, the operation of each component of the virtual machine management device 154 according to the embodiment of the present invention will be described in detail with reference to FIG.

First, the virtual machine provisioning unit 155 acquires the virtual machine 152 previously distributed from the virtual machine provisioning accelerator 108 when the virtual machine 150 is requested to be provisioned at each compute node 150 in the cloud system. The virtual machine 152 is booted using the BWS 138 of the virtual machine 152 and the entire disk image of the corresponding virtual machine 152 downloaded to the block storage node 160 after the virtual machine 152 is booted Perform machine provisioning.

The I / O management unit 156 manages the virtual machine 152 after the virtual machine 152 is booted using the BWS 138 of the virtual machine 152 distributed to the compute node 150 according to the embodiment of the present invention. 152 to the virtual disk 162 allocated to the corresponding virtual machine 152 on the BWS 138 or the block storage node 160 and provides the requested data to the virtual machine 152 And manages the operation.

That is, when data is read or written on the booted virtual machine 152 to receive a data request for reading or writing data from the virtual machine 152, the I / A hash table 406 storing a hash value for the data on which the write has been performed is used to determine whether the requested data is in the BWS 138 or in the virtual machine 152 on the block storage node 160. [ And provides the virtual machine 152 with the data requested by the BWS 138 or the virtual disk 162 according to the determination result.

As shown in FIG. 4, the I / O management unit 156 includes an I / O processing unit 400, a decision maker 402, a BWS reader unit 408, a hash table management unit (hash) table manager 404 and the like. Hereinafter, the operation of each component of the I / O manager 156 will be described in more detail.

When the I / O processing unit 400 receives the data request from the virtual machine 152, the I / O processing unit 400 searches the virtual disk 162 on the BWS 138 or the block storage node 160 for the requested data, .

That is, the I / O processing unit 400 is an interrupt handler, and it only fetches an I / O request from the virtual machine 152 before the BWS reader unit 408. The I / O request while waiting for an API (application program interface) to read the I / O while it is determined that the requested data is in the BWS 138, The BWS reader 138 calls an API that reads the I / O of the BWS 138 and sends an event to the BWS reader 138. As soon as the BWS reader 138 receives the event, Make the data accessible.

That is, when the I / O request is received from the virtual machine 152 and the BWS reader unit 408 waits until the I / O is completed, the BWS The reader unit 402 waits without being able to perform I / O. Accordingly, in the embodiment of the present invention, when an I / O request is generated from the virtual machine 152, the I / O processing unit 400 first snatches the I / O request, It is determined whether the data is in the BWS 138 or in the virtual disk 162 on the block storage node 160 and only when the I / O requested data is found in the BWS 138, (408). As a result, I / O processing can be performed in an asynchronous manner with respect to an I / O request from the virtual machine 152, thereby improving performance.

The hash table management unit 404 receives the hash value of the data written on the virtual machine 152 and stores the hash value in the hash table 406. [ In this case, the hash value may be, for example, an offset value of a sector in which data written on the virtual disk 162 is stored, but is not limited thereto. 5, the hash table management unit 404 manages different offset values on the same sector in a linked-list as shown in FIG. 5, and obtains a hash value Can be easily retrieved.

The determination unit 402 refers to the hash table 406 managed by the hash table management unit 404 and determines whether the requested data from the virtual machine 152 exists in the BWS 138 or on the virtual storage unit 160 163), and provide the determination result to the I / O processing unit 400. The I /

When the I / O request is received from the virtual machine 152, the I / O processor 400 determines whether the I / O requested data exists in the BWS 138 or in the virtual disk 162 on the block storage node 160 The determination unit 402 requests the determination.

Then, the determining unit 402 determines whether the I / O requested data has been written by referring to the hash table 406 and determines whether the I / O requested data is in the BWS 138 160) virtual disk 162, and provides the determination result to the I / O processing unit 400.

At this time, since the hash value of the data once written in the virtual machine 152 is all stored in the hash table 406 as the sector offset value, the determination unit 402 determines whether or not the I / If the data is entirely in the hash table 406, it can be determined that the I / O requested data is in the virtual disk 162 on the block storage node 160 and the data corresponding to the I / The I / O requested data is in the BWS 138. However, the present invention is not limited thereto.

The BWS reader unit 408 can read the data stored in the BWS 138. If there is a request for data on the BWS 138 from the I / O processing unit 400, To the I / O processing unit 400. The I /

FIG. 6 is a flowchart illustrating a write operation for virtual machine provisioning in a virtual machine management apparatus according to an embodiment of the present invention. Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 4 to 6. FIG.

After the virtual machine 152 is booted at the compute node 150, the user is allowed to use the virtual machine 152, and from the virtual machine 152 in accordance with the use of the virtual machine 152, A data request may occur to the device 154. This data request is processed by the I / O manager 156 of the virtual machine management device 154.

At this time, if the data request is a write request for data (S600), the I / O manager 156 of the virtual machine management device 156 accesses the corresponding virtual machine (not shown) on the block storage node 160 152 on the virtual disk 162 (S602).

After writing the data, the I / O manager 156 stores the offset value of the sector on the virtual disk 162 storing the written data in the hash table 406 (S604).

The reason why the offset value of the sector on the virtual disk 162 of the written data is recorded as the hash value in the hash table 406 is that if there is a read request for data from the virtual machine 152, To be read from the BWS 138 or from the virtual disk 162 on the block storage node 160.

In other words, the I / O manager 156 stores the sector offset value of the data once written in the virtual machine 152 as a hash value on the hash table 406. Thereafter, for example, the virtual machine 152 O requested data is stored in the hash table 406. If the I / O requested data is in the hash table 406, the I / O requested data is determined to be in the virtual disk 162 on the block storage node 160, The I / O requested data is in the BWS 138 if it is not in the BWS 406.

FIG. 7 shows a processing flow for a read operation in virtual machine provisioning in a virtual machine management apparatus according to an embodiment of the present invention. Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 4 to 5 and FIG.

After the virtual machine 152 is booted at the compute node 150, the user is allowed to use the virtual machine 152, and from the virtual machine 152 in accordance with the use of the virtual machine 152, A data request may occur to the device 154. This data request is processed by the I / O manager 156 of the virtual machine management device 154.

At this time, if the data request is a read request for data (S700), the I / O manager 156 of the virtual machine management device 154 checks whether the data requested to be read has been written before (S702) .

At this time, the I / O manager 156 refers to the hash table 406 to determine whether the data requested to be read has been written before. That is, since the sector offset value of the data once written in the virtual machine 152 is all stored in the hash value on the hash table 406, the I / O management unit 156 reads the offset value of the sector from the virtual machine 152 If the data requested to be read is in the hash table 406, it is determined that the data requested to be read has been written before. If the data requested to be read is not in the hash table 406, the data requested to be read has not been written before .

As a result of the above determination, when it is determined that the data requested to be read has been written before, it means that the corresponding data exists in the virtual disk 162 on the block storage node 160. Therefore, the I / The read requested data is read from the virtual disk 162 on the block storage node 160 using the hash value of the corresponding data on the hash table 406 in step S704 and the read data is provided to the virtual machine 152 (S708).

If it is determined that the data requested to be read has not been written before, the I / O manager 156 refers to the read request in the BWS 138, (S704), and provides the read data to the virtual machine 152 (S708).

As described above, according to the present invention, a virtual machine provisioning accelerator using a booting set, and a booting set capable of booting a virtual machine at the time of virtual machine provisioning in a virtual machine management apparatus, are provided to all the compute nodes in the cloud system in advance After provisioning and storing, the virtual machine provisioning speed can be accelerated by booting the virtual machine using the boot working set at each compute node without going through the network in the virtual machine provisioning. In addition, by using pre-stored booting sets, even when multiple virtual machines are provisioned at the same time, the network usage is significantly reduced, which can alleviate the boot storm as a network bottleneck.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention should not be limited by the described embodiments but should be defined by the appended claims.

100: control node 102: compute node management unit
104: block storage node management unit 106: image service unit
108: Virtual Machine Provisioning Accelerator 130: BWS Generation Node
136: SSD 138: BWS
150: compute node 152: virtual machine
154: Virtual machine management device 156: I / O manager
160: Block storage node 162: Virtual disk
170: storage node

Claims (8)

A BWS (Boot Working Set) generating a BWS (Boot Working Set) including data necessary for booting the virtual machine among the disk images when a disk image of at least one virtual machine created in at least one compute node in the cloud system is registered; A generating unit,
A BWS management unit for distributing the BWS to the compute node and controlling the virtual machine to boot using the BWS at the compute node,
The virtual machine provisioning acceleration device comprising:
The method according to claim 1,
Wherein the BWS generator comprises:
Wherein during booting of the virtual machine using the disk image, the data used during the booting of the disk image is checked, and the BWS is generated using only the confirmed data.
3. The method of claim 2,
Wherein the BWS generator comprises:
And cause a compute node assigned to create the BWS in the cloud system to generate the BWS.
Receiving a disk image of a virtual machine to be created in at least one compute node in the cloud system,
Generating a BWS including data necessary for booting the virtual machine among the disk images;
Distributing the BWS to the compute node;
Controlling the virtual node to boot using the BWS at the compute node
/ RTI >
A virtual machine provisioning unit for booting the virtual machine using a BWS composed of data necessary for booting the virtual machine among disk images of the virtual machine when provisioning of a virtual machine is requested to a compute node in the cloud system;
When a data request for reading or writing the data is received from the virtual machine by reading or writing data on the booted virtual machine, a hash table storing a hash value for the data written on the virtual machine Determines whether the requested data is in the BWS or the virtual disk of the virtual machine, searches the requested data in the BWS or the virtual disk according to the determination result, and provides I / O (Input / Output) management unit
The virtual machine management apparatus comprising:
6. The method of claim 5,
Wherein the I /
An I / O processing unit for receiving the data request from the virtual machine, searching the BWS or the virtual disk for the requested data, and providing the requested data to the virtual machine;
A determination unit for determining whether the requested data is in the BWS or the virtual disk by referring to the hash table, and providing the determination result to the I / O processing unit;
A BWS reader unit which is capable of reading data stored in the BWS and retrieving the requested data from the BWS when the data request is received from the I / O processing unit and providing the requested data to the I /
The virtual machine management apparatus comprising:
6. The method of claim 5,
The hash value,
Wherein the virtual disk is an offset value of a sector in which the data on which the writing is performed is stored.
Booting the virtual machine using a BWS which is composed of data necessary for booting the virtual machine among disk images of the virtual machine at a compute node in the cloud system,
Receiving a data request for reading or writing data from the booted virtual machine;
Determining whether the requested data is in the BWS or in a virtual disk of the virtual machine by referring to a hash table storing a hash value of the data written in the virtual machine,
Searching the requested data in the BWS or the virtual disk according to the determination result and providing the requested data to the virtual machine
/ RTI >

Images