KR20220058132A - Method and device to manage cloud orchestration template with version management system - Google Patents

Abstract

A method and an apparatus for managing a cloud orchestration template are disclosed. The method for managing the cloud orchestration template includes: identifying a user request included in an initiation request, in response to the initiation request of a virtual machine (VM); searching for a template with a version, determined by the user request, in an object storage; and initiating the VM that implements the user request in an orchestrator by transmitting a first template, which is searched and found in the object storage, to the orchestrator.

Description

Method and device for managing cloud orchestration template applying version control system

The present invention provides a cloud orchestration template management method and apparatus to which a version management system is applied to build a cloud environment customized to user requirements by proposing a system and process for managing a cloud orchestration template.

In particular, in the present invention, by using a template that can create and manage a version of a virtual machine according to a user's requirements, it can be used as an infrastructure to build an elastic cloud environment, a cloud orchestration template management method and apparatus suggest

Conventionally, only the open stack-based cloud orchestration method and device, and the multi-purpose virtual machine deployment method and device in the cloud computing environment are limited and described.

For example, in Korea Registration No. 2106223 (2020.04.23), in conjunction with the generation request of the template script, classifying user requirements included in the creation request, classifying the user requirements into functional requirements , creating a shell script for a selection item determined by a selection requirement (Option PR) belonging to the functional requirement, and generating a template script that executes the shell script, thereby receiving the template script from the hit orchestrator Disclosed is an OpenStack-based cloud orchestration method, including the step of driving a VM (Virtual Machine) implementing the functional requirements in (Heat Orchestrator).

Korea Registration No. 2106223 limits the configuration of creating template scripts by classifying user requirements into functional and non-functional requirements in OpenStack, an open source cloud platform. At this time, the template script is generated and used based on the mapping table for cloud orchestration.

In addition, Korea Registration No. 2129389, a list creation process that is performed by a virtual machine placement device, and generates a list according to a service request for placing a virtual machine (VM); a weight calculation process of calculating a weight for the purpose of the service request associated with the generated list; an objective function evaluation process of evaluating the purpose of the service request associated with the multipurpose function according to the weight; and a target machine selection process of selecting the corresponding virtual machine as a target machine when the evaluation score of the corresponding virtual machine (VM) is higher than the evaluation score of the initially selected VM; Discloses a multi-purpose virtual machine deployment method in a cloud computing environment that can be managed anytime, anywhere through

Korea Registration No. 2129389 indicates a list of virtual machines that can be created according to a service request, and is limited to selecting and deploying a target machine after going through an objective function evaluation process. Korea Registration No. 2129389 discloses a deployment method characterized in that each virtual machine is compared with an initially selected virtual machine through an evaluation score, and constraint conditions regarding resource waste and power consumption are satisfied.

Therefore, in order to build a user-customized cloud environment to be differentiated from the previously disclosed inventions, a basic template is managed and provided to be used when a change of the virtual machine is required, and the part where the virtual machine's resources are changed after that is accurately identified Identification skills are essential.

An embodiment of the present invention manages and provides a basic template to build a user-customized cloud environment and utilizes it when a virtual machine needs to be changed, and thereafter, version management that accurately identifies the part where the virtual machine's resources are changed A task to solve is to provide a method and device for managing a cloud orchestration template to which the system is applied.

In addition, according to an embodiment of the present invention, a new template having an updated version is created based on the identified resource changes, or a virtual machine is automatically arranged and efficiently managed by using a method of reusing an existing template. aim to do

According to an embodiment of the present invention, there is provided a method for managing a cloud orchestration template to which a version management system is applied, comprising: identifying a user requirement included in the driving request by interworking with a driving request of a virtual machine (VM); retrieving the version of the template determined by the user requirement from object storage; and transmitting the first template retrieved from the object storage to an orchestrator, so that the orchestrator drives a virtual machine implementing the user requirements.

In addition, the cloud orchestration template management apparatus to which the version management system is applied according to an embodiment of the present invention identifies a user requirement included in the driving request by interworking with a driving request of a virtual machine (VM) wealth; a search unit that searches object storage for a version of the template determined by the user requirements; and a processing unit that transmits the first template retrieved from the object storage to an orchestrator to drive a virtual machine that implements the user requirements in the orchestrator.

According to an embodiment of the present invention, in order to build a user-customized cloud environment, a basic template is managed and provided to be used when a change of the virtual machine is required, and thereafter, the part where the resource of the virtual machine is changed is accurately identified. A cloud orchestration template management method and device may be provided.

