WO2018088629A1 - Method and apparatus for constructing virtual cluster by union-mounting readable and writable virtual disks - Google Patents

Abstract

The present invention relates to a method and apparatus for constructing a virtual cluster by union-mounting readable and writable virtual disks. A method for constructing a virtual cluster having a plurality of virtual machines according to an embodiment of the present invention comprises the steps of: receiving a provisioning request for a virtual cluster having a plurality of virtual machines; in response to the provisioning request for the virtual cluster, generating a first disk in which software commonly required for the plurality of virtual machines is installed, the first disk being shared and accessible by the plurality of virtual machines; generating, in each of the plurality of virtual machines, a second disk in which a write operation can be performed in association with the software; and union-mounting the first disk and the second disk. Accordingly, the present invention can provide a method and apparatus for constructing a virtual cluster by union-mounting readable and writable virtual disks, wherein a separate united virtual disk in which a write operation can be performed is provided and union-mounted with a read-only virtual disk, so that each of the virtual machines can perform a write operation on the shared virtual disk.

Description

Method and device for building virtual cluster through merge mounting of read and write virtual disks

The present invention relates to a method and apparatus for constructing a virtual cluster through merge mounting of a read and write virtual disk, and more specifically, to a virtual cluster by merging each virtual disk in a read and write form including different software. The present invention relates to a method and apparatus for building a virtual cluster through merge mounting of a read and write virtual disk capable of building a virtual disk.

As network and storage technologies have evolved, platform technologies, ie, virtualization technologies, have been actively studied to apply analytical processing technology of large data stored in sharable storage. In particular, in order to effectively analyze a large amount of data, a technique for processing distributed and stored data in parallel is becoming important. However, in order to process large data distributed in parallel, a virtual cluster technology that clusters and utilizes one or more processing computing nodes is essential.

A virtual cluster is a collection of virtual machines with software that performs specific functions and is networked. To create a virtual cluster, you need to provision virtual computing resources. Virtual disk provisioning includes virtual cluster batch provisioning and virtual cluster disk provisioning. Virtual cluster placement provisioning refers to a process for creating and creating a virtual cluster in a virtualized physical system based on resource information of virtual machines included in a virtual cluster to be created. Virtual cluster disk provisioning refers to a process of creating a virtual disk for creating a virtual machine of a virtual cluster. Here, the process of installing and configuring the software requested by the user, that is, the system software and the application software, on each of the created virtual disks directly affects the overall virtual disk provisioning time.

[Related Technical Documents]

Method and system for providing a virtual machine, and a recording medium having recorded thereon a program (public patent 10-2014-0055481)

In order for one or more virtual machines to share a virtual disk, the shared virtual disk may be provided to the virtual machine as read-only. If you do not provide a virtual disk as read-only, the file system of the shared virtual disk may change when each virtual machine writes.

Therefore, the inventors of the present invention provide a separate merged virtual disk capable of performing a write operation and merge mounting with a read-only virtual disk, so that each virtual machine can share a virtual disk to drive a program. Invented a method and apparatus for construction.

Another problem to be solved by the present invention is to efficiently use the storage space of the virtual disk by merging and mounting the virtual disk capable of writing to the shared virtual disk by sharing the already created read-only virtual disk This will reduce the time it takes to provision.

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

In order to solve the above problems, a virtual cluster construction method through merging mounting of a read and write virtual disk according to an embodiment of the present invention is a step of receiving a provisioning request for a virtual cluster having a plurality of virtual machines Creating a first disk having software commonly required for the plurality of virtual machines, the plurality of virtual machines being shared and accessible in response to a provisioning request for the virtual cluster, associated with the software in each of the plurality of virtual machines Generating a second disk capable of writing and merging and mounting the first disk and the second disk.

According to another feature of the invention, the virtual cluster construction method through the merge mounting of the read and write virtual disk further comprises the step of storing data in which the location path of the second disk is recorded on the first disk, The disk can be set to allow only read operations.

According to still another aspect of the present invention, a virtual cluster construction method through merge mounting of a read and write virtual disk may include receiving a back-up request of a virtual machine and a write operation stored on a second disk. The method may further include storing a file, wherein the file capable of writing may include a file copied from the first disk, which was conventionally read-only.

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

According to another feature of the present invention, the merging and mounting of the first disk and the second disk may include generating the merged first disk and the second disk to appear as a tree.

According to another feature of the invention, the step of merging and mounting the first disk and the second disk, if the same file or folder exists on the first disk and the second disk, the same file or folder on the second disk Can be configured to be accessed.

According to another feature of the invention, the software exists in a plurality of versions, and the step of creating the first disk comprises the step of creating a plurality of first disks on which the respective software of the plurality of versions is installed, The step of merging may be a step of merging and mounting the plurality of first and second disks.

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

According to another feature of the present invention, a virtual cluster construction method through merge mounting of a read and write virtual disk, when a write operation is requested for a file stored on the first disk, the file stored on the first disk is second; The method may further include copying to a disk and performing a write operation on the file copied to the second disk.

In order to solve the above problems, a virtual cluster building apparatus through merge mounting of a read and write virtual disk according to an embodiment of the present invention is a device for building a virtual cluster having a plurality of virtual machines, The virtual disk provisioning process receiving unit that receives a provisioning request for a virtual cluster having a virtual machine and software commonly installed in a plurality of virtual machines that are shared and accessible by a plurality of virtual machines in response to the provisioning request for the virtual cluster are installed. And a virtual disk generating unit for generating a first disk, creating a second disk capable of writing in association with software in each of the plurality of virtual machines, and merging and mounting the first disk and the second disk.

According to another feature of the present invention, the virtual disk generating unit may store data in which the location path of the second disk is recorded on the first disk, and the first disk may be configured to only read.

According to another feature of the present invention, the virtual disk provisioning process receiving unit receives a backup request of the virtual machine, the virtual disk generating unit stores a file capable of write operations stored in the second disk, It may include a file copied from the first disk, which was conventionally read-only.

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

