KR20180051830A - Method and apparatus for establishing virtual cluster by mounting of readable and writable virtual disks - Google Patents

Abstract

The present invention relates to a method for building a virtual cluster by merge-mounting readable and writeable virtual disks and an apparatus thereof. According to an embodiment of the present invention, a method for building a virtual cluster having a plurality of virtual machines includes the following steps of: receiving a provisioning request for the virtual cluster having the plurality of virtual machines; creating a first disk shared among the plurality of virtual machines to be accessible by the plurality of virtual machines corresponding to a provisioning request for the virtual cluster and having software required in common among the plurality of virtual machines; creating a second disk allowing a writing work on each virtual machine in association with the software; and mounting the first disk and the second disk by merging the first disk into the second disk. A merge-type virtual disk capable of performing a writing work is provided to perform merge-mounting with respect to a read-only virtual disk, so each virtual machine performs a writing work on the shared virtual disk, thereby providing a method for building a virtual cluster by merge-mounting readable and writable virtual disks and an apparatus thereof.

Description

TECHNICAL FIELD [0001] The present invention relates to a method and apparatus for constructing a virtual cluster by merge mounting of a read / write virtual disk,

The present invention relates to a method and an apparatus for constructing a virtual cluster through merge mounting of a readable and writable virtual disk, and more particularly, to a method and apparatus for constructing a virtual cluster by merging virtual disks, To a method and apparatus for constructing a virtual cluster through merge mounting of a readable and writable virtual disk.

As network technology and storage technologies have evolved, platform technology, or virtualization technology, has been actively researched to apply analytical processing techniques for large amounts of data stored in shared storage. Particularly, in order to effectively analyze a large amount of data, a technique of processing distributed and stored data in parallel is important. However, in order to process large amount of data distributed in parallel, it is necessary to use a virtual cluster technology that utilizes one or more processing computing nodes as clusters.

A virtual cluster is a set of virtual machines installed with software that performs a specific function and is connected to a network. To create virtual clusters, you must go through the steps of provisioning virtual computing resources. Virtual disk provisioning includes virtual cluster placement provisioning and virtual cluster disk provisioning. Virtual cluster placement provisioning refers to a process for creating virtual clusters based on resource information of virtual machines included in a virtual cluster to be created by placing them in a virtualized physical system. Virtual cluster disk provisioning refers to the process of creating a virtual disk to create a virtual machine in a virtual cluster. Here, the process of installing and setting the software requested by the user in each of the created virtual disks, that is, the system software and the application software, directly affects the total virtual disk provisioning time.

[Related Technical Literature]

A virtual machine providing method, a system, and a recording medium on which the program is recorded (Patent Document 10-2014-0055481)

One or more virtual machines may be presented to the virtual machine as read-only virtual disks in order to share the virtual disks. If the virtual disk is not provided as read-only, the file system of the shared virtual disk may fluctuate when each virtual machine performs a write operation.

Therefore, the inventors of the present invention provide a separate merge-type virtual disk capable of performing a write operation, and merge-mount the read-only virtual disk, thereby enabling each virtual machine to share a virtual disk, And a method and apparatus for constructing the same.

Another problem to be solved by the present invention is to efficiently use the storage space of a virtual disk by merely mounting a read-only virtual disk, which is already created, and a virtual disk capable of a write operation to a shared virtual disk, Thereby shortening the provisioning time.

The problems of the present invention are not limited to the above-mentioned problems, and other problems not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, there is provided a method for establishing a virtual cluster through merging mounting of a readable and writable virtual disk, the method comprising: receiving a provisioning request for a virtual cluster having a plurality of virtual machines; Creating a first disk in which software required in common to a plurality of virtual machines is installed, wherein the first disk is shared and accessible by a plurality of virtual machines in response to a provisioning request for the virtual cluster; Creating a second disk capable of write operation, and mounting the first disk and the second disk by merging.

According to another aspect of the present invention, there is provided a method of constructing a virtual cluster through merge mounting of a readable and writable virtual disk, the method including storing data in which a location path of a second disk is recorded on a first disk, The disk can be set to be read only.

According to another aspect of the present invention, there is provided a method for constructing a virtual cluster through merge mounting of a virtual disk capable of reading and writing, comprising: receiving a back-up request of a virtual machine; And the file that can be written may include a file copied from the first disk that was conventionally read-only.

According to another aspect of the present invention, files associated with the software may be stored on the second disk.

According to another aspect of the present invention, the step of mounting the first disk and the second disk by merging includes the step of creating the merged first disk and the second disk so that they appear as one tree.

According to another aspect of the present invention, the step of mounting the first disk and the second disk by merging includes the steps of: when the same file or folder exists in the first disk and the second disk, Lt; / RTI >

According to another aspect of the present invention, software exists in a plurality of versions, and the step of creating a first disc includes a step of creating a plurality of first discs in which a plurality of versions of each software are installed, May be a step of merging and mounting a plurality of the first disk and the second disk.

According to another aspect of the present invention, the step of mounting may comprise merging and mounting a plurality of first disks such that different files are accessible in each of the plurality of versions of software.

According to another aspect of the present invention, there is provided a method for constructing a virtual cluster through merge mounting of a virtual disk capable of reading and writing, wherein when a write operation is requested to a file stored in the first disk, A step of copying to a disk, and a step of performing a write operation on a file copied to the second disk.

According to an aspect of the present invention, there is provided an apparatus for constructing a virtual cluster having a plurality of virtual machines, the apparatus comprising: A virtual disk provisioning process receiving unit for receiving a provisioning request for a virtual cluster having a virtual machine, and software required in common to a plurality of virtual machines accessible and accessible by a plurality of virtual machines in response to a provisioning request for the virtual cluster And a virtual disk creating unit for creating a first disk, creating a second disk in each of the plurality of virtual machines capable of performing a write operation in association with software, and mounting the first disk and the second disk by merging.

According to another aspect of the present invention, the virtual disk creation unit stores data in which the location path of the second disk is recorded in the first disk, and the first disk can be set to be capable of only the read operation.

According to another aspect of the present invention, a virtual disk provisioning process receiving unit receives a backup request of a virtual machine, a virtual disk creating unit stores a file capable of performing a write operation stored in a second disk, And may include files copied from the first read-only disk.

According to another aspect of the present invention, files associated with the software may be stored on the second disk.

According to another aspect of the present invention, the virtual disk creating unit may create the merged first disk and the second disk as a single tree.

According to another aspect of the present invention, the virtual disk creation unit may be configured such that, when the same file or folder exists in the first disk and the second disk, the same file or folder of the second disk is accessed.