In addition, according to an embodiment of the present invention, a new template having an updated version is created based on the identified resource changes, or a virtual machine is automatically deployed and efficiently using a method of reusing an existing template. can be managed with

1 is a block diagram showing the configuration of a cloud orchestration template management apparatus to which the version management system of the present invention is applied.
2 is a structural diagram showing the operation of the cloud orchestration template management apparatus presented in the present invention.
3 is a flowchart of a process of a version control system according to the present invention;
4 is a diagram showing a case in which Ubuntu Linux 64-bit is selected according to a user's requirements, according to an embodiment of the present invention.
FIG. 5 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 4 .
6 is a view showing a case in which CentOS 7 x86-64 is selected according to a user's requirements, according to another embodiment of the present invention.
7 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 6 .
8 is a diagram for explaining an example of an index file whose major version is updated.
9 is a diagram illustrating a case in which C language is selected according to a user, according to a user's requirements, according to another embodiment of the present invention.
FIG. 10 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 9 .
11 is a diagram illustrating a case in which C++ language is selected according to a user's requirements, according to another embodiment of the present invention.
12 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 11 .
13 is a diagram for explaining an example of an index file whose major version is updated.
14 is a diagram illustrating a case in which 10 students are selected according to a user's requirements.
15 is a diagram illustrating a case in which 100 students are selected according to a user's requirements.
16 is a view showing an example of an index file in which the minor version is updated in relation to FIGS. 14 and 15 .
17 is a diagram showing an example of an index file including resource information of each version.
18 is a diagram illustrating an example of object storage in which a template file and an index file are stored.
19 is a flowchart illustrating a cloud orchestration template management method according to an embodiment of the present invention.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, since various changes may be made to the embodiments, the scope of the patent application is not limited or limited by these embodiments. It should be understood that all modifications, equivalents and substitutes for the embodiments are included in the scope of the rights.

The terms used in the examples are used for the purpose of description only, and should not be construed as limiting. The singular expression includes the plural expression unless the context clearly dictates otherwise. In this specification, terms such as "comprise" or "have" are intended to designate that a feature, number, step, operation, component, part, or a combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiment belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

In addition, in the description with reference to the accompanying drawings, the same components are given the same reference numerals regardless of the reference numerals, and the overlapping description thereof will be omitted. In describing the embodiment, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

1 is a block diagram showing the configuration of a cloud orchestration template management device to which the version management system of the present invention is applied.

1, according to an embodiment of the present invention, a cloud orchestration template management apparatus to which a version management system is applied (hereinafter, abbreviated as 'cloud orchestration template management apparatus', 100) is an identification unit 110, a search It may be configured to include the unit 120 and the processing unit 130 . In addition, the cloud orchestration template management apparatus 100 may additionally include the resource management unit 140 according to an embodiment.

The identification unit 110 identifies a user requirement included in the driving request by interworking with a driving request of a virtual machine (VM). That is, the identification unit 110 may serve to extract user requirements from a driving request input from the user in order to activate a virtual machine driven by specifications desired by the user.

The user requirement may be a concept including a function-specific request (functional requirement) that the virtual machine to be driven must have, and an external request (non-functional requirement) related to a connection to the virtual machine.

The search unit 120 searches for a template of a version determined by the user's requirement from object storage. That is, when a pre-written template that satisfies all user requirements is stored in the object storage, the search unit 120 may serve to search for a template of the corresponding version from the object storage.

For example, when [the number of users '15', Disk '40GB', image 'windows 8.1', RAM '4096MB'] is identified as user requirements, the search unit 120 has all of the user requirements. , the template of version V1.1 can be retrieved from object storage.

The processing unit 130 transmits the first template retrieved from the object storage to an orchestrator, so that the orchestrator drives a virtual machine that implements the user requirements. That is, the processing unit 130 generates a template script using a template (first template) retrieved from object storage by satisfying all user requirements, and then transmits it to the orchestrator, so that the user in the orchestrator receiving the template script It can serve to run a virtual machine (VM) that implements the requirements. Here, the template script may be a command, command syntax, etc. that enables the user's requirements to be realized in a virtual environment through the orchestrator.