According to another feature of the present invention, the virtual disk generating unit may generate the merged first disk and the second disk to appear as a tree.

According to another feature of the present invention, the virtual disk generating unit may be configured to access the same file or folder of the second disk when the same file or folder exists on the first disk and the second disk.

According to another feature of the invention, the software is present in a plurality of versions, the virtual disk generating unit generates a plurality of first disks, each of which is installed a plurality of versions of the software, a plurality of first disk and the second disk Can be mounted by merging

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

According to another feature of the present invention, when a write operation is requested for a file stored in a first disk, the virtual disk generating unit copies the file stored in the first disk to the second disk, and the file copied to the second disk. The write operation can be performed on.

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

The present invention provides a virtual cluster capable of performing a write operation on a shared virtual disk by providing a separate merged virtual disk capable of performing a write operation in a virtual cluster and merging mounting with a read-only virtual disk. There is an effect that can provide a construction method and apparatus.

The present invention can efficiently use the storage space of the virtual disk and reduce the time required for provisioning the virtual disk by sharing a read-only virtual disk already created and merging it with a virtual disk capable of writing to the shared virtual disk. It can be effective.

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

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

2 is an exemplary block diagram illustrating a virtual cluster building apparatus through merge mounting of a read and write virtual disk according to an embodiment of the present invention.

3 illustrates a virtual cluster construction procedure according to a virtual cluster construction method through merge mounting of a read and write virtual disk according to an embodiment of the present invention.

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

FIG. 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 hierarchy of merged virtual disks when the virtual machine uses various application software according to another embodiment of the present invention.

7 (a) to 7 (d) illustrate the effects of virtual disk provisioning for building a virtual cluster according to another embodiment of the present invention.

Advantages and features of the present invention and methods for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various forms, and only the present embodiments are intended to complete the disclosure of the present invention, and the general knowledge in the art to which the present invention pertains. It is provided to fully convey the scope of the invention to those skilled in the art, and the present invention is defined only by the scope of the claims.

Shapes, sizes, ratios, angles, numbers, and the like disclosed in the drawings for describing the embodiments of the present invention are exemplary, and the present invention is not limited to the illustrated items. In addition, in describing the present invention, if it is determined that the detailed description of the related known technology may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. When 'comprises', 'haves', 'consists of' and the like mentioned in the present specification are used, other parts may be added unless 'only' is used. In case of singular reference, the plural number includes the plural unless specifically stated otherwise.

In interpreting a component, it is interpreted to include an 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 only used to distinguish one component from another. Therefore, the first component mentioned below may be a second component within the technical spirit of the present invention.

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

Each of the features of the various embodiments of the present invention may be combined or combined with each other in part or in whole, various technically interlocking and driving as can be understood by those skilled in the art, each of the embodiments may be implemented independently of each other It may be possible to carry out together in an association.

Hereinafter, the terms used in the present specification are defined.

As used herein, “provisioning” refers to a procedure of allocating, deploying, and distributing resources according to a user's request. Here, the resource may mean a memory of the server, a CPU, or the like. Specifically, provisioning refers to a procedure of creating a virtual disk in which software is installed in 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 run.

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

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

Referring to FIG. 1A, the virtual disk 120 in which the 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. Unlike a general hard disk, 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. Therefore, the virtual disk 120 configures a file system necessary for each virtual machine 110 in the generated file or logical volume and is provided to the virtual machine 110. In addition, the virtual disk 120 includes application software such as desired system software 131, first application software 132, and second application software 133 and a version of system software 131 that is different from the operating system of the physical machine. Installed, the virtual disk 120 may be provided to the virtual machine 110.

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

Referring to FIG. 1B, the virtual cluster building apparatus may generate a virtual disk 140 including the same software by duplicating the virtual disk 120 previously generated.

Referring to FIG. 1 (b), the virtual cluster building apparatus includes Debian 8.0, the system software 131, Open JDK 7.0, and the first application software 132, according to the virtual disk creation procedure of FIG. 1 (b). 2 The virtual disk 120 is created by copying the virtual disk 120 including the software 130 including Hadoop 2.6.0, which is the application software 133, as it is. Thus, the virtual disk 140 also includes Debian 8.0, Open JDK 7.0 as the first application software 132 and Hadoop 2.6.0 as the second application software 133. Virtual disk provisioning through cloning is faster than virtual disk creation through installation. Specifically, virtual disk creation through installation installs the software that is actually required for the virtual disk. On the other hand, the virtual disk creation through cloning is only time consuming to duplicate the software installed in the pre-created virtual disk, and thus can be created more quickly than the virtual disk creation through installation. In addition, virtual disk creation by cloning does not perform a setting step for software in virtual disk creation by cloning by replicating the virtual disk in the state where the software installed in the virtual disk is set. It can be created quickly. Therefore, the virtual cluster building apparatus stores the assets necessary for the replication of the virtual disk in the reuse asset storage, and creates the virtual disk faster based on the stored assets.

Accordingly, the virtual cluster building device generates a virtual disk on which software is installed according to a user's request, and builds a virtual cluster including a plurality of virtual machines on which the generated virtual disk is installed.

2 is an exemplary block diagram illustrating a virtual cluster building apparatus through merge mounting of a read and write virtual disk according to an embodiment of the present invention.

2, the virtual cluster building apparatus 200 includes a virtual cluster provisioning process receiving unit 210, a reused virtual disk search unit 220, a virtual cluster provisioning process performing unit 211, and a virtual cluster provisioning initiation unit 212. , A virtual cluster provisioning process observer 213, a virtual disk provisioning procedure generator 230, and a virtual disk generator 240.