According to another aspect of the present invention, software exists in a plurality of versions, and the virtual disk creating unit creates a plurality of first disks each having a plurality of versions of software, Can be merged and mounted.

According to another aspect of the present invention, the virtual disk creating unit may merge and mount a plurality of first disks so that different files are accessible in each of the plurality of versions of the software.

According to another aspect of the present invention, when a write operation is requested to a file stored in the first disk, the virtual disk creation unit copies the file stored in the first disk to the second disk, The write operation can be performed.

The details of other embodiments are included in the detailed description and drawings.

The present invention provides a separate coherent virtual disk capable of performing a write operation in a virtual cluster, and by merge mounting with a read-only virtual disk, a virtual cluster in which each virtual machine can perform a write operation to a shared virtual disk There is an effect that a construction method and an apparatus can be provided.

The present invention relates to a method of efficiently using storage space of a virtual disk and shortening a time required for provisioning a virtual disk by merging and mounting a read-only virtual disk that has already been created and a virtual disk capable of being written to a shared virtual disk There is an effect that can be.

The effects according to the present invention are not limited by the contents exemplified above, and more various effects are included in the specification.

FIG. 1 is a diagram for explaining virtual disk provisioning according to an embodiment of the present invention.
2 is an exemplary block diagram for explaining a virtual cluster establishing apparatus through merge mounting of a readable and writable virtual disk according to an embodiment of the present invention.
FIG. 3 illustrates a procedure for constructing a virtual cluster according to a method of constructing a virtual cluster through merge mounting of a read / write virtual disk according to an embodiment of the present invention.
FIG. 4 illustrates a virtual disk sharing method of a virtual machine using a merged virtual disk according to an embodiment of the present invention.
5 illustrates a virtual disk file structure of a virtual machine in which a plurality of directories are merged through merge mounting according to another embodiment of the present invention.
FIG. 6 illustrates a file system hierarchical structure of a merged virtual disk when a virtual machine uses various application software according to another embodiment of the present invention.
Figures 7 (a) through 7 (d) illustrate the effect of virtual disk provisioning for building a virtual cluster in accordance with another embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention, and the manner of achieving them, will be apparent from and elucidated with reference to the embodiments described hereinafter in conjunction with the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims.

The shapes, sizes, ratios, angles, numbers, and the like disclosed in the drawings for describing the embodiments of the present invention are illustrative, and thus the present invention is not limited thereto. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Where the terms 'comprises', 'having', 'done', and the like are used herein, other parts may be added as long as '~ only' is not used. Unless the context clearly dictates otherwise, including the plural unless the context clearly dictates otherwise.

In interpreting the constituent elements, it is construed to include the error range even if there is no separate description.

Although the first, second, etc. are used to describe various components, these components are not limited by these terms. These terms are used only to distinguish one component from another. Therefore, the first component mentioned below may be the second component within the technical spirit of the present invention.

Like reference numerals refer to like elements throughout the specification unless otherwise specified.

It is to be understood that each of the features of the various embodiments of the present invention may be combined or combined with each other partially or entirely and technically various interlocking and driving is possible as will be appreciated by those skilled in the art, It may be possible to cooperate with each other in association.

Hereinafter, terms used in this specification will be defined.

As used herein, the term " provisioning " means a procedure for allocating, arranging, and distributing resources according to a user's request. Here, the resource may mean a memory, CPU, etc. of the server. Specifically, provisioning refers to a procedure for creating a virtual disk in which software is installed in a storage of a server according to a user's request, and placing the virtual disk in a virtual machine so that the software can be operated.

FIG. 1 is a diagram for explaining virtual disk provisioning according to an embodiment of the present invention.

Referring to FIG. 1 (a), the virtual machine 110 includes a virtual disk 120 in which software 130 is installed. The software 130 may include system software 131, first application software 132, and second application software 133.