If the version of the template is not stored in the object storage, the processing unit 130 creates a first template corresponding to the version by using a base template. That is, when the pre-written template that satisfies all user requirements is not stored in the object storage, the processing unit 130 uses the basic template of the regulation as a prototype, and can serve to directly create the corresponding version of the template. .

In the above example, if the basic template is defined as [number of users '1', Disk '20GB', image 'windows 8.1', RAM '20458MB'], the processing unit 130 in this basic template, the number of users / Disk By changing /RAM, you can directly create a template of version V1.1, which has all of the above user requirements [number of users '15', Disk '40GB', image 'windows 8.1', RAM '4096MB'].

Thereafter, the processing unit 130 may transmit the created first template to the orchestrator. That is, the processing unit 130 transmits the template script generated using the first template directly written to the orchestrator, and in the orchestrator, based on the template script, a virtual machine (VM) that implements the user requirements. can be made to run.

In order to check whether the version of the template requested by the user is stored in the object storage, the cloud orchestration template management apparatus 100 may additionally include a resource management unit 140 .

The resource management unit 140 checks resource information on all templates stored in the object storage through an index file. That is, the resource management unit 140 may play a role of receiving and checking resource information for each template stored in the object storage from an index file that interworks with the object storage and records resource information of the template.

Also, if the resource information does not find resource information corresponding to the user's requirement in the resource information, the resource management unit 140 may determine that the version of the template is not stored in the object storage. That is, the resource management unit 140 analyzes the resource information and determines that there is no resource information corresponding to the user requirement, thereby confirming that the required version of the template is not actually stored in the object storage.

As the version of the template is not stored in the object storage, the processing unit 130 may modify the resource information of the basic template to correspond to the user requirement. That is, the processing unit 130 may adjust the resource information of the basic template of the regulation according to the user requirements.

Thereafter, the processing unit 130 may create the first template by making the modified resource information correspond to the basic template. That is, the processing unit 130 may newly create a basic template corresponding to the adjusted resource information as the first template.

Also, the processing unit 130 classifies the degree of change from the resource information of the basic template according to the modification into 'Major' or 'Minor', and describes it in the resource information of the first template. That is, the processing unit 130 may identify how different the created first template is from the basic template by tagging it with 'Major' or 'Minor'.

For the above-described example of creating a template of version V1.1 in which 'number of users/Disk/RAM', which is a hardware resource, is changed in the basic template, the processing unit 130 tags the template of version V1.1 as 'Minor' can be distinguished by

If, in the basic template, for version 2.0 [number of users '60', Disk '80GB', image 'Ubuntu 18.04', RAM '8192MB'] that changes not only the hardware resources, but also the operating system image, the processing unit 130 can be identified by tagging the template of version V2.0 with 'Major'.

Also, the resource management unit 140 may record the resource information of the first template in the index file and store the first template in the object story. That is, the resource management unit 140 records the resource information in the index file for the template directly created, so that the resource information is systematically managed in the index file, and the created template is stored in the object story, so that the template is later It can be made to correspond to a search for

When a change in the user requirements occurs, the processing unit 130 is associated with the first template, determines whether the virtual machine is running, and as a result of the determination, if it is running, resource information of the first template is extracted from the index file, the extracted resource information of the first template is modified to correspond to the changed user requirements, the modified resource information is matched to the first template, and the second template is updated. can

That is, the processing unit 130 adjusts the resource information of the first template when a change occurs in user requirements while the first template according to the existing user requirements is implemented as a virtual machine, and a template that meets the changed user requirements After writing , by updating the second template, the second template according to the changed user requirements can be implemented as a virtual machine.

On the other hand, as a result of the determination, if it is not being driven, the processing unit 130 modifies the resource information of the basic template to correspond to the changed user requirements, and the modified resource information corresponds to the basic template, and the second It can be written as a template.

That is, if the first template is not currently implemented as a virtual machine and is only maintained in object storage, the processing unit 130 creates a template according to the changed user requirements by adjusting the resource information of the basic template, and then By passing it to the orchestrator as a second template, the orchestrator can run a virtual machine that implements the changed user requirements.

According to an embodiment of the present invention, in order to build a user-customized cloud environment, a basic template is managed and provided to be used when a change of the virtual machine is required, and thereafter, the part where the resource of the virtual machine is changed is accurately identified. A cloud orchestration template management method and device may be provided.

In addition, according to an embodiment of the present invention, a new template having an updated version is created based on the identified resource changes, or a virtual machine is automatically deployed and efficiently using a method of reusing an existing template. can be managed with