Referring to FIG. 2, the virtual cluster provisioning process receiving unit 210 receives a provisioning request for a virtual cluster using an XML Remote Procedure Call (RPC). The virtual cluster may be a collection of a plurality of different virtual machines. Here, the virtual machine may include a virtual disk on which software is installed. In this case, the received provisioning request is a provisioning request for building a virtual cluster by merging virtual disks capable of read and write operations. In addition, the virtual cluster provisioning process receiver 210 may determine a virtual cluster provisioning request through the merged virtual disk when two or more virtual machines among the received provisioning requests include the same software. The virtual cluster provisioning process receiving unit 210 runs the XML RPC server and transmits 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 a software requirement installed in the virtual machines of the virtual cluster requested by the user. The virtual cluster provisioning process execution unit 211 parses the received virtual cluster provisioning request. In addition, the virtual cluster provisioning process execution unit 211 stores the parsed work object in an internal buffer to manage the progress state of the virtual cluster provisioning job. All virtual cluster provisioning processes of the present invention are performed by calling a subcomponent by the virtual cluster provisioning process execution unit 211. Here, the subcomponent is a virtual cluster building apparatus 200 such as a reused virtual disk searching unit 220 which is a component of the virtual cluster building apparatus 200, a virtual disk provisioning procedure generating unit 230, and a virtual disk generating unit 240. ) Means all modules. Each subcomponent receives, processes, and returns a task to be performed by the virtual cluster provisioning process performing unit 211 in a task unit. In addition, each subcomponent has a task execution unit that calls processing logic for each step that should be performed based on the status information of the task. The virtual cluster provisioning initiation unit 212 is a component for driving and terminating subcomponents present in the virtual cluster building apparatus 200. The subcomponents of the virtual cluster building apparatus 200 are operated and managed by the virtual cluster provisioning initiator 212. The virtual cluster provisioning process observer 213 periodically monitors the progress of the work managed by the virtual cluster provisioning process performer 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 may include the number of virtual machines in the virtual cluster desired by the user, a specification of virtual resources such as VCPU, memory, and virtual disk space that the virtual machines will have, system and application software and configuration information of the virtual machine, and the like. You will receive a request to create a virtual cluster provisioning, including time and space constraints. That is, the external system may transmit a virtual cluster provisioning generation request to the virtual cluster provisioning process receiver 210.

The reuse virtual disk search unit 220 searches a virtual disk stored in the reuse asset storage 300 to search whether the virtual disk to be created is reusable in response to a provisioning request for the virtual cluster. In detail, the reuse virtual disk search unit 220 searches for a merged virtual disk that can be reused in the reuse asset storage 300. Here, the merged virtual disk refers to a virtual disk that can be merged with a plurality of virtual disks each having different software installed thereon. The reuse asset store 300 stores the outputs of all the software generated in the virtual disk provisioning management apparatus 200. Deliverables can be stored in a virtual disk provisioning request received from an external system, a feature model of a virtual cluster, a virtual cluster provisioning procedure and reuse created by the virtual disk provisioning procedure generator 230, a virtual cluster provisioning procedure, a reusable virtual disk, Software installation and configuration program. The reuse virtual disk search unit 230 may assign an integer identifier to which a hash function is applied to the feature model of the virtual disk to be stored in the reuse asset storage, and search for the existing virtual disk in the reuse asset storage 300. .

The virtual disk provisioning procedure determiner 240 determines a provisioning procedure of the virtual disk according to the search result of the reused virtual disk searcher 230. In detail, the virtual disk provisioning procedure determiner 240 specifies a virtual disk provisioning procedure and method for specifying whether to create a merged virtual disk for a virtual cluster having a plurality of virtual machines through a new installation or a replication. Determine. When provisioning a virtual disk with a new installation, the virtual disk provisioning procedure generation unit 240 searches the reuse asset repository 300 for a software installer required for the installation and provisions the virtual disk 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 the operating system virtual disk corresponding to the operating system software and the application software virtual disk corresponding to the application software. The generated procedure includes the name and version information of the operating system software. The virtual disk provisioning procedure generator 240 may also generate a procedure for creating a virtual disk to be reused later. If a reusable virtual disk exists, the virtual disk provisioning procedure generation unit 240 generates a provisioning procedure of a virtual disk to be generated based on an asset to be set by searching and replicating a location where the reusable virtual disk is stored. That is, the virtual disk provisioning procedure generation unit 240 generates a reused virtual disk provisioning procedure for copying as it is based on the reusable virtual disk or installing additional application software. Therefore, the virtual disk provisioning procedure generation unit 240 should generate a procedure of duplicating the virtual disk to be reused, installing the necessary application software, and setting it in the reuse virtual disk provisioning procedure. The virtual disk to be cloned is analyzed by the reuse virtual disk search unit 230 and searched with an integer identifier obtained using a hash function. The virtual disk provisioning procedure generation unit 240 parses the reused asset statement of the retrieved reusable virtual disk and generates a reused virtual disk provisioning procedure.

The virtual disk generating unit 240 generates a virtual disk according to the generated virtual disk provisioning procedure. In detail, the virtual disk generating unit 240 associates the software with each of the first disk and the plurality of virtual machines, each of which may be shared and accessible by a plurality of virtual machines, and having a read operation installed only with software required for the plurality of virtual machines. A second disk capable of being written to. At this time, the virtual disk generating 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 for a file stored on the first disk, the virtual disk generator 240 copies the file stored on the first disk to the second disk and performs a write operation on the file copied to the second disk. do.

Accordingly, the virtual cluster building apparatus 200 merges a read-only virtual disk having necessary software installed therewith with a virtual disk capable of writing, thereby unlike an integrated virtual cluster construction in which only a virtual disk containing necessary software cannot be created. The storage space of the virtual disk can be used efficiently.