Referring to FIG. 1 (a), a virtual disk 120 in which a root file system is installed is a device necessary for driving the virtual machine 110. The virtual machine 110 including the virtual disk 120 can boot from the root file system. The virtual disk 120 may be created in the form of a file or a logical volume in which a file system in an operating system of a physical machine exists, unlike a general hard disk. Accordingly, the virtual disk 120 forms a file system required for each virtual machine 110 in the created file or logical volume, and is provided to the virtual machine 110. The virtual disk 120 is also provided with application software such as the desired system software 131, the first application software 132 and the second application software 133, and a version of the system software 131 different from the operating system of the physical machine And the virtual disk 120 may be provided to the virtual machine 110. [

Referring to FIG. 1 (a), the virtual cluster establishing apparatus provision the virtual disk 120 by installing the software 130 in the virtual disk 120. The virtual cluster establishing apparatus creates an empty virtual disk 120 to create a virtual disk 120 in which the software 130 is installed. Subsequently, the virtual cluster establishing apparatus installs Debian 8.0 as the system software 131, Open JDK 7.0 as the first application software 132, and Hadoop 2.6.0 as the second application software 133 in the empty virtual disk 120 . Finally, the virtual cluster establishing apparatus sets the software 130 installed in the virtual disk 120. Specifically, the virtual cluster establishing apparatus performs settings necessary to execute Debian 8.0 as the system software 131, Open JDK 7.0 as the first application software 132, and Hadoop 2.6.0 as the second application software 133 . In FIG. 1A, the virtual disk 120 may be an integrated virtual disk, but the present invention is not limited thereto. The virtual disk may be implemented as a merged virtual disk in which a plurality of virtual disks each have one software and can be combined with each other have.

Referring to FIG. 1 (b), the virtual cluster establishing apparatus may create a virtual disk 140 including the same software by duplicating a virtual disk 120 created in advance.

Referring to FIG. 1B, the virtual cluster establishing apparatus includes Debian 8.0 as the system software 131, Open JDK 7.0 as the first application software 132, and Debian 8.0 as the first application software 132 according to the virtual disk creation procedure of FIG. 2 application software 133 including Hadoop 2.6.0 is installed to create the virtual disk 140. [ Thus, the virtual disk 140 also includes Debian 8.0, Open JDK 7.0, which is the first application software 132, and Hadoop 2.6.0, which is the second application software 133. [ Provisioning a virtual disk through replication can be faster than creating a virtual disk through installation. Specifically, virtual disk creation through installation installs software that is actually needed for the virtual disk. On the other hand, virtual disk creation through replication is faster than virtual disk creation through installation because it only takes time to replicate software installed on a pre-created virtual disk. In addition, the creation of a virtual disk through replication is performed by setting the software installed in the virtual disk to replicate the virtual disk, thereby avoiding the step of setting up the software for creation of the virtual disk through replication. Can be created quickly. Therefore, the virtual cluster establishing apparatus stores the assets required for replicating the virtual disk in the reusable asset repository, and creates the virtual disk more quickly based on the stored assets.

Accordingly, the virtual cluster establishing apparatus creates a virtual disk in which software is installed according to a user's request, and constructs a virtual cluster including a plurality of virtual machines in which the created virtual disk is installed.

2 is an exemplary block diagram for explaining a virtual cluster establishing apparatus through merge mounting of a readable and writable virtual disk according to an embodiment of the present invention.

2, the virtual cluster establishing apparatus 200 includes a virtual cluster provisioning process receiving unit 210, a reused virtual disk searching unit 220, a virtual cluster provisioning process performing unit 211, a virtual cluster provisioning starting unit 212, A virtual cluster provisioning process observing unit 213, a virtual disk provisioning procedure generating unit 230, and a virtual disk creating unit 240. [

Referring to FIG. 2, the virtual cluster provisioning process receiving unit 210 receives a provisioning request for a virtual cluster using XML RPC (Remote Procedure Call). The virtual cluster may be a collection of a plurality of different virtual machines. Here, the virtual machine may include a virtual disk in which software is installed. At this time, the received provisioning request is a provisioning request for building a virtual cluster by merging virtual disks capable of reading and writing. In addition, the virtual cluster provisioning process receiving unit 210 may determine a virtual cluster provisioning request through a merged virtual disk when two or more of the received provisioning requests include the same software. The virtual cluster provisioning process receiving unit 210 drives the XML RPC server and delivers the received virtual cluster provisioning request to the virtual cluster provisioning process performing unit 211. The provisioning request for the virtual cluster received by the virtual cluster provisioning process receiving unit 210 includes the software requirements installed in the virtual machines of the virtual cluster requested by the user. The virtual cluster provisioning process performing unit 211 parses the received virtual cluster provisioning request. In addition, the virtual cluster provisioning process performing unit 211 stores the task object parsed in the internal buffer to manage the progress status of the virtual cluster provisioning task. All the virtual cluster provisioning processes of the present invention are performed by calling a subcomponent by the virtual cluster provisioning process performing unit 211. [ Here, the sub-component refers to a virtual cluster establishing apparatus 200 such as a reuse virtual disk searching unit 220, a virtual disk provisioning procedure generating unit 230 and a virtual disk creating unit 240, which are components of the virtual cluster establishing apparatus 200 ). ≪ / RTI > Each subcomponent receives, processes, and returns a task to be performed by the virtual cluster provisioning process performing unit 211 on a task basis. In addition, each subcomponent includes a task execution unit that calls stepwise processing logic to be executed based on the status information of the task. The virtual cluster provisioning initiation unit 212 is a component that drives and terminates subcomponents existing in the virtual cluster establishing apparatus 200. The subcomponents of the virtual cluster establishing apparatus 200 are operated and managed by the virtual cluster provisioning initiation unit 212. The virtual cluster provisioning process observing unit 213 periodically monitors the progress of a job managed by the virtual cluster provisioning process performing unit 211 and transmits the progress status to the external system. Here, the external system may be a web-based system that provides a virtual cluster provisioning service. Specifically, the external system determines the number of virtual machines in the virtual cluster desired by the user, the specification of virtual resources such as VCPU, memory, and virtual disk space to be held by the virtual machine, system and application software and setting information of the virtual machine, Time, space constraints, and so on. That is, the external system may transmit a virtual cluster provisioning creation request to the virtual cluster provisioning process receiving unit 210.

The reusable virtual disk searching unit 220 searches for a virtual disk stored in the reusable asset storage 300 in order to search for reusability of a virtual disk to be created in response to a provisioning request for a virtual cluster. Specifically, the reusable virtual disk searching unit 220 searches the reusable asset storage 300 for a reusable merged virtual disk. Herein, the merged virtual disk means a virtual disk that can be merged with a plurality of virtual disks having different software installed therein. The reusable asset repository 300 stores the output of all the software created in the virtual disk provisioning management device 200. [ The virtual disk provisioning procedure generated by the virtual disk provisioning procedure generation unit 230 and the reuse virtual cluster provisioning procedure, the reusable virtual disk, and the reusable virtual disk provisioning procedure, which are received from the external system, It is a software installation and setup program. The reusable virtual disk searching unit 230 may assign an integer identifier applying a hash function to the feature model of the virtual disk to be stored in the reusable asset store so that the existing virtual disk can be retrieved from the reusable asset store 300 .

The virtual disk provisioning procedure determining unit 240 determines the provisioning procedure of the virtual disk according to the search result of the reuse virtual disk searching unit 230. Specifically, the virtual disk provisioning procedure determination unit 240 determines whether or not to create a merged virtual disk for a virtual cluster having a plurality of virtual machines, through a new installation or replication, through a virtual disk provisioning procedure and method . The virtual disk provisioning procedure generator 240 searches the reusable asset repository 300 for a software installer required for the installation and updates the virtual disk provisioning procedure based on the installer of the retrieved software, Create a procedure. At this time, the virtual disk provisioning procedure generation unit 240 generates a procedure for installing a virtual disk including each of an operating system virtual disk corresponding to operating system software and application software virtual disks corresponding to application software. The generated procedure includes the operating system software name and version information. The virtual disk provisioning procedure generation unit 240 may also generate a procedure for creating a virtual disk to be reusable later. When there is a reusable virtual disk, the virtual disk provisioning procedure generator 240 searches for a location where the reusable virtual disk is stored and creates a provisioning procedure for the virtual disk to be created based on the replicated and set assets. That is, the virtual disk provisioning procedure generation unit 240 generates a reusable virtual disk provisioning procedure in which the virtual disk provisioning procedure generation unit 240 replicates the virtual disk based on the reusable virtual disk or installs additional application software. Therefore, the virtual disk provisioning procedure generation unit 240 must generate a replay virtual disk provisioning procedure by duplicating a virtual disk to be reused, and installing and setting necessary application software. The virtual disk to be replicated is analyzed by the reusable virtual disk searching unit 230 and retrieved as an integer identifier obtained by using the hash function. The virtual disk provisioning procedure generation unit 240 generates reuse virtual disk provisioning procedure by parsing the reused asset description of the retrieved reusable virtual disk.

The virtual disk creation unit 240 creates a virtual disk according to the created virtual disk provisioning procedure. Specifically, the virtual disk creating unit 240 creates a virtual disk having a plurality of virtual machines, which can be shared and accessed by a plurality of virtual machines, And creates a second disk that can be written. At this time, the virtual disk creating unit 240 stores data in which the location path of the second disk is recorded on the first disk. When a write operation is requested to a file stored in the first disk, the virtual disk generator 240 copies the file stored in the first disk to the second disk and performs a write operation on the file copied to the second disk do.

As a result, the virtual cluster establishing apparatus 200 merges the read-only virtual disk in which the required software is installed and the virtual disk capable of the write operation, thereby making it possible to create only the virtual disk including necessary software The storage space of the virtual disk can be efficiently used.

3 illustrates a virtual disk provisioning procedure according to a virtual disk provisioning management apparatus according to an embodiment of the present invention. For convenience of explanation, the components will be described with reference to FIG. 2 and reference numerals.

The virtual disk provisioning process receiving unit 210 receives a provisioning request for a virtual cluster having a plurality of virtual machines (S310).

Specifically, the virtual cluster provisioning process performing unit 211 included in the virtual cluster provisioning process receiving unit 210 receives the virtual cluster provisioning request included in the virtual cluster provisioning request, which merges the plurality of received virtual disks, Parsing the statement. At this time, the virtual machine of the virtual cluster must be able to be placed on a specific physical host so that the virtual cluster provisioning specification can be parsed. The virtual cluster provisioning specification is an XML-format document conforming to the OVF standard, and the parsed result is generated as an internal data structure to be used in the virtual cluster establishing apparatus 200. In addition, the virtual cluster provisioning process performing unit 211 determines whether a virtual disk of the virtual cluster existing in the parsed specification can be created. The criterion that can be determined is whether or not there is a space that can be stored based on the virtual disk size of the specified virtual cluster and whether or not provisioning is possible until the virtual disk usage time defined by the user is determined. In order to perform this process, a shared storage for storing the virtual disk must exist, and the result of the determination is whether or not the virtual disk can be provisioned.

Then, in response to the request, the virtual disk creating unit 240 creates a first disk in which software required in common for a plurality of virtual machines, which are shared by a plurality of virtual machines, is installed (S320).

Specifically, the virtual disk creation unit 240 first creates an empty first disk having the name Vdisk_01. The name and size of the generated first disk are determined based on the virtual disk provisioning procedure specified by the virtual disk provisioning procedure generation unit 230. [ The virtual disk creating unit 240 creates a file system specified by the user on the first disk, creates an empty directory having the name vdisk_01, and mounts the first disk in the form of a loopback device. If the created first disk is mounted, the virtual disk creation unit 240 duplicates or installs the virtual disk on the first disk installed with the system software specified in the virtual disk provisioning procedure. At this time, when the reusable virtual disk searching unit 220 finds a reusable merge type virtual disk in which the corresponding system software is installed, the virtual disk creating unit 240 replicates the reusable merge type virtual disk to the first disk. In the case of the merge type virtual disk, the virtual disk creation unit 240 replaces the file with the size of the virtual disk requested by the user and does not match the size of the reused virtual disk, thereby provisioning the virtual disk. This is because, in the case of the merged virtual disk, the space of the virtual disk requested by the user is created on the second disk and then merged. Here, the second disk refers to a virtual disk that is associated with software in each of a plurality of virtual machines and is writable.

On the other hand, when the system software to be installed on the first disk is not present in the reuse asset storage 300, and the virtual disk generator 240 generates the first disk on which the system software is installed, the virtual disk provisioning procedure generator 230 generates, Creates a virtual disk provisioning procedure that is meta information based on the name, version, and architecture information of the system software installed to register as an asset to be reused.

If there is application software to be additionally installed after the virtual disk creating unit 240 installs the system software on the first disk, the virtual disk creating unit 240 creates a first disk for application software whose name is Vdisk_01_app do. The virtual disk creating unit 240 creates a separate first disk without installing any application software on the first disk having the Vdisk_01 installed with the system software in order to improve the reusability of the virtual disk in which the respective software is installed. The virtual disk creation unit 240 installs the file system on the first disk, which is the second Vdisk_01_app, and mounts the empty directory with the name app01 as a loopback device. In addition, the virtual disk creating unit 240 creates an empty directory for the application software and an empty directory named vdisk_01 / app01 under the directory where the first disk having the Vdisk_01 is mounted. Then, the virtual disk creating unit 240 creates a virtual directory in which the application software installed in the vdisk_01 / app01 directory created by binding the first directory vdisk_01 / app01 and the second directory app01 to each other is actually Vdisk_01_app Allows the disk to be installed in the mounted app01 directory. The reason why the virtual disk creating unit 240 installs the application software through the bind mount is because the application software is dependent on the system software. If the virtual disk creating unit 240 installs the application software in the app01 directory in which the first disk of Vdisk_01_app is mounted, the application software dependent on the system software of the virtual machine is installed. That is, the user has requested that the application software OpenJDK7 be created in the form of a virtual disk that can run on the Linux Debian 8.0 version of the AMD64 architecture, but if it does not go through the bind mount process, OpenJDK7 is installed which can run on the Linux Debian 7.0 version of the AMD64 architecture to be. If the bind mount process is normally performed, the virtual disk creation unit 240 changes the root file system to the vdisk_01 directory in which the system software is installed, and downloads and installs the vdisk_01 / app01 directory in which the application software is created. When the application software is installed, the virtual disk provisioning procedure generator 230 generates a virtual disk provisioning procedure for the virtual disk in which the system software is installed, and the generated virtual disk provisioning procedure and the asset ID are stored in the reusable asset storage 300 . Thereafter, the virtual disk creating unit 240 unmounts the bind-mounted application software directory under the directory in which the system software is installed. Also unmount the vdisk_01 directory on which the first virtual disk with Vdisk_01 is mounted and the app01 directory on which the first disk with Vdisk_01_app is mounted. Finally, the virtual disk creating unit 240 replicates the generated first disk by the required number. System software and application software settings installed on the first disk are performed on the second disk allocated to the virtual machine.

Then, the virtual disk creating unit 240 creates a second disk that can be written in association with software in each of the plurality of virtual machines (S330).

Specifically, the virtual disk creation unit 240 creates a second disk in each of the plurality of virtual machines in association with the software installed in the first disk and writable. Here, the second disk is a virtual disk capable of storing data used by each virtual machine when a plurality of virtual machines share a virtual disk. The second disk applies system settings such as hostname and IP address to each virtual machine and provides space for storing data that is modified and created while the user is using the virtual machine. The first disk shared by the virtual machines is generally a virtual disk in which system software or application software exists. If there is no system configuration for each virtual machine on the second disk, it is recognized as a virtual machine having the same hostname and IP address do. In addition, when a plurality of virtual machines simultaneously request a shared first disk to be written, the file system created in the virtual disk is broken. Therefore, the shared first disk must be provisioned as read-only, and a second disk capable of storing the used data must be separately provided. However, since there is no need to install separate system software and application software on the second disk, a file and directory structure is required to set up system software and application software, and to store the data to be modified and generated.

Since the virtual disk creating unit 240 creates the second disk based on the system software information of the virtual machine, the system software information of the virtual machine to be created in the virtual disk provisioning procedure is required. First, the virtual disk creating unit 240 creates an empty second disk for each virtual machine, and installs the same file system as the file system of the first disk shared by the plurality of virtual machines in the created virtual disk. The virtual disk creation unit 240 mounts the generated second disk as a loopback device in an empty directory named vdisk_01 and vdisk_02, and creates directories existing in the root directory of the system software to be used by the virtual machine. For example, in the case of Linux Debian, the directory for bin, dev, home, lib, media, opt, root, sbin, srv, usr, boot, etc, lib64, mnt, proc, run, selinux, sys, And the virtual disk creation unit 240 creates an empty directory having the same name in a directory mounted on the second disk. The reason for creating a directory with the same name as the directory that exists at the top of the root filesystem of the system software is to store the data that the virtual machine will modify or write. In addition, the virtual disk creation unit 240 replicates directories and files in which all write operations that may occur during the booting of the system software and application software occur. For example, in Debian 8.0, during the boot process, under the 'log' and 'tmp' directories under 'var', the system status, file system consistency check results, error information, File deletion, and the like. As mentioned earlier, a merge virtual disk provides a read-only virtual disk on which system software and application software are installed, so the virtual machine can not perform write operations at boot time. Therefore, the virtual disk creation unit 240 removes errors in the booting process by moving the directory and the file in which the write operation is performed to the second disk among the merged virtual disks provided for each virtual machine. Here, the merge mounting is a technique in which all the software components are merged into one or more files that are not integrated in a single file or a directory existing in the file system of the physical host. The virtual disk creating unit 240 merges all the files and directories existing in the lower directory and the upper directory through the merge mounting, so that the virtual directory is displayed as a single logical file structure. If the virtual disk creation unit 240 performs merge mounting with the directory of the first disk where the actual shared system software is installed and the directory of the same name created on the second disk with the lower directory and the upper directory respectively, Even if the file does not exist, the directories of the first disk and the second disk are merged and exposed in the virtual machine. That is, the virtual machine is logically exposed as one logical file structure, but all the data that the user writes is created under the directory specified by upperdir, which is stored in the directory existing on the second disk. Therefore, if the virtual disk creation unit 240 designates the first disk shared by the plurality of virtual machines as lowerdir, designates the second disk as upperdir, and performs the merge mounting, all the data generated by the virtual machine becomes upperdir It is possible to increase the reusability of the shared virtual disk stored in the directory of the merged second disk. In addition, the virtual disk creating unit 240 stores the system settings of the respective virtual machines on the second disk and merges them, so that when the virtual machine is operated, different hostnames and IP addresses are applied to reuse the shared first disk Can be maximized. When the virtual disk creating unit 240 creates the second disk, the system settings are created and stored in different directories and files according to the system software. In the case of Linux Debian, the virtual disk creation unit 240 creates a hosts file containing the hostname and IP address of virtual machines such as hostname under the etc directory. In addition, the virtual disk creating unit 240 creates an IP address of each virtual machine in the network directory under the etc directory with the file name interfaces. If there is a first disk in which application software is installed among the shared first disks, the virtual disk creating unit 240 stores the application software setting information in the second disk as well as the system software settings. In the case of Hadoop 2.6.0, the virtual disk creating unit 240 creates the hadoop / conf directory under the opt directory by creating and storing a directory on the second disk where application software settings should be stored, , core-site.xml, hdfs-site.xml, mapred-site.xml, master, slaves, and so on. That is, files associated with software installed on the first disk are stored in the second disk. If all the configuration files for the system software and the application software are generated, the virtual disk creation unit 240 finally creates the work directory. In the merge mounting, the work directory is utilized as a directory for temporarily storing data used in the upper directory during the merge, so the virtual disk generator 240 must create the work directory on the second disk. The virtual disk creating unit 240 dismounts the second disk of the created virtual machine and finishes the job if all configuration file creation jobs are completed.

In addition, when receiving a back-up request of the virtual machine, the virtual disk creating unit 240 stores a file that can be written on the second disk. In addition, the virtual disk creating unit 240 stores data in which the location path of the second disk is recorded on the first disk. At this time, the first disk is set so that only the reading operation is possible. The write-enabled file includes files copied from the first read-only disk.

Subsequently, the virtual disk creating unit 240 mounts the first disk and the second disk by merging (S340).

That is, the virtual disk creating unit 240 merges and mounts the first disk and the second disk so that they appear as a single tree. At this time, if the same file or folder exists in the first disk and the second disk, the virtual disk creation unit 240 allows the same file or folder of the second disk to be accessed. If there are a plurality of first disks having a plurality of versions of software installed therein, the virtual disk creating unit 240 merges and mounts the plurality of first disks and the second disks. That is, the virtual disk creating unit 240 merges and mounts the plurality of second disks so that different files can be accessed in each of the plurality of versions of the software. At this time, the plurality of first disks are created by installing the software of each of the plurality of versions by the virtual disk creating unit 240.

According to some embodiments, when a write operation is requested to a file stored in the first disk, the virtual disk generator 240 copies the file stored in the first disk to the second disk, Perform a write operation on the file.

Accordingly, the virtual cluster establishing apparatus 200 can separately create a writable virtual disk, shorten the provisioning process of the virtual disk by sharing the already created virtual disk without generating the virtual disk in which the software to be used is created .

FIG. 4 illustrates a virtual disk sharing method of a virtual machine using a merged virtual disk according to an embodiment of the present invention.

4, the virtual cluster 410 includes a plurality of virtual machines 411, a second virtual machine 412, a third virtual machine 413, and a fourth virtual machine 414 . The first disk 421 is a virtual disk containing system software and includes system software of Debian 8.0. Also, the first disk 422 is a virtual disk containing application software, including OpenJDK and Hbase 1.1.1. At this time, the first disks 421 and 422 can be read only, and can be shared among a plurality of other virtual machines. Each of the second disks 431, 432, 433 and 434 is connected to the first disk 412 in the first virtual machine 411, the second virtual machine 412, the third virtual machine 413 and the fourth virtual machine 414, Which are associated with the system software and the application software included in the virtual disks 421 and 422.

4, the first virtual machine 411 shares a first disk 421, 422 including Debian 8.0, OpenJDK and Hbase 1.1.1, and data on Debian 8.0, OpenJDK and Hbase 1.1.1 And a second disk 431 capable of performing write operations when it is created and modified. The second virtual machine 412, the third virtual machine 413 and the fourth virtual machine 414 likewise share a first disk 421, 422 including Debian 8.0, OpenJDK and Hbase 1.1.1, and Debian 8.0 , OpenJDK, and Hbase 1.1.1, the second disk 432 allocated to the second virtual machine 412 capable of performing the write operation, the second disk 432 allocated to the third virtual machine 413, A third disk 433 allocated to the fourth virtual machine 414, and a second disk 434 allocated to the fourth virtual machine 414, respectively. Thus, the first virtual machine 411, the second virtual machine 412, the third virtual machine 413 and the fourth virtual machine 414 are connected to the Debian 8.0, OpenJDK, and OpenJDK included in the first disk 421, Data for Debian 8.0, OpenJDK, and Hbase 1.1.1 are shared via the second disks 431, 432, 433, and 434 corresponding to the respective virtual machines 411, 412, 413, and 414, Can be created and modified.

In some embodiments, the first virtual machine 411, the second virtual machine 412, the third virtual machine 413, and the fourth virtual machine 414 are connected to the first disk 421, Alternatively, application software or system software of a different version from the system software may be used through a write operation on the second disk 431, 432, 433, 434. For example, the first virtual machine 411 may use Hbase1.1.2, an upgraded version of Hbase1.1.1, on the second disk 421, which is write enabled. Specifically, the virtual cluster establishing apparatus 200 copies the configuration file changed to be upgraded to Hbase1.1.2 among the configuration files of Hbase1.1.1 stored in the first disk 422 to the second disk 421, The second disk 431 including the changed configuration file for upgrading from Hbase1.1.1 to Hbase1.1.2 and the first disk 421 including the configuration file of Hbase1.1.1 identical to the configuration file of Hbase1.1.2 are merged and mounted do. That is, even though the first virtual machine 411, the second virtual machine 412, the third virtual machine 413, and the fourth virtual machine 414 share the same first disk 421 and 422, May include software versions different from software installed on the first disks 421 and 422 through write operations on the virtual disks 431, 432, 433, and 434.

Accordingly, the virtual cluster establishing apparatus 200 can efficiently use the storage space of the virtual disk by providing software of a different version from the software included in the virtual disk that can be shared without a separate provisioning through a writable virtual disk , And the virtual disk provisioning step can be reduced.

5 illustrates a virtual disk file structure of a virtual machine in which a plurality of directories are merged through merge mounting according to another embodiment of the present invention.

Referring to FIG. 5, two or more directories are merged into a single file system in a merged mounting directory, that is, a mounting point. The directory to be merged may be included in the first disk and the second disk. All directories of the first disk, that is, LowerDir is read-only, and the directory of the second disk, that is, UpperDir is a read- Write). If there is a file or directory of the same name among the merged directories, the directory of the second disk, that is, the file existing in Upper Dir, has the highest read priority. Also, the directory of the first disk, i.e., Lower Dir, is configured to be read-only. And all write operations are applied to the directory of the second disk. Therefore, although File1.txt and File3.txt exist in directory 3 to be merged with directory 3 actually merged, directory 3 to be merged and directory 2 to be merged are all merge-mounted to a read-only directory. I can not. Accordingly, when the user performs a write operation on the file in the merge-mounted directory, the virtual cluster establishing apparatus 200 deletes the file in the directory 2 to be merged with the directory 3 to be merged from the second disk The directory 1 to be merged reflects the post-cloning write operation. As a result, directory 1 to be merged stores File1.txt and File3.txt.

Accordingly, the virtual cluster establishing apparatus 200 permits the writing operation of the software included in the virtual disk to be possible by merge-mounting the first disk, which can be read only, and the second disk, which is writable.

FIG. 6 illustrates a file system hierarchical structure of a merged virtual disk when a virtual machine uses various application software according to another embodiment of the present invention.

Referring to FIG. 6, the file system hierarchy 600 is a hierarchical structure of a merged file system when one or more application software references different libraries of the same name. For example, application software 'A' and 'B' use the same library 'liba'. When the application software 'A' uses the library version '1.9' and the application software 'B' uses the library version '2.1', when the merge virtual disk is created, 1.9 'version is installed, and' 2.1 'version library is installed in the virtual disk where application software' B 'is installed. Due to software dependency problems, there is usually a standardized rule naming software and libraries by name, major version, and minor version. Therefore, the library name required by the application software 'A' is 'liba.1.9', and the application software 'B' has the library 'liba.2.1'. Since the virtual cluster establishing apparatus 200 merges the file systems installed in the respective merge-type virtual disks when the virtual machine is driven, the user can not use the 'liba.1.9' library file existing in the virtual disk in which the application software 'A' The 'liba.2.1' library file of the virtual disk where application software 'B' exists is displayed at the same time. Therefore, the virtual cluster establishing apparatus 200 does not cause a software conflict problem even if a merge type virtual disk for each software element is created.

Figures 7 (a) through 7 (d) illustrate the effect of virtual disk provisioning for building a virtual cluster in accordance with another embodiment of the present invention.

Referring to FIG. 7A, there is shown a graph 710 of a single virtual disk creation time measurement result per non-reuse and reuse-based virtual disk type. Here, the re-use means that when a new virtual disk is created by equally including the software installed in a previously created virtual disk, a new virtual disk is created by duplicating the previously created virtual disk.

Referring to FIG. 7A, the size of the virtual disk used for checking the effect of virtual disk provisioning is 3 GB, the system software is Debian 7.0, the application software is OpenJDK 7.0, Hadoop 2.6.0, and HBase 1.1.1 was used. As a result of checking the effect, the non-reused integrated virtual disk 711 on the virtual machine allocated with 4 VCPUs and 4 GB of memory shows the generation time of 1273.85 seconds, and the non-reused combined virtual disk 7812) shows the generation time of 1217.69 seconds . The difference in the generation time of the non-reused integrated type and the merged type virtual disks 711 and 712 can be regarded as a difference that can occur because the time for installing the system and application software uses the external storage where each software package exists. The difference in the generation time of the non-reuse integrated type and the merged type virtual disks 711 and 712 can be regarded as a slight difference in installation time depending on the network environment of the external storage where the software package exists. Therefore, it can be seen that the generation times of the non-reused integrated type and the merged type virtual disks 711 and 712 are similar regardless of the virtual disk type.

When the virtual disk on which the system software is installed is reused, the total generation time of the integrated and merged virtual disks 713 and 714 represents 629.16 seconds and 608.96 seconds, respectively. If only system software is reused, it is necessary to install application software. Similar to the generation of the non-reusable virtual disks 711 and 712, the difference in the generation time of the system software reuse integrated type and the merged type virtual disks 713 and 714 is that the package of the application software to be installed is stored in the external storage, . As a result, even if the system software is reused, if the application software to be additionally installed exists, the generation times of the system software reuse integrated type and the merged type virtual disks 713 and 714 are similar. When all the virtual disks having the system and the application software are reused, the generation times of the integrated type and the merged type virtual disks 715 and 716 are 356.17 seconds and 233.87 seconds, respectively. Reuse of System and Application Software Compared to the integrated virtual disk 715, the reuse of system and application software is shortened because the generation time of the merged virtual disk 716 is shortened because of the difference in the method of reusable virtual disk replication. System and Application Software Reuse The integrated virtual disk 715 replicates the contents of a reusable virtual disk after creating a blank disk image corresponding to the size of the virtual disk requested by the user. If the size of the reusable virtual disk is 2.2 GB, the user can not provide the requested virtual disk size of 3 GB. In contrast, the system and application software reuse combined virtual disk 716 can create an upper disk and merge it, so that the virtual disk in which the reusable software is installed can be copied and used as it is. Here, the Upper disk is a disk that stores settings for software installed in the merged virtual disk and stores data to be stored due to a write operation. If the size of the reusable virtual disk is 2.2 GB, it is necessary to provide 0.8 GB of the upper disk. Duplicating the contents of a reusable virtual disk consumes a lot of replication time compared to the time of duplicating a single virtual disk file because it repeatedly performs all the file-by-file copy operations. Therefore, when reusing all the software components, the time for generating the concurrent disk is shortened as compared with the integrated type.

Referring to FIG. 7B, a graph 720 of the generation time result of each virtual disk type as the number of virtual machines included in one virtual cluster increases. Will be described with reference to Fig. 7 (a) for convenience of explanation.

Referring to FIG. 7 (b), the reuse-based integrated virtual disk creation time in the virtual machine allocated with four VCPUs and 4 GB of memory shows an exponential increase in the generation time in the number of virtual machines . Especially, it can be seen that the generation time increase rate slightly increases from the point when the number of virtual machines is changed from 8 (721) to 16 (722). The reuse-based integrated virtual disk creation time is generated because the disk created by the number of virtual machines must be duplicated. That is, since the virtual machines existing in the same virtual cluster do not share the created virtual disk, the integrated system must duplicate the disk in which all necessary system software and application software are installed by the number of virtual machines. In the case of replication, the same result can be obtained because it is necessary to replicate the replica by the size of the virtual disk requested by the user.

Referring to FIG. 7C, a graph 730 of a merged virtual disk creation time of a virtual machine of 32 virtual servers included in the virtual cluster as the maximum number of shared virtual machines per virtual disk increases is included.

Referring to FIG. 7C, a graph 730 of a merged virtual disk creation time reduction rate of a virtual machine of 32 virtual servers included in the virtual cluster according to an increase in the maximum number of shared virtual machines per virtual disk is represented. Also, it is expressed based on the generation time reduction rate when the maximum number of shared virtual machines per virtual disk is one. As a result, the reuse-based concurrent disk creation time in a virtual machine allocated 4 VCPUs and 4 GB of memory is based on a total of 32 virtual machines (736), and the maximum number of shared virtual machines per virtual disk is 1 to 4 (731, 732, 733). However, if the maximum number of shared virtual machines is four or more (733, 734, 735, 736), the reduction ratio of generation time is reduced to 11% or less. That is, it can be seen that the maximum number of virtual machines that can be shared per virtual disk is four (733) when the method of generating a merged virtual disk of the present invention is used. This means that even if the number of virtual machines included in the virtual cluster increases, the maximum generation time savings can be obtained when a maximum of four virtual machines (731, 732, and 733) share one virtual disk.

Referring to (d) of FIG. 7, a graph 740 of the shared storage space used by the virtual disk type according to the increase of the number of virtual machines existing in the virtual cluster is shown. The integrated virtual disk 741 represents a linear shared storage usage size in proportion to an increase in the number of virtual machines existing in the virtual cluster. This can be interpreted as a result because virtual disks are created in proportion to the number of virtual machines existing in each virtual cluster. In addition, we can conclude that the virtual machines in the virtual cluster use the shared storage linearly according to the number of virtual machines because they do not share the virtual disk with the homogeneous software installed. The merged virtual disks 742, 743, and 744 represent different shared storage usage spaces according to the maximum number of virtual machines to be shared per virtual disk. First, if one shared virtual machine (741) is shared per merged virtual disk, it shows the same storage usage space as the integrated virtual disk. This is because the virtual machines of the virtual cluster are all the same as those provided with individual virtual disks. However, when the number of maximum shared virtual machines increases from 2 (742), 4 (743), and 8 (744), the decrease rate of storage space usage is 36.88%, 55.32% and 64.54%, respectively. Similar to the generation time reduction rate, when the maximum number of shared virtual machines per merged virtual disk is 4 or more (743, 744), the reduction rate of the shared storage space is lowered. As a result, the generation time of the merged virtual disks 742, 743, and 744 is shorter than that of the integrated virtual disk 741 even when the number of shared virtual machines increases. can confirm. It can also be seen that the generation time of the integrated virtual disk 741 and the combined virtual disks 742, 743 and 744 is proportional to the increase in the number of virtual machines existing in the virtual cluster. The used space of the shared storage also increases in proportion to the number of virtual machines shared by both the integrated virtual disk 741 and the merged virtual disks 742, 743, and 744. Especially, when the number of maximum shared virtual machines among the merged virtual disks is one (742), it is confirmed that shared storage having the same size as the integrated type is used. Of course, in terms of the total virtual disk creation time, it is possible to create a disk faster than the integrated virtual disk 741. However, considering the use space of the shared storage, the virtual machine that has allocated 4 VCPUs and 4GB of memory requires a minimum shared virtual machine It can be concluded that it is reasonable to perform virtual disk provisioning after setting two or more (742, 743, 744).

In this specification, each block or each step may represent a part of a module, segment or code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative embodiments, the functions mentioned in the blocks or steps may occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially concurrently, or the blocks or steps may sometimes be performed in reverse order according to the corresponding function.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, which is capable of reading information from, and writing information to, the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

Although the embodiments of the present invention have been described in detail with reference to the accompanying drawings, it is to be understood that the present invention is not limited to those embodiments and various changes and modifications may be made without departing from the scope of the present invention. . Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. Therefore, it should be understood that the above-described embodiments are illustrative in all aspects and not restrictive. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

110 virtual machines
120, 140 virtual disks
130 Software
131 System Software
132 First application software
133 Second application software
200 Virtual Cluster Device
210 Virtual Cluster Provisioning Process Receiver
211 Virtual Cluster Provisioning Process Performer
212 Virtual Cluster Provisioning Initiation Section
213 Virtual Cluster Provisioning Process Observation
220 Reusable Virtual Disk Search Unit
230 Virtual Disk Provisioning Procedure Generator
240 virtual disk creation unit
300 reusable asset repository
410 virtual clusters
411 First Virtual Machine
412 Second Virtual Machine
413 Third Virtual Machine
414 Fourth Virtual Machine
421, 422 first disk
431, 432, 433, 434 The second disk
600 file system hierarchy
710 Graph of single virtual disk creation time measurement by type of non-reusable and reusable virtual disk
711 Non-Reusable Integrated Virtual Disks
712 Non-Reusable Mergeable Virtual Disk
713 Reusing System Software Integrated Virtual Disk
714 Reusing System Software Mergeable Virtual Disk
715 Reusing system and application software Integrated virtual disk
716 System and Application Software Reuse Mergeable Virtual Disk
720 Graph of the result of generation time for each type of virtual disk as the number of virtual machines included in the cluster subgroup increases
721 Number of virtual machines 8
722 Number of virtual machines 16
730 Graph of reduction rate of creation time of merged virtual disks in virtual machines with 32 servers included in the virtual cluster subgroup as the maximum number of shared virtual machines per virtual disk increases
731 Maximum number of shared virtual machines per virtual disk One
732 Maximum number of shared virtual machines per virtual disk 2
733 Maximum number of shared virtual machines per virtual disk 4
734 Maximum number of shared virtual machines per virtual disk 8
735 Maximum number of shared virtual machines per virtual disk 16
736 Maximum number of shared virtual machines per virtual disk 32
740 Graph of the shared storage space used by virtual disk type as the number of virtual cluster subgroups increases
741 One virtual machine shared per integrated virtual disk and one virtual shared disk
742 two shared virtual machines per integrated virtual disk and a merged virtual disk
743 Consolidated virtual disks and 4 shared virtual machines per merged virtual disk
744 Consolidated virtual disks and 8 shared virtual machines per merged virtual disk

Claims (18)

A method of constructing a virtual cluster having a plurality of virtual machines,
Receiving a provisioning request for the virtual cluster having the plurality of virtual machines;
Creating a first disk in which software required in common to the plurality of virtual machines is installed, the first disk being shared and accessible by the plurality of virtual machines in response to a provisioning request for the virtual cluster;
Creating a second disk in each of the plurality of virtual machines, the second disk being writable in association with the software; And
And merging the first disk and the second disk to mount a virtual cluster by merge mounting of a readable and writable virtual disk. The method according to claim 1,
Further comprising the step of storing data in which the location path of the second disk is recorded in the first disk,
Wherein the first disk is set to be readable only, and a virtual cluster is constructed by merge mounting of a readable and writable virtual disk. 3. The method of claim 2,
Receiving a back-up request of the virtual machine; And
Further comprising the step of storing a file capable of being written in the second disk,
Wherein the write-enabled file includes a file copied from the first disk, which was conventionally read-only, by merge mounting of a readable and writable virtual disk. The method according to claim 1,
And storing the files associated with the software on the second disk, wherein the virtual disks are readable and writable. The method according to claim 1,
Wherein the step of merging and mounting the first disk and the second disk comprises:
And creating the merged first disk and the second disk so that they appear as a single tree. The method according to claim 1,
Wherein the step of merging and mounting the first disk and the second disk comprises:
Constructing a virtual cluster through merge mounting of a readable and writable virtual disk configured to access the same file or folder of the second disk when the same file or folder exists in the first disk and the second disk Way. The method according to claim 1,
The software resides in a plurality of versions,
Wherein the step of creating the first disk comprises:
Generating a plurality of first discs in which software of each of the plurality of versions is installed,
Wherein the mounting comprises:
And merging and mounting the plurality of first disks and the second disks, wherein the plurality of first disks and the second disks are mounted by merging. 8. The method of claim 7,
Wherein the mounting comprises:
And merging and mounting the plurality of first disks so that different files are accessible in each of a plurality of versions of the software. The method according to claim 1,
When a write operation is requested to a file stored in the first disk,
Copying the file stored in the first disk to the second disk; And
Further comprising performing the write operation on a file copied to the second disk, wherein the virtual cluster is mounted by merge mounting of a readable and writable virtual disk. An apparatus for constructing a virtual cluster having a plurality of virtual machines,
A virtual disk provisioning process receiving unit that receives a provisioning request for the virtual cluster having the plurality of virtual machines; And
Generating a first disk, in which software required in common to the plurality of virtual machines is installed, which is shared and accessible by the plurality of virtual machines in response to a provisioning request for the virtual cluster,
Creating a second disk in each of the plurality of virtual machines, the second disk being writable in association with the software,
And a virtual disk creating unit that mounts the first disk and the second disk by merging the virtual disk and the virtual disk. 11. The method of claim 10,
Wherein the virtual disk creation unit comprises:
Storing data in which the position path of the second disk is recorded in the first disk,
Wherein the first disk is configured to allow only a read operation, and a read / write virtual disk is mounted by merge mounting. 12. The method of claim 11,
Wherein the virtual disk provisioning process receiving unit comprises:
Receiving a backup request of the virtual machine,
Wherein the virtual disk creation unit comprises:
Storing a file capable of being written in the second disk,
Wherein the file capable of performing the write operation includes a file copied from the first disk, which was conventionally read-only, by merge mounting of a readable and writable virtual disk. 11. The method of claim 10,
And a file associated with the software is stored in the second disk. 11. The method of claim 10,
Wherein the virtual disk creation unit comprises:
Wherein the first disk and the second disk are merged into a single tree so that the first disk and the second disk are merged into a single tree. 11. The method of claim 10,
Wherein the virtual disk creation unit comprises:
If the same file or folder exists in the first disk and the second disk,
Wherein the virtual disk is configured such that the same file or folder of the second disk is accessed. 11. The method of claim 10,
The software resides in a plurality of versions,
Wherein the virtual disk creation unit comprises:
Generating a plurality of first discs having software of each of the plurality of versions,
And a plurality of the first disks and the second disks are mounted by being merged, wherein the virtual clusters are mounted by merge mounting of a readable and writable virtual disk. 17. The method of claim 16,
Wherein the virtual disk creation unit comprises:
And a plurality of first disks are merged and mounted so that different files can be accessed in each of a plurality of versions of the software. 11. The method of claim 10,
When a write operation is requested to a file stored in the first disk,
Wherein the virtual disk creation unit comprises:
Copying the file stored in the first disk to the second disk,
And performing a write operation on a file copied to the second disk, wherein the virtual cluster is mounted by merge mounting of a readable and writable virtual disk.

Images