2 is a structural diagram showing the operation of the cloud orchestration template management apparatus presented in the present invention.

The roles and operations of the main means (components) included in FIG. 2 are as follows.

The Version Management System 210 may serve to manage versions of the orchestration template. The Version Management System 210 performs a version search of a template in the Object Storage 220 based on the user's requirements, reuses an existing stored template, or creates a new version of a template to build a cloud environment. can play a role in managing them.

The Object Storage 220 may be a storage for storing objects. The Object Storage 220 may store an orchestration template having version information and an Index File 240 having connection information for each template file.

The Orchestrator 230 is a device that performs a series of tasks for integrating cloud resources based on an orchestration template, and may be an engine that generates a virtual machine by interpreting the orchestration template.

The Index File 240 may be a file having resource information of all versions stored in the Object Storage 220 . The Version Management System 210 may perform a template version search, create a new template version, and the like, through the Index File 240 . That is, the Index File 240 may serve to connect the template file corresponding to each version and the version management system.

The base template is an initial version corresponding to V1.0, and may include resource information and version information that the orchestration template should have. The orchestration template of each version is configured in the form indicated by the basic template, and can be divided into Major and Minor and updated according to the modification level of the changed resource information.

The Version Management System 210 operates in the following process.

(1) The Version Management System 210 receives the requirements requested by the user. The Version Management System 210 may receive a request from the user for requirements (CPU, Memory, Disk usage, images, etc.) for the environment of the virtual machine that the user needs.

(2) The Version Management System 210 may search for a template version based on the requested requirement. The Version Management System 210 may perform a version search for a template for creating a corresponding virtual machine based on information corresponding to a user's requirements. If there is a template that meets the requirements, the Version Management System 210 returns the searched version of the template. If there is no template that meets the requirements, the Version Management System 210 creates a new template by using the default template, based on the template version management rule.

(3) The Version Management System 210 makes it possible to create a virtual machine (VM). The Version Management System 210 transmits the discovered template or the created template to the Orchestrator 230 , so that the Orchestrator 230 creates a virtual machine to which resources appropriate to the template file are allocated.

(4) The Version Management System 210 receives it when a user changes a requirement. Upon receipt of the changed requirements, when a change in hardware or operating system occurs for a previously created and operated virtual machine, the Version Management System 210 updates the template and version information according to the prescribed template version management rules. do.

In addition, the Version Management System 210 stores the newly created template in the Object Storage 220 in which the basic template is stored. In addition, the Version Management System 210 may form a version tracking relationship between templates by updating the Index File 240 at the same time as saving the template file.

[Table 1] is an example of a version control table that stores the version tracking relationship between templates.

[Table 1] shows an example in which the stored template and version information are managed according to the template version management rule.

In [Table 1], it can be seen that, in the case of updating from version V1.0 to V1.1, several items were changed, but only hardware resources (Disk, RAM, number of users) were added or improved in all.

The Version Management System 210 may apply <Minor Version> regardless of the number of changed items when updating from version V1.0 to V1.1, in which only hardware resources are changed.

On the other hand, when it is updated from version V1.0 to V2.0 or V3.0, the image (operating system) is changed and this can be a large-scale change. Accordingly, the Version Management System 210 may apply <Major Version> when updating from version V1.0 to V2.0 or V3.0 regardless of whether the hardware resource is changed.

The Version Management System 210 applies version management to the template file to enable flexible operation in the cloud environment.

The first created template file is defined as a basic template, and is written as the version name of V1.0 as shown in Table 1.

Also, according to the modification level of the changed resource information, the Version Management System 210 defines the <Major Version> and <Minor Version> concepts.

<Major Version> means to update the version number when a large-scale change occurs. For example, when changing the operating system in the basic template, it can be classified as a <Major Version> type.

<Minor Version> means updating the version number when a function that was not in the previous version is added or improved. For example, when changing hardware resources in the basic template, it can be classified as a <Minor Version> type.

3 is a flowchart of a process of a version control system according to the present invention;

In step 310, the version control system may request a requirement for the environment of the virtual machine through the service UI.

In step 320, the version control system may automatically issue a token (Token).

In operation 330, the version control system may search for a template file version corresponding to the corresponding requirement.

In step 340, the version control system determines whether there is a template file version corresponding to the requirement.