3 illustrates a virtual disk provisioning procedure according to an apparatus for managing virtual disk provisioning according to an embodiment of the present invention. For convenience of description, reference will be made to the components and reference numerals of FIG. 2.

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 may provide the virtual cluster provisioning included in the virtual cluster provisioning request for merging a plurality of virtual disks each including different software. Parse the specification. In this case, the virtual cluster provisioning specification can be parsed only when the virtual machine of the virtual cluster can be deployed to a specific physical host. The virtual cluster provisioning specification is a document in XML format conforming to the OVF standard, and the parsed result is generated as an internal data structure to be used by the virtual cluster building apparatus 200. In addition, the virtual cluster provisioning process execution unit 211 determines whether a virtual disk of a virtual cluster existing in the parsed specification can be created. The criterion that can be determined is whether there is space to store based on the size of the virtual disk of the specified virtual cluster and whether provisioning is possible up to the point of use of the virtual disk defined by the user. In order to perform this process, a shared storage for storing virtual disks must exist. The result of the determination is whether virtual disk provisioning is possible.

Subsequently, in response to the request, the virtual disk generating unit 240 generates a first disk on which software required in common for the plurality of virtual machines is installed, which can be shared and accessed by the plurality of virtual machines (S320).

In detail, the virtual disk generating unit 240 first generates an empty first disk named Vdisk_01. The name and size of the created first disk is determined based on the virtual disk provisioning procedure specified by the virtual disk provisioning procedure generation unit 230. The virtual disk generating unit 240 creates a file system specified by the user on the first disk, creates an empty directory whose name is vdisk_01, and mounts the first disk in the form of a loopback device. If the created first disk is mounted, the virtual disk generator 240 replicates or newly installs the virtual disk first disk on which the system software specified in the virtual disk provisioning procedure is installed. At this time, when the reuse virtual disk search unit 220 finds a reusable merged virtual disk on which the corresponding system software is installed, the virtual disk generator 240 replicates the reusable merged virtual disk on the first disk. In the case of the merged virtual disk, the virtual disk generating unit 240 copies the file and provisions the virtual disk even if the size of the virtual disk requested by the user does not match the size of the virtual disk to be reused. This is because, in the case of the merged virtual disk, the space of the virtual disk requested by the user may be created on the second disk, merged, and then provided. In this case, the second disk refers to a virtual disk associated with software and capable of writing to each of the plurality of virtual machines.

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

If there is application software that needs to be additionally installed after the virtual disk generator 240 installs the system software on the first disk, the virtual disk generator 240 creates a first disk for the application software named Vdisk_01_app. do. The virtual disk generating unit 240 generates a separate first disk without additionally installing application software on the first disk, which is Vdisk_01 on which system software is installed, to increase reusability of the virtual disk on which each software is installed. The virtual disk generating unit 240 installs a second disk Vdisk_01_app first disk also created a file system, and creates an empty directory named app01 and mounts it as a loopback device. In addition, the virtual disk generating unit 240 generates an empty directory for the application software and an empty directory named vdisk_01 / app01 under the directory on which the first disk mounted with the Vdisk_01 is mounted. Subsequently, the virtual disk generating unit 240 binds the first directory, vdisk_01 / app01, and the second directory, app01, to the vdisk_01 / app01 directory, which is created by binding each other. It will be installed in the app01 directory where you mounted the disk. The reason why the virtual disk generator 240 installs the application software through the bind mount is because the application software is dependent on the system software. If the virtual disk generator 240 installs the application software in the app01 directory on which the first disk mounted as the Vdisk_01_app is mounted, the application software dependent on the system software of the virtual machine is installed. In other words, the user requested that the application software OpenJDK7 be created in the form of a virtual disk that can run on Linux Debian 8.0 of the AMD64 architecture. to be. If the bind mount process is normally performed, the virtual disk generating 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 installation of the application software is completed, the virtual disk provisioning procedure generation unit 230 generates a virtual disk provisioning procedure for the virtual disk on which the system software is installed, and the generated virtual disk provisioning procedure and the asset ID are stored in the reuse asset repository 300. Stored. Thereafter, the virtual disk generating unit 240 unmounts the bind-mounted application software directory under the directory in which the system software is installed. In addition, the vdisk_01 directory on which the first virtual disk of Vdisk_01 is mounted and the app01 directory on which the first disk of Vdisk_01_app are mounted are also unmounted. Finally, the virtual disk generator 240 duplicates the generated first disk as many times as necessary. The system software and application software settings installed on the first disk are performed on the second disk assigned to the virtual machine.

Subsequently, the virtual disk generating unit 240 generates a second disk capable of a write operation in association with software in each of the plurality of virtual machines (S330).

In detail, the virtual disk generating unit 240 generates a second disk capable of writing in association with software installed on the first disk in each of the plurality of virtual machines. Here, the second disk is a virtual disk capable of storing data written by each virtual machine when the virtual disk shared by a plurality of virtual machines is used. The second disk applies system settings, such as hostname and IP address, to each virtual machine and provides space to store 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 where system software or application software exists, and if the system configuration does not exist for each virtual machine on the second disk, the first disk is recognized as a virtual machine having the same hostname and IP address. do. In addition, when a plurality of virtual machines write to the shared first disk at the same time, a file system created in the virtual disk is broken. Therefore, the shared first disk must be provisioned read-only and a separate second disk capable of storing the written data must be provided separately. 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 the system software and application software and to store data that is modified and generated.

Since the virtual disk generator 240 generates a second disk based on the system software information of the virtual machine, the system software information of the virtual machine to be generated in the virtual disk provisioning procedure is required. First, the virtual disk generating unit 240 generates 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 generated virtual disk. The virtual disk generator 240 mounts the generated second disk as a loopback device in empty directories named vdisk_01 and vdisk_02, and then creates directories existing in the root directory of the system software to be used by the virtual machine. For example, for Linux Debian, bin, dev, home, lib, media, opt, root, sbin, srv, usr, boot, etc, lib64, mnt, proc, run, selinux, sys, tmp, var. The virtual disk generator 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 on top of the root file system of the system software is to store data that the virtual machine modifies or writes. In addition, the virtual disk generating unit 240 replicates the directory and files in which all write operations that can occur during the booting process of the system software and application software are generated. For example, in Debian 8.0, the system's status, file system consistency checks, error information, and temporary storage are stored in the 'log' and 'tmp' subdirectories under 'var'. Stores information such as file deletion. As mentioned earlier, merged virtual disks provide read-only virtual disks with system software and application software, which prevents the virtual machine from writing to it at boot time. Accordingly, the virtual disk generator 240 removes an error in the booting process by moving a directory and a file where a write operation is performed to the second disk among the merged virtual disks provided for each virtual machine. Here, merge mounting is a technology in which all software components merge and provide one or more files rather than being integrated in one file or a directory existing in a file system of a physical host. The virtual disk generating unit 240 merges all files and directories existing in the lowerdir and the upperdir through merge mounting, and thus appears as one logical file structure. If the virtual disk generator 240 performs merge mounting with the directories of the first disk and the same name created on the second disk and the lowerdir and the upperdir, respectively, the directory of upperdir is associated with the actual system software. 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. In other words, the virtual machine is logically exposed as a logical file structure, but all data written by the user are created under the directory designated by upperdir, which is stored in a directory on the second disk. Therefore, when the virtual disk generator 240 assigns the first disk shared with a plurality of virtual machines to lowerdir, assigns the second disk to upperdir, and then performs merge mounting, all data generated by the virtual machine is transferred to upperdir. It is stored in the directory of the merged second disk to increase the reusability of the shared virtual disk. In addition, the virtual disk generator 240 stores the system settings of each virtual machine on the second disk and merges them, so that different hostnames and IP addresses are applied when the virtual machines are driven, thereby reusing the shared first disk. It can be maximized. When the virtual disk generating unit 240 generates the second disk, system settings are generated and stored in different directories and files according to the system software. In the case of Linux Debian, the virtual disk generator 240 creates a hosts file including hostnames and IP addresses of virtual machines such as hostname under the etc directory. In addition, the virtual disk generating unit 240 generates an IP address of each virtual machine as a file name of interfaces in the network directory under the etc directory. In addition to the system software settings, when there is a first disk on which application software is installed among the shared first disks, the virtual disk generating unit 240 stores the application software setting information on the second disk. In addition, the virtual disk generator 240 creates and stores a directory in which application software settings are to be stored on the second disk similarly to the system software settings, and in the case of Hadoop 2.6.0, creates a hadoop / conf directory under the opt directory. Create and save the necessary configuration files such as core-site.xml, hdfs-site.xml, mapred-site.xml, master and slaves. 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 have been created, the virtual disk generator 240 finally creates a work directory. In the merge mounting, the work directory is used as a directory for temporarily storing data used in the upperdir during merging, so the virtual disk generator 240 must create a work directory on the second disk. The virtual disk generating unit 240 terminates the operation after unmounting the second disk of the created virtual machine if all the configuration file creation tasks are completed.

In addition, when receiving a back-up request of the virtual machine, the virtual disk generating unit 240 stores a file capable of a write operation stored in the second disk. In addition, the virtual disk generating 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 such that only read operations are possible. Files that are writable include files copied from the first disk, which were previously read only.

Subsequently, the virtual disk generating unit 240 merges and mounts the first disk and the second disk (S340).

That is, the virtual disk generating unit 240 merges and mounts the first disk and the second disk to be seen as a tree. In this case, when the same file or folder exists on the first disk and the second disk, the virtual disk generating unit 240 allows the same file or folder of the second disk to be accessed. In addition, when there are a plurality of first disks having a plurality of versions of software installed thereon, the virtual disk generating unit 240 merges and mounts the plurality of first disks and the second disk. That is, the virtual disk generating 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 generated by the virtual disk generating unit 240 in which the respective softwares of the plurality of versions are installed.

According to some embodiments, when a write operation is requested for a file stored in the first disk, the virtual disk generating unit 240 copies the file stored in the first disk to the second disk and then copies the file to the second disk. Write to the file.

Accordingly, the virtual cluster building apparatus 200 may shorten the provisioning process of the virtual disk by separately creating a writeable virtual disk and sharing and using the virtual disk already created without creating a virtual disk on which software to be used is installed. Can be.

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

Referring to FIG. 4, the virtual cluster 410 may include a plurality of virtual machines, that is, a first virtual machine 411, a second virtual machine 412, a third virtual machine 413, and a fourth virtual machine 414. Have The first disk 421 is a virtual disk including system software and includes system software of Debian 8.0. In addition, the first disk 422 is a virtual disk including application software, and includes OpenJDK and Hbase 1.1.1. In this case, the first disks 421 and 422 may be read only, and may be shared among a plurality of other virtual machines. Each second disk 431, 432, 433, 434 is a first disk in the first virtual machine 411, the second virtual machine 412, the third virtual machine 413, and the fourth virtual machine 414. A virtual disk that performs write operations in association with system software and application software included in 421 and 422.

Referring to FIG. 4, the first virtual machine 411 shares first disks 421, 422 including Debian 8.0, OpenJDK, and Hbase 1.1.1, and displays data for Debian 8.0, OpenJDK, and Hbase 1.1.1. A second disk 431 capable of writing in case of creation and modification is included. The second virtual machine 412, the third virtual machine 413, and the fourth virtual machine 414 likewise share the first disks 421, 422 including Debian 8.0, OpenJDK, and Hbase 1.1.1, and Debian 8.0 The second disk 432 assigned to the second virtual machine 412 capable of writing, and the second disk assigned to the third virtual machine 413 when creating and modifying data for the OpenJDK and Hbase 1.1.1. 433 and second disk 434 allocated to fourth virtual machine 414, respectively. Accordingly, the first virtual machine 411, the second virtual machine 412, the third virtual machine 413, and the fourth virtual machine 414 are configured with Debian 8.0, OpenJDK, and the first disk 421, 422. Data for Debian 8.0, OpenJDK, and Hbase 1.1.1 via second disks 431, 432, 433, 434 that share Hbase 1.1.1 and correspond to the respective virtual machines 411, 412, 413, 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 application software included in the first disks 421, 422. Alternatively, application software or system software of a different version from the system software can be used through a write operation on the second disks 431, 432, 433, 434. For example, the first virtual machine 411 may use Hbase1.1.2, which is an upgraded version of Hbase1.1.1, via the second disk 421 capable of writing. In detail, the virtual cluster building apparatus 200 copies and upgrades 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, onto the second disk 421, Mounting by merging the second disk 431 containing the changed configuration file and the first disk 421 containing the same configuration file of Hbase1.1.1 as the configuration file of Hbase1.1.2 to be upgraded from Hbase1.1.1 to Hbase1.1.2. do. That is, even if 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 disks 421 and 422, the second virtual machine 411, the second virtual machine 412, and the fourth virtual machine 414 share the same first disks 421 and 422. A write operation on the virtual disks 431, 432, 433, and 434 may include a version of software different from the software installed on the first disks 421 and 422.