If there is no file version (No direction in step 340), in step 350, the version control system stores and updates the version of the template file according to the proposed requirements.

If there is a file version (Yes direction in step 310), in step 360, the version control system creates a virtual machine based on the template file of the corresponding version.

In step 370, the version control system determines whether to change the resource in the created virtual machine.

If there is a resource change (in the Yes direction of step 370), the version control system returns to step 310 .

If there is no resource change (direction No in step 370), the version control system ends.

Hereinafter, the cloud orchestration template management apparatus of the present invention will be described by way of example applied to a coding education system.

The cloud orchestration template management apparatus 100 may create an instructor's virtual machine for opening a lecture.

The cloud orchestration template management apparatus 100 may create a virtual machine serving as a classroom to teach students according to the requirements of the instructor. The cloud orchestration template management apparatus 100 may provide a file such as an educational image or a program code through the created virtual machine, and may provide an education service with data provided to students accessing the virtual machine.

The cloud orchestration template management apparatus 100 may update the version by adjusting the virtual machine resource.

The cloud orchestration template management apparatus 100 may perform version update when the resource of the virtual machine being used is not suitable in the current environment. The cloud orchestration template management apparatus 100 may set a major change, such as an operating system or a new educational language, as a major. Alternatively, the cloud orchestration template management apparatus 100 may use a template of the most suitable environment according to a corresponding criterion after determining as a Minor for a change in a compute environment (system resource) for reducing the overload of the virtual machine. .

The cloud orchestration template management apparatus 100 may adjust resources according to requirements for each scenario.

The cloud orchestration template management apparatus 100 may require resource adjustment according to various situations in the initially created virtual machine.

[Table 2] is a mapping table for template version management in the cloud-based coding education system.

[Table 2] shows the conditions and variables for building an educational environment, and it can be seen that the resources adjusted according to each variable are set differently.

One of the conditions for updating the major version is the image (operating system).

4 is a diagram showing a case in which Ubuntu Linux 64-bit is selected according to a user's requirements, according to an embodiment of the present invention.

FIG. 5 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 4 .

When the instructor selects the operating system of Ubuntu Linux 64-bit through the web interface as in FIG. 4, the cloud orchestration template management device 100 can create a VM through the HOT template, as shown in FIG. 5, based on this. there is.

6 is a diagram illustrating a case in which CentOS 7 x86-64 is selected according to a user's requirements, according to another embodiment of the present invention.

7 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 6 .

When the instructor selects the operating system of CentOS 7 x86-64 through the web interface as shown in FIG. 6 , the cloud orchestration template management device 100 can create a VM through the HOT template as shown in FIG. 7 based on this. there is.

8 is a diagram for explaining an example of an index file whose major version is updated.

The cloud orchestration template management apparatus 100 may store the updated major version in the index file by creating a coding environment of an image (operating system) that does not exist before, as shown in FIG. 8 .

The cloud orchestration template management apparatus 100 may automatically install software necessary for execution according to which 'coding language' is to be taught. The corresponding condition is implemented through Software Configuration and is an item that can be selected in multiple ways, and the cloud orchestration template management apparatus 100 may classify it as a major version when even one of the selected languages is different.

9 is a diagram illustrating a case in which C language is selected according to a user, according to a user's requirements, according to another embodiment of the present invention.

FIG. 10 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 9 .

9 and 10 , the cloud orchestration template management apparatus 100 may generate a VM in which a gcc compiler capable of compiling C language is installed through a template generated when C language is selected.

11 is a diagram illustrating a case in which C++ language is selected according to a user's requirements, according to another embodiment of the present invention.

12 is a diagram illustrating an example of creating a VM through a HOT template in relation to FIG. 11 .

11 and 12 , the cloud orchestration template management apparatus 100 may generate a VM in which a g++ compiler capable of compiling a C++ language is installed through a template generated when a C++ language is selected.

The cloud orchestration template management apparatus 100 may update a major version by creating a coding environment of a language that does not exist.

13 is a diagram for explaining an example of an index file whose major version is updated.

For flexible operation of virtual machines, virtual machines that have been trained are automatically shut down. At this time, the cloud orchestration template management apparatus 100 designates a period for maintaining the education data, so that the virtual machine is maintained for the specified period even after the education is finished, so that materials used for education can be used.

The first condition for minor version update is the number of users. In order to handle the overhead that increases as the number of users accessing the virtual machine increases, the number of CPUs or the size of RAM must be increased. Conversely, if more resources are given compared to the person connecting, in order to avoid wasting resources, resource allocation should be reduced.