Accordingly, the virtual cluster building apparatus 200 can efficiently use the storage space of the virtual disk by providing a different version of software than the software included in the virtual disk that can be shared without a separate provisioning through the writeable virtual disk. And reduce virtual disk provisioning steps.

FIG. 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 one merged directory, that is, a mounting point. The directories to be merged can be included on the first and second disks, where all directories on the first disk, LowerDir, are read-only, and directories on the second disk, UpperDir, are read and write-only. Write). If a file or directory of the same name exists among the merged directories, the directory on the second disk, that is, the file in Upper Dir, has the highest read priority. In addition, the directory of the first disk, that is, Lower Dir, is configured as read only. All writes are then applied to directories on the second disk. Therefore, File1.txt and File3.txt exist in the directory 3 to be merged and the directory 2 to be merged, respectively, but the directory 3 to be merged and the directory 2 to be merged are all merge-mounted as read-only directories. Can not. Accordingly, when the user performs a write operation on the corresponding file in the merge-mounted directory, the virtual cluster building apparatus 200 of the second disk capable of writing the file existing in the directory 2 to be merged with the directory 2 to be merged is created. Reflects write after replication to directory1 to be merged. As a result, File1.txt and File3.txt are stored in the directory 1 to be merged.

Accordingly, the virtual cluster building apparatus 200 merges and mounts the first disk capable of reading only and the second disk capable of writing, thereby enabling writing of software included in the virtual disk.

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

Referring to FIG. 6, file system hierarchy 600 is a hierarchy of merged file systems where one or more application software references different libraries of the same name. For example, the application software 'A' and 'B' use the same library 'liba'. If the application software 'A' uses the library version '1.9' and the application software 'B' uses the library version '2.1', the virtual disk with the application software 'A' is installed when the merged virtual disk is created. 1.9 'version is installed, and' 2.1 'version library is installed on the virtual disk where application software' B 'is installed. In general, due to software dependency issues, there are standardized rules for 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 'liba.2.1' library. Since the virtual cluster building apparatus 200 merges the file systems installed in the respective merged virtual disks when the virtual machine is driven, the user has a 'liba.1.9' library file existing in the virtual disk where the application software 'A' is installed. The library files 'liba.2.1' of the virtual disk where the application software 'B' exists are all displayed at the same time. Therefore, even if the virtual cluster building apparatus 200 generates a merged virtual disk for each software element, the virtual cluster building apparatus 200 does not cause a software conflict problem.

7 (a) to 7 (d) illustrate the effects of virtual disk provisioning for building a virtual cluster according to another embodiment of the present invention.

Referring to FIG. 7A, a graph 710 of a single virtual disk creation time measurement result for each virtual disk type based on non-reuse and reuse is shown. Here, when reusing, when creating a new virtual disk by including the same software installed in the previously created virtual disk, it means to create a new virtual disk by copying the previously created virtual disk.

Referring to (a) of FIG. 7, the size of the virtual disk used to verify the effect of virtual disk provisioning is 3GB, 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-reusable integrated virtual disk 711 on the virtual machine allocated four VCPUs and 4 GB of memory has a creation time of 1273.85 seconds, and the non-reusable merge virtual disk 7812 has a creation time of 1217.69 seconds. It was. The creation time difference of the non-reusable integrated and merged virtual disks 711 and 712 can be regarded as a difference that can occur due to the use of external storage in which each software package exists. The creation time difference of the non-reuse integrated and merged virtual disks 711 and 712 may be regarded as a slight difference in installation time depending on the network environment of the external storage where the software package exists. Accordingly, it can be seen that the creation times of the non-reuse integrated and merged virtual disks 711 and 712 are similar regardless of the virtual disk type.

When reusing a virtual disk with system software installed, the total creation time of the integrated and merged virtual disks 713 and 714 represents 629.16 seconds and 608.96 seconds, respectively. If you reuse only the system software, you will see this result because the application software must be installed. As with the creation of non-reusable virtual disks 711 and 712, the difference in system software reuse integrated and merged virtual disk 713 and 714 creation time differences can be caused by the fact that the package of the application software to be installed is stored in external storage. This can be interpreted. As a result, even if the system software is reused, if there is application software that needs to be additionally installed, the creation time of the system software reuse integrated and merged virtual disks 713 and 714 may be confirmed to be similar. When both the system and the application software are reused, the creation time of the integrated and merged virtual disks 715 and 716 represents 356.17 seconds and 233.87 seconds, respectively. The reason why the creation time of the system and application software reuse merged virtual disk 716 is shortened compared to the system and application software reuse integrated virtual disk 715 may be seen as a result of the method difference of reusable virtual disk replication. System and application software reuse The integrated virtual disk 715 creates a blank disk image as large as the size of the virtual disk requested by the user, and then duplicates the contents of the reusable virtual disk. This is because if the size of the reusable virtual disk is 2.2 GB, the user cannot provide the requested 3 GB of virtual disk size. In contrast, the system and application software reuse merged virtual disk 716 may create and merge an upper disk to duplicate a virtual disk on which reusable software is installed. Here, the upper disk is a disk that stores the settings for the software installed in the merged virtual disk and stores the data to be stored due to the write operation. This is because if the size of the reusable virtual disk is 2.2GB, the upper disk should be created by providing 0.8GB. Replicating the contents of a reusable virtual disk repeatedly takes all the file-by-file copy operations, which consumes much more time than duplicating a single virtual disk file. Therefore, when all the software components are reused, merged disk creation time is inevitably shortened compared to the integrated type.