For example, the cloud orchestration template management apparatus 100 provides one CPU based on 20 users.

14 is a diagram illustrating a case in which 10 students are selected according to a user's requirements.

15 is a diagram illustrating a case in which 100 students are selected according to a user's requirements.

16 is a view showing an example of an index file in which the minor version is updated in relation to FIGS. 14 and 15 .

In the case of 10 students in FIG. 14 and in the case of 100 students in FIG. 15 , the cloud orchestration template management device 100 sets the flavor according to the number of students as “m1.small”, “m1” as shown in FIG. .xlarge” can be allocated.

Also, as shown in FIG. 16 , the cloud orchestration template management apparatus 100 may update a minor version when a flavor is changed.

And since the amount of files to be stored by the virtual machine will increase according to the training period, the cloud orchestration template management apparatus 100 arranges a large-capacity storage as the training becomes longer.

In addition, in a special case such as a test, since the number of users of the virtual machine may increase rapidly, the cloud orchestration template management apparatus 100 replaces the flavor so as to handle the overhead of the corresponding event period.

17 is a diagram showing an example of an index file including resource information of each version.

As shown in FIG. 17 , the cloud orchestration template management apparatus 100 may classify versions according to criteria determined by Major and Minor and store resource information according to the versions in an index file.

18 is a diagram showing an example of object storage in which a template file and an index file are stored.

The cloud orchestration template management apparatus 100 may store all the generated template files in the object storage, as shown in FIG. 18 . In addition, the cloud orchestration template management apparatus 100 may build a user-customized cloud environment by reusing the stored template according to a change in user requirements or a change in the cloud operating environment.

Hereinafter, a work flow of the cloud orchestration template management apparatus 100 according to embodiments of the present invention will be described in detail with reference to FIG. 19 .

The cloud orchestration template management method according to the present embodiment may be performed by the cloud orchestration template management apparatus 100 .

6 is a flowchart illustrating a cloud orchestration template management method according to an embodiment of the present invention.

First, the cloud orchestration template management apparatus 100 identifies a user requirement included in the driving request by interworking with the driving request of the virtual machine ( S1910 ). Step 1910 may be a process of extracting user requirements from a driving request input from the user to activate a virtual machine driven with a specification desired by the user.

The user requirement may be a concept including a function-specific request (functional requirement) that the virtual machine to be driven must have, and an external request (non-functional requirement) related to a connection to the virtual machine.

Also, the cloud orchestration template management apparatus 100 searches for a template of a version determined by the user requirement from the object storage (S20). Step 1920 may be a process of searching for a template of a corresponding version from the object storage when a pre-written template that satisfies all user requirements is stored in the object storage.

For example, when [the number of users '15', Disk '40GB', image 'windows 8.1', RAM '4096MB'] is identified as a user requirement, the cloud orchestration template management device 100 performs the user requirements You can retrieve all of the templates from version V1.1 from object storage, which you have.

Subsequently, the cloud orchestration template management apparatus 100 transmits the first template retrieved from the object storage to the orchestrator, thereby driving the virtual machine implementing the user requirements in the orchestrator (1930). In step 1930, a template script is generated using a template (first template) retrieved from the object storage by satisfying all user requirements, and then delivered to the orchestrator, so that the orchestrator that has received the template script receives the user requirements It may be a process of driving a virtual machine (VM) that implements . Here, the template script may be a command, command syntax, etc. that enables the user's requirements to be realized in a virtual environment through the orchestrator.

If the version of the template is not stored in the object storage, the cloud orchestration template management apparatus 100 creates a first template corresponding to the version by using the basic template. That is, the cloud orchestration template management device 100 can directly create a template of the corresponding version by using the basic template of the regulation as a prototype when a pre-written template that satisfies all user requirements is not stored in the object storage. .

In the above example, if the default template is defined as [the number of users '1', Disk '20GB', image 'windows 8.1', RAM '20458MB'], the cloud orchestration template management device 100 in this basic template, By changing the number of users/Disk/RAM, create your own template of version V1.1, which has all of the above user requirements [number of users '15', Disk '40GB', image 'windows 8.1', RAM '4096MB'] can