Referring to FIG. 7B, a graph 720 of a creation time result for each virtual disk type as the virtual machines included in one virtual cluster increases. For convenience of explanation, it will be described with reference to FIG. 7A.

Referring to (b) of FIG. 7, an integrated virtual disk creation time based on reuse on a virtual machine allocated with 4 VCPUs and 4 GB of memory shows an exponential increase in creation time exponentially with the number of virtual machines. . In particular, it can be seen that the increase in generation time increases slightly from the point when the number of virtual machines goes from eight (721) to sixteen (722). The reason why the reuse-based integrated virtual disk creation time is generated is because the number of created disks must be duplicated. That is, since the integrated type does not share the created virtual disks of virtual machines in the same virtual cluster, the number of virtual machines must be duplicated with the disks on which all necessary system software and application software are installed. And when cloning, it is necessary to duplicate the size of the virtual disk requested by the user repeatedly.

Referring to FIG. 7C, a graph 730 of a reduction rate of merged virtual disk creation time of 32 virtual machines included in a virtual cluster according to an increase in the maximum number of shared virtual machines per virtual disk is included.

Referring to FIG. 7C, a graph 730 of a rate of decrease in merged virtual disk creation time of 32 virtual machines included in a virtual cluster according to an increase in the maximum number of shared virtual machines per virtual disk is shown. In addition, it is expressed based on the creation time reduction rate when the maximum number of shared virtual machines per virtual disk is one. As a result, on a virtual machine with four VCPUs and 4 GB of memory, the reuse-based merged disk creation time is based on a total of 32 (736) virtual machines, up to one to four shared virtual machines per virtual disk. (731, 732, 733) showed a rapid decrease in production time. However, if the maximum number of shared virtual machines is four or more (733, 734, 735, 736), it can be seen that the reduced generation time ratio is reduced to 11% or less. That is, when the merged virtual disk creation method of the present invention is used, it can be seen that the maximum expectation reduction rate can be expected if the maximum shareable virtual machines per virtual disk is 4 (733). This means that even if the number of virtual machines included in the virtual cluster increases, the highest generation time reduction can be obtained when up to four (731, 732, 733) virtual machines share one virtual disk.

Referring to FIG. 7D, a graph 740 of a result of comparing the shared storage space used by virtual disk types according to the increase in the number of virtual machines in the virtual cluster is shown. Unified virtual disk 741 represents a linear shared storage usage size in proportion to the increase in the number of virtual machines present in the virtual cluster. This can be interpreted as a result of creating a virtual disk in proportion to the number of virtual machines in each virtual cluster. In addition, since the virtual machines in the virtual cluster do not share a virtual disk with homogeneous software, it can be concluded that the shared storage is used linearly according to the number of virtual machines. Merged virtual disks 742, 743, and 744 represented different shared storage footprints depending on the maximum number of shared virtual machines per virtual disk. First, if there were one (741) shared virtual machines per merged virtual disk, it represented the same storage footprint as the consolidated virtual disk. This is because the virtual machines of the virtual cluster are the same as when all the individual virtual disks are provided. However, each time the maximum number of shared virtual machines increases to two (742), four (743), and eight (744), they show 36.88%, 55.32%, and 64.54% reductions in storage space usage, respectively. Similar to the creation time reduction rate, the reduction rate of the shared storage space is lowered when the maximum number of shared virtual machines per merged virtual disk is four or more (743, 744). In conclusion, the creation time of the merged virtual disks 742, 743, and 744 is faster than the integrated virtual disk 741, even though the number of shared virtual machines increases. can confirm. In addition, it can be seen that the creation time of the integrated virtual disk 741 and the merged virtual disk 742, 743, 744 in proportion to the increase in the number of virtual machines in the virtual cluster. The used storage space of the shared storage also increased in proportion to the number of virtual machines shared by the integrated virtual disk 741 and the merged virtual disk 742, 743, and 744. In particular, when the maximum number of shared virtual machines among the merged virtual disks is one (742), it is confirmed that the shared storage of the same size as the integrated type is used. Of course, in terms of total virtual disk creation time, it is possible to create a disk faster than the integrated virtual disk 741, but considering the space used for the shared storage, the virtual machine with the minimum shared virtual machine should be installed on a virtual machine allocated with 4 VCPUs and 4 GB of memory. It can be concluded that it is reasonable to set up two or more (742, 743, 744) and then perform virtual disk provisioning.

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

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be implemented directly in hardware, a software module or a combination of the two executed by a processor. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, which can read information from and write information to the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside in a user terminal. In the alternative, 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 more detail with reference to the accompanying drawings, the present invention is not necessarily limited to these embodiments, and various modifications can be made without departing from the spirit of the present invention. . Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe 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 embodiments described above are exemplary in all respects and not restrictive. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

[Description of the code]

110 virtual machines

120, 140 virtual disks

130 software

131 system software

132 First Application Software

133 Second application software

200 Virtual Cluster Deployment Device

210 Virtual cluster provisioning process receiver

211 Virtual cluster provisioning process implementation

212 Virtual Cluster Provisioning Initiation

213 Virtual Cluster Provisioning Process Observer

220 Reuse Virtual Disk Finder

Creating Virtual Disk Provisioning Procedures

240 Virtual disk creation unit

300 reusable asset repository

410 virtual cluster

411 First virtual machine

412 Second virtual machine

413 Third Virtual Machine

414th virtual machine

421, 422 first disc

431, 432, 433, 434 2nd disc

600 file system hierarchy

710 Graph of measurement results of single virtual disk creation time by virtual disk type based on non-reuse and reuse

711 Non-Reuse Integrated Virtual Disks

712 Non-Reusable Merge Virtual Disks

713 Reusing System Software Integrated Virtual Disk