Thereafter, the cloud orchestration template management apparatus 100 may transmit the created first template to the orchestrator. That is, the cloud orchestration template management device 100 transmits a template script generated using the first template directly created to the orchestrator, and in the orchestrator, based on the template script, virtual implementation of the user requirements You can make it run a machine (VM).

In order to check whether the version of the template requested by the user is stored in the object storage, the cloud orchestration template management device 100 uses an index file (Index File) to store resource information on all templates stored in the object storage. Check it. That is, the cloud orchestration template management apparatus 100 may receive and check resource information for each template stored in the object storage from an index file that is linked with the object storage and records resource information of the template.

Also, if the cloud orchestration template management apparatus 100 does not find resource information corresponding to the user requirement in the resource information, it may be determined that the version of the template is not stored in the object storage. That is, the cloud orchestration template management apparatus 100 analyzes the resource information and determines that there is no resource information corresponding to the user requirement, thereby confirming that the required version of the template is not actually stored in the object storage.

As the version of the template is not stored in the object storage, the cloud orchestration template management apparatus 100 may modify resource information of the basic template to correspond to the user requirement. That is, the cloud orchestration template management apparatus 100 may adjust the resource information of the basic template of the regulation according to user requirements.

Thereafter, the cloud orchestration template management apparatus 100 may create the first template by making the modified resource information correspond to the basic template. That is, the cloud orchestration template management apparatus 100 may newly create a basic template corresponding to the adjusted resource information as the first template.

In addition, the cloud orchestration template management apparatus 100 classifies the degree of change from the resource information of the basic template according to the modification into 'Major' or 'Minor', and describes it in the resource information of the first template do. That is, the cloud orchestration template management apparatus 100 may identify how different the created first template is from the basic template by tagging it with 'Major' or 'Minor'.

With respect to the above example of creating a template of version V1.1 in which 'number of users/Disk/RAM', which is a hardware resource, is changed in the basic template, the cloud orchestration template management device 100 is 'in the template of version V1.1' They can be identified by tagging them as 'Minor'.

Cloud orchestration template management for version 2.0 [number of users '60', disk '80GB', image 'Ubuntu 18.04', RAM '8192MB'] that changes not only hardware resources, but also the operating system image in the basic template The device 100 can be identified by tagging the template of version V2.0 with 'Major'.

Also, the cloud orchestration template management apparatus 100 may record the resource information of the first template in the index file and store the first template in the object story. That is, the cloud orchestration template management apparatus 100 records the resource information in the index file for the template directly created, so that the resource information is systematically managed in the index file, and the created template is stored in the object story, It can be made to correspond to a search for a template later.

When a change in the user requirements occurs, the cloud orchestration template management apparatus 100 determines whether the virtual machine is running in association with the first template, and as a result of the determination, if it is running, the first Extracting the resource information of the template from the index file, modifying the extracted resource information of the first template to correspond to the changed user requirements, and matching the modified resource information to the first template, a second The template can be updated.

That is, the cloud orchestration template management apparatus 100 adjusts the resource information of the first template when a change occurs in user requirements while the first template according to the existing user requirements is implemented as a virtual machine, and the changed user requirements After creating a template that meets the requirements and updating the second template, the second template according to the changed user requirements can be implemented as a virtual machine.

On the other hand, as a result of the determination, if not in operation, the cloud orchestration template management apparatus 100 modifies the resource information of the basic template to correspond to the changed user requirements, and the modified resource information corresponds to the basic template , can be written as the second template.

That is, if the first template is not currently implemented as a virtual machine and is only maintained in object storage, the cloud orchestration template management device 100 adjusts the template according to the changed user requirements to the resource information of the basic template. After writing it, by passing it to the orchestrator as a second template, the orchestrator can run a virtual machine that implements the changed user requirements.

According to an embodiment of the present invention, in order to build a user-customized cloud environment, a basic template is managed and provided to be used when a change of the virtual machine is required, and thereafter, the part where the resource of the virtual machine is changed is accurately identified. A cloud orchestration template management method and device may be provided.

In addition, according to an embodiment of the present invention, a new template having an updated version is created based on the identified resource changes, or a virtual machine is automatically deployed and efficiently using a method of reusing an existing template. can be managed with

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Software may comprise a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device. The software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or apparatus, to be interpreted by or to provide instructions or data to the processing device. , or may be permanently or temporarily embody in a transmitted signal wave. The software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

As described above, although the embodiments have been described with reference to the limited drawings, those skilled in the art may apply various technical modifications and variations based on the above. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