714 System Software Reuse Merged Virtual Disks

715 System and Application Software Reuse Integrated Virtual Disks

716 System and Application Software Reuse Merged Virtual Disks

720 Graph of Creation Time Result by Virtual Disk Type as Virtual Machines in a Cluster Subgroup Increase

721 virtual machines

16 virtual machines

The rate of decrease in the merged virtual disk creation time of 32 virtual machines in a virtual cluster subgroup as the maximum number of shared virtual machines per virtual disk increases.

Maximum number of shared virtual machines per 731 virtual disk

Maximum number of shared virtual machines per 732 virtual disk

Maximum number of shared virtual machines per 733 virtual disk

Maximum number of shared virtual machines per 734 virtual disk

Maximum number of shared virtual machines per 735 virtual disk 16

Maximum number of shared virtual machines per 736 virtual disk

740 Graph showing shared storage space usage by virtual disk type with increasing number of virtual cluster subgroups

1 shared virtual machine per 741 consolidated and merged virtual disks

2 shared virtual machines per integrated virtual disk and merged virtual disk

743 merged virtual disks and 4 shared virtual machines per merged virtual disk

8 shared virtual machines per 744 merged virtual disks and merged virtual disks

This application is the result of the following subjects.

Assignment Number: IITP-2016-R2720-16-0004

Department name: Ministry of Science, ICT and Future Planning

Specialized Research and Management Institution: Information and Communication Technology Promotion Center (IITP)

Project name: University ICT Research Center Promotion Support Project

Project Title: Development of High Performance Hybrid Cloud Computing Technology for Intelligent Information Service

Contribution rate: 1/1

Organizer: Konkuk University Industry-Academic Cooperation Foundation

Period: 2016.07.01 ~ 2019.12.31

Claims (18)

1. A method of building 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 on which software required in common for the plurality of virtual machines is installed that 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 writeable associated with the software; And

   And merging and mounting the first disk and the second disk, wherein the virtual cluster construction method comprises merging mounting of a read and write virtual disk.
2. The method of claim 1,

   Storing the data on which the location path of the second disk is recorded on the first disk,

   The first disk is a virtual cluster building method through the merge mounting of the read and write virtual disk, the read operation is set to only.
3. The method of claim 2,

   Receiving a back-up request of the virtual machine; And

   Storing a writeable file stored in the second disk;

   And the write-enabled file includes a file copied from the first disk, which was previously read-only.
4. The method of claim 1,

   The virtual cluster building method of claim 2, wherein the files associated with the software are stored in the second disk.
5. The method of claim 1,

   Merging and mounting the first disk and the second disk,

   And generating the merged first disk and the second disk to be viewed as a tree.
6. The method of claim 1,

   Merging and mounting the first disk and the second disk,

   When the same file or folder exists on the first disk and the second disk, the virtual cluster is established by merging mounting of a read and write virtual disk configured to access the same file or folder on the second disk Way.
7. The method of claim 1,

   The software exists in multiple versions,

   Generating the first disk,

   Creating a plurality of first disks on which software of each of the plurality of versions is installed,

   The mounting step,

   And a step of merging and mounting the plurality of first disks and the second disks.
8. The method of claim 7, wherein

   The mounting step,

   Merging and mounting the plurality of first disks such that different files are accessible in each of the plurality of versions of the software.
9. The method of claim 1,

   When a write operation is requested for a file stored in the first disk,

   Copying a file stored on the first disk to the second disk; And

   And performing the write operation on the file copied to the second disk, wherein the virtual cluster is constructed by merging mounting of the read and write virtual disk.
10. An apparatus for building a virtual cluster having a plurality of virtual machines,

    A virtual disk provisioning process receiving unit which receives a provisioning request for the virtual cluster having the plurality of virtual machines; And

    Create a first disk having software required in common for the plurality of virtual machines that are shared and accessible by the plurality of virtual machines in response to a provisioning request for the virtual cluster,

    Create a second disk in each of the plurality of virtual machines in association with the software to enable writing;

    And a virtual disk generating unit for merging and mounting the first disk and the second disk, wherein the virtual cluster building apparatus includes merging mounting of a read and write virtual disk.
11. The method of claim 10,

    The virtual disk generation unit,

    Storing data in which the location path of the second disk is recorded on the first disk,

    The first disk is a virtual cluster building apparatus through the merge mounting of the read and write virtual disk, which is configured to only read operations.
12. The method of claim 11,

    The virtual disk provisioning process receiver,

    Receiving a backup request of the virtual machine,

    The virtual disk generation unit,

    A file capable of a write operation stored in the second disk;

    And the write-enabled file includes a file copied from the first disk, which was previously read-only.
13. The method of claim 10,

    The virtual cluster construction apparatus of claim 2, wherein the files associated with the software are stored in the second disk.
14. The method of claim 10,

    The virtual disk generation unit,

    The virtual cluster building apparatus of claim 1, wherein the merged first disk and the second disk are viewed as a tree.
15. The method of claim 10,

    The virtual disk generation unit,

    If the same file or folder exists on the first disk and the second disk,

    The virtual cluster building apparatus of claim 2, wherein the same file or folder of the second disk is configured to be accessed.
16. The method of claim 10,

    The software exists in multiple versions,

    The virtual disk generation unit,

    Create a plurality of first disks on which software of each of the plurality of versions is installed,

    And a virtual mounting apparatus for merging and mounting the read and write virtual disks by merging and mounting the plurality of first disks and the second disks.
17. The method of claim 16,

    The virtual disk generation unit,

    And merging mounting of the read and write virtual disks to merge and mount the plurality of first disks so that different files are accessible in each of the plurality of versions of the software.
18. The method of claim 10,

    When a write operation is requested for a file stored in the first disk,

    The virtual disk generation unit,

    Copy the file stored on the first disk to the second disk,

    And a virtual mounting apparatus configured to perform a write operation on a file copied to the second disk, through merge mounting of a read and write virtual disk.

Images