100: Cloud orchestration template management device
110: identification unit 120: search unit
130: processing unit 140: resource management unit

Claims (17)

In conjunction with the request to run a virtual machine (VM, Virtual Machine),
identifying user requirements included in the driving request;
retrieving a version of the template determined by the user requirement from object storage; and
By transferring the first template retrieved from the object storage to an orchestrator, the orchestrator drives a virtual machine that implements the user requirements.
A cloud orchestration template management method with a version control system that includes According to claim 1,
If the version of the template is not stored in the object storage,
creating a first template corresponding to the version by using a base template; and
transmitting the created first template to the orchestrator
A cloud orchestration template management method with a version control system that further includes. 3. The method of claim 2,
checking resource information on all templates stored in the object storage through an index file; and
In the resource information, if resource information corresponding to the user requirement is not found,
confirming that the version of the template is not stored in the object storage;
A cloud orchestration template management method with a version control system that further includes. 4. The method of claim 3,
Creating the first template comprises:
modifying the resource information of the basic template to correspond to the user requirements; and
Corresponding the modified resource information to the basic template, creating the first template
A cloud orchestration template management method with a version control system that includes 5. The method of claim 4,
Creating the first template comprises:
Classifying the degree of change from the resource information of the basic template according to the modification into 'Major' or 'Minor', and writing in the resource information of the first template
A cloud orchestration template management method with a version control system that further includes. 5. The method of claim 4,
The cloud orchestration template management method comprises:
Recording the resource information of the first template in the index file and storing the first template in the object story
A cloud orchestration template management method with a version control system that further includes. According to claim 1,
When changes to the above user requirements occur,
In association with the first template, determining whether the virtual machine is running;
As a result of the determination, if it is running,
extracting the resource information of the first template from an index file;
modifying the resource information of the extracted first template to correspond to the changed user requirements; and
Corresponding the modified resource information to the first template and updating to a second template
A cloud orchestration template management method with a version control system that further includes. 8. The method of claim 7,
As a result of the above determination, if it is not running,
modifying the resource information of the basic template to correspond to the changed user requirements; and
Corresponding the modified resource information to the basic template, creating the second template
A cloud orchestration template management method with a version control system that further includes. In conjunction with the request to run a virtual machine (VM, Virtual Machine),
an identification unit for identifying user requirements included in the driving request;
a search unit that searches for a version of the template determined by the user requirement from object storage; and
A processing unit that transmits the first template retrieved from the object storage to an orchestrator to drive a virtual machine that implements the user requirements in the orchestrator
A cloud orchestration template management device with a version control system that includes 10. The method of claim 9,
If the version of the template is not stored in the object storage,
The processing unit,
Using a base template, create a first template corresponding to the version,
delivering the created first template to the orchestrator
Cloud orchestration template management device with version control system applied. 11. The method of claim 10,
Check resource information for all templates stored in the object storage through an index file, and if resource information corresponding to the user requirement is not found in the resource information, the version of the template is Resource management plane that confirms that it is not stored in object storage
A cloud orchestration template management device to which a version control system is applied further comprising a. 12. The method of claim 11,
The processing unit,
Modify the resource information of the basic template to correspond to the user requirements,
Corresponding the modified resource information to the basic template to create the first template
Cloud orchestration template management device with version control system applied. 13. The method of claim 12,
The processing unit,
According to the modification, the degree of change from the resource information of the basic template is divided into 'Major' or 'Minor', which is described in the resource information of the first template
Cloud orchestration template management device with version control system applied. 13. The method of claim 12,
The resource management unit,
Recording the resource information of the first template in the index file and storing the first template in the object story
Cloud orchestration template management device with version control system applied. 10. The method of claim 9,
When changes to the above user requirements occur,
The processing unit,
In association with the first template, it is determined whether the virtual machine is running,
As a result of the determination, if it is running,
Extracting the resource information of the first template from the index file, modifying the extracted resource information of the first template to correspond to the changed user requirements, and matching the modified resource information to the first template , to update with the second template
Cloud orchestration template management device with version control system applied. 16. The method of claim 15,
As a result of the above determination, if it is not running,
The processing unit,
Modify the resource information of the basic template to correspond to the changed user requirements,
The modified resource information corresponds to the basic template to create the second template
Cloud orchestration template management device with version control system applied. A computer-readable recording medium recording a program for executing the method of any one of claims 1 to 8.

Images