KR102019486B1 - Update method of containers in virtual system and apparatus thereof - Google Patents

Abstract

The present invention relates to a data updating method of a container updating apparatus in a virtualization system for operating a plurality of virtual machine containers, the container updating apparatus generating a plurality of containers on a host OS, for the plurality of containers Storing common data in a first hierarchical base image, storing common data for at least some of the plurality of containers in a second hierarchical base image, and when a container update request for any common data is received, update And updating based on the layer of the base image in which the common data is stored, wherein the first layer base image is lower than the second layer base image.

Description

Update method of containers in virtual system and apparatus

The present invention relates to a method and apparatus for updating a container in a virtualization system. More specifically, a container update method for improving container update speed by storing and managing common data as a base image in a container-based virtualization system. To the device.

The hypervisor-based virtualization system, as shown in FIG. 1, installs a host operating system (OS) 102 on the hardware 101 and through the host OS 102. When the 103 is driven, the hypervisor 103 divides resources to create a virtual machine 104, and installs a guest OS 105 in each virtual machine 104 to operate individually. Each virtual machine 104 is assigned to each user so that the user perceives the use of a physically separate, independent device and runs various applications 106 on the guest OS 105. .

This virtualization system has the advantage of being able to operate multiple server environments independently in one physical system, but it requires a lot of resource waste because each virtual machine 104 has to allocate resources for the individual guest OS 105. Has disadvantages. In addition, in the hypervisor-based virtualization system, there is a problem that the system efficiency is inferior in that the application 106 must pass through the guest OS 105 in order to use the host OS 102 resources.

In order to solve this problem, container-based virtualization systems have recently been developed. The container-based virtualization system is a technology for installing a host OS 202 on hardware 201 and creating a plurality of containers 203 on the host OS 202 as a virtual machine, as shown in FIG. 2. Each container 203 can use individual data (eg, binary code, library, etc.) independently installed and used in the container, and common data can be utilized through sharing between the containers 203 to efficiently utilize resources. Make sure

In the container-based virtualization system, resources are saved in that the guest OS for each virtual machine is not separately installed, and the system does not go through the guest OS even when a host OS 202 resource such as common data is desired. The efficiency is good.

When operating a plurality of virtual machine servers that provide web services using the container-based virtualization system, the container-based virtualization system may be configured as shown in FIG. In particular, the virtualization system may create each server container 303 as a virtual machine that provides the same or different web services for each client 306 on the host OS 302. Some of the server containers 303 may provide a first web service, for example Jenkins, to a corresponding client, and others may correspond to a second web service, for example, bugzilla. Can be provided to

Each server container 303 may store web service data 304 (eg, Apache, Mysql, PHP, etc.) needed to provide a corresponding web service. The server container 306 that provides the same web service may have the same at least a portion of the web service data 304. Nevertheless, in the conventional container-based virtualization system shown in FIG. 3, each server container 303 stores web service data 304 separately. Individual data that is not identical between the server container 303 (other portions of the web service data or data other than the web service data) may be stored in the delta area 305 of each server container 306.

In the conventional container-based virtualization system as described above, when an update for any web service occurs, all server containers 306 providing the web service are individually updated. In this prior art, even if the container update is processed in parallel, there is a problem that the entire update takes a lot of time and the update performance is deteriorated due to lack of resources.

The present invention is to solve the above problems, and provides a container update method and apparatus that can improve the update rate of the container by storing and managing common data as a base image in a container-based virtualization system.

The container update method according to the present invention for solving the above problems is a data update method of a container update device in a virtualization system for operating a plurality of virtual machine container, the container update device is a plurality of containers on a host OS Generating, storing common data for the plurality of containers in a first hierarchical base image, storing common data for at least some of the plurality of containers in a second hierarchical base image, and any common If a container update request for data is received, performing an update based on a layer of a base image in which common data to be updated is stored, wherein the first layer base image is a lower layer than the second layer base image It features.

The performing of the update may include performing a first update operation when the common data to be updated is stored in the lowest hierarchical base image, wherein the first update operation includes: Designating a stored base image as an installation directory and executing an update on the installation directory.

The performing of the update may include performing a second update operation when the common data to be updated is not stored in the lowest hierarchical base image, wherein the second update operation comprises: updating the common data. Designating at least one lower layer base image of a base image in which data is stored as a read-only area, and designating a base image in which the common data to be updated is stored as a read and write area, wherein the at least one lower layer base image and the Combining and mounting the common data to be updated, designating the mount point as an installation directory, and executing an update on the installation directory.

The performing of the updating may include performing the first update operation on the lowest layer base image among the base layers of the plurality of layers when the common data to be updated is stored in the base images of the plurality of layers. And repeating the second update operation from the next lower layer base image of the lowest layer base image to the highest layer base image until the highest layer base image of the plurality of layer base images is updated. Characterized in that it comprises a.

In addition, the plurality of containers operate as a server providing a web service, and the common data stored in the first hierarchical base image is web service data necessary for providing the web service, and the second hierarchical base image. The common data stored in the web service data may be web service data necessary to provide a specific web service provided by the at least some of the plurality of containers.

In addition, the container update apparatus according to the present invention for solving the above problems is a data update device for providing a virtualization system for operating a plurality of virtual machine containers, the data for a plurality of containers created on the host OS A storage unit for storing and dividing the resources of the storage unit for allocation to each of the plurality of containers, storing common data for the plurality of containers in a first hierarchical base image, and at least some of the plurality of containers And a controller configured to store the common data for the second layer base image and to update the container based on the layer of the base image in which the common data to be updated is stored when the container update request for the arbitrary common data is received. The first layer base image is the second layer base It is characterized in that the lower layer than the image.

The controller may perform a first update operation when the common data to be updated is stored in the lowest hierarchical base image, wherein the first update operation designates a base image in which the common data to be updated is stored as an installation directory. And updating the installation directory.

The controller may perform a second update operation when the common data to be updated is not stored in the lowest hierarchical base image, wherein the second update operation includes at least one of the base image in which the common data to be updated is stored. Designate a lower layer base image of the read-only area, a base image storing the common data to be updated as a read and write area, mount and mount the at least one lower layer base image and the common data to be updated. And designating the mount point as an installation directory and executing the update on the installation directory.

The controller may perform the first update operation on the lowest layer base image among the base layers of the plurality of layers when the common data to be updated is stored in the base images of the plurality of layers. The second update operation is repeatedly performed from the next lower layer base image of the lowest layer base image to the highest layer base image until the highest layer base image of the base layers of the three layers is updated.

Container update method and apparatus in the virtualization system according to the present invention, in the container-based virtualization system, even when the number of containers is reduced, the time required for updating the entire container, eliminating the interference between the web service providing server by the update can do.

In addition, the container update method and apparatus in the virtualization system according to the present invention, by storing and managing common data shared by the containers in a base image, it is possible to minimize the resources allocated for individual containers and to efficiently utilize the resources. .

In addition, the container update method and apparatus in the virtualization system according to the present invention can reduce the cost to be paid by the client provided with the web service through the container environment.

1 is a diagram for explaining a software structure of a hypervisor-based virtualization system.
2 is a diagram for explaining a software structure of a container-based virtualization system.
3 is a diagram for describing a software structure of a container-based virtualization system for providing a web service.
4 is a block diagram showing the structure of a container update apparatus according to the present invention.
5 is a view for explaining the software structure of the container update apparatus according to the present invention.
6 is a flowchart illustrating a container update method according to the present invention.

In the following description of embodiments of the present disclosure, when it is determined that a detailed description of a related well-known configuration or function may obscure the gist of the present disclosure, the detailed description may be omitted.

As used herein, "includes," "can include." And the like refer to the existence of the corresponding function, operation, component, etc. disclosed, and do not limit one or more additional functions, operations, components, and the like. Also, in this specification, "includes." Or "have." And the like are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described in the specification, and that one or more other features or numbers, step, action, component, part, or It should be understood that they do not preclude the presence or possibility of adding these in advance.

As used herein, the singular forms "a", "an" and "the" include plural forms unless the context clearly indicates otherwise.

Hereinafter, with reference to the accompanying drawings will be described the present invention.

4 is a block diagram showing the structure of a container update apparatus according to the present invention.

According to various embodiments of the present disclosure, the container update apparatus 400 may be a device supporting a virtualization system, and in particular, a device supporting a container-based virtualization system. Accordingly, as shown in FIG. 2, the container update apparatus 400 installs a host OS on the storage unit 440 provided as hardware, and allocates resources of the storage unit 440 for each of the plurality of containers. Partitioning / allocation creates multiple containers on the host OS. The plurality of containers created on the host OS are driven using common data but operate independently.

According to various embodiments of the present disclosure, the container update apparatus 400 may create a container by virtualizing a server for providing various web services. The server created as a container may be an application server, a game server, a mail server, a media server, a database server, a proxy server, a web server, a domain server, a home server, an FTP server, and the like.

Referring to FIG. 4, the container update apparatus 400 according to the present invention includes an input unit 410, a communication unit 420, a control unit 430, and a storage unit 440.

The input unit 410 may receive various user's manipulations for controlling the operation of the container update apparatus 400. To this end, the input unit 410 may be composed of a key pad, a dome switch, a touch pad (constant voltage / capacitance), a jog wheel, a jog switch, and the like.

In various embodiments of the present disclosure, the input unit 410 may receive various user inputs for creating / modifying / controlling a container. As an example, the input unit 410 may receive a user input for requesting to create a container or changing setting information about the created container. Alternatively, the input unit 410 may receive a user input corresponding to an update request for at least one container.

The communication unit 420 performs data communication with the outside. The communication unit 420 may include a transmitter for upconverting and amplifying a frequency of a transmitted signal, a receiver for low noise amplifying and downconverting a received signal, and the like.

In various embodiments of the present disclosure, the communication unit 420 may receive various control signals for creating / modifying / controlling a container. As an example, the communication unit 420 may receive a request for creating a container or a request for changing configuration information about a container. Alternatively, the communication unit 420 may receive an update request or update package for at least one container.

In various embodiments of the present disclosure, the communication unit 420 may perform data communication with at least one client that receives and uses a service provided by a container.

The controller 430 controls each component of the container update apparatus 400 to perform the container update method according to the present invention.

The controller 430 generates a plurality of containers (virtual machines) on the host OS and controls their operations. The controller 430 may create a container by virtualizing a server for providing a web service according to a request.

More specifically, referring to FIG. 5, the controller 430 may store common data for a plurality of containers as a lower layer base image (hereinafter, referred to as a first layer base image) 520 on the host OS 510. have. Common data stored in the first hierarchical base image 520 may be web service data necessary to provide a web service, and may include, for example, Apache, Mysql, PHP, and the like.

The control unit 430 is the first layer base image 520 for the plurality of containers 541-1, ..., 541-N, 542-1, ..., 542-N which are virtualized web service providing servers. You can set the directory address for accessing common data. The plurality of containers 541-1,..., 541 -N, 542-1,..., 542 -N have a first layer via a set directory address when reference (use) of common data is required. The common image may be loaded by accessing the base image 520. The plurality of containers 541-1, ..., 541-N, 542-1, ..., 542-N directly use the loaded common data or copy them to their own storage resources (storage space). Can be used.

In addition, the controller 430 may display common data of at least one container providing the same web service among the plurality of containers on the first hierarchical base image 520 (hereinafter, referred to as a second hierarchical base image). (531, 532). Common data stored in the second layer base images 531 and 532 may be web service data necessary to provide a specific web service. In an embodiment, the common data stored in the second hierarchical base images 531 and 532 may be different from the common data stored in the first hierarchical base images 531 and 532. Alternatively, in another embodiment, the common data stored in the second hierarchical base image 531, 532 is the same as the common data stored in the first hierarchical base image 520, but with different details. Priority may be set higher than common data stored in the image 520.

In the embodiment of FIG. 5, the common data for providing the first web service is stored as the second hierarchical base image 531, and the second hierarchical base image 532 with different common data for providing the second web service is different. Stored as). In the embodiment of FIG. 5, the first web service is Jenkins and the second web service is Bugzilla, but the web service is not limited thereto.

The controller 430 is a directory for accessing the second hierarchical base image 531 of the first web service with respect to the first group container 541-1,..., 541 -N for providing the first web service. You can set the address. In addition, the controller 430 accesses the second layer base image 532 of the first web service for the second group container 542-1,..., 542 -N for providing the second web service. You can set the directory address.

The first hierarchical base image 520 and the second hierarchical base image 531 and 532 are basically set as read-only areas.

The controller 430 separately stores individual data for each of the plurality of containers 541-1,..., 541 -N, 542-1,..., 542 -N in a delta area of the container. Can be. The delta area is set as a read-write area, and as an example, individual setting of each of the containers for the common data of the first layer base image 520 and the second layer base image 531, 532. Data including the value may be stored.

In the embodiment of FIG. 5, the first group containers 541-1,..., 541 -N are common data of the first hierarchical base image 520, and a second hierarchical base image for providing a first service. The first web service may be provided to the first group clients 551-1,..., 551 -N by using the common data of 531 and individual data stored in the delta area. Similarly, the second group containers 542-1,..., 542 -N are common data of the first hierarchical base image 520 and common data of the second hierarchical base image 532 for providing a second service. And the second web service to the second group clients 552-1,..., 552 -N using individual data stored in the delta area.

In the above embodiment, the first hierarchical base image 520 is disclosed as one, but the present invention is not limited thereto. That is, a plurality of first hierarchical base images 520 may be provided according to the type and shape of a network device supported by the container updater 400.

In addition, in the above embodiment, the second hierarchical base images 531 and 532 are disclosed as two, but the present invention is not limited thereto, and the number of web services supported by the container update apparatus 400 may be smaller. A number of or more second layer base images 531, 532 may be provided.

In addition, in the above embodiment, the container update apparatus 400 is disclosed as configuring the first hierarchical base image 520 and the second hierarchical base image 531, 532 for storing common data, but the present invention is The base image of more layers may be configured according to the structure of the service supported by the container update apparatus 400.

According to various embodiments of the present disclosure, when a container update event occurs, the controller 430 updates the common data stored in the first hierarchical base image 520 and / or the second hierarchical base image 531 and 532. . The container update event may be generated by receiving a user input or update package through the input unit 410 or the communication unit 420. The container update of the controller 430 may be performed by the host OS 510. Hereinafter, an update method of the controller 430 will be described in detail according to the hierarchy of the base image in which the common data to be updated is stored.

Common data update of lower layer base images

When a container update event occurs, the controller 430 determines whether the container update event is related to common data of the first hierarchical base image 520 or common data of the second hierarchical base images 531 and 532. Can be.

If the container update event relates to common data stored in the first hierarchical base image 520, the controller 430 designates the first hierarchical base image 520 as an install directory of the update package, and sets the update package. Run In this case, the second hierarchical base image 520 may be set as a read and write area for updating. Accordingly, the common data of the first hierarchical base image 520 is updated with the common data according to the update package.

Updating Common Data in Higher Layer Base Images

If the container update event relates to common data stored in any second hierarchical base image 531 or 532 of the plurality of second hierarchical base images 531, 532, the controller 430 may control the second hierarchical base image 531 or the second hierarchical base image 531 or 532. In the embodiment of FIG. 5, that is, the base image that exists lower than 532, that is, the first hierarchical base image 520 is designated as a lower directory of a read-only area, and the corresponding second hierarchical base image 531 is provided. Or 532) as an upper directory of the read and write area. The controller 430 merges and mounts the first layer base image 520 and the second layer base image 531 or 532 to designate the mount point as an installation directory, and executes an update package. do. Accordingly, the common data of the first hierarchical base image 520 is not changed, and the common data of the second hierarchical base image 531 or 532 is updated with common data according to the update package.

Common data update for upper and lower layer base images

If the container update event is for both common data stored in the first layer base image 520 and common data stored in any second layer base image 531 or 532 of the plurality of second layer base images 531, 532. The controller 430 may first perform common data update of the above-described upper layer base image, and then perform common data update of the above-described lower layer base image.

The plurality of containers 541-1,..., 541 -N, 542-1,..., 542 -N are the first layer base image 520 and / or the second layer base updated as described above. By referring to the common data of the images 531 and 532, it operates as an updated container and can provide an updated version of the web service. If necessary, the controller 430 may reset the directory address for accessing the updated common data for the containers using the updated common data.

The storage unit 440 may store various programs for the operation of the controller 430 and various data for a plurality of containers. The program stored in the storage 440 may be executed by the controller 430.

In various embodiments of the present disclosure, the storage unit 440 may allocate resources for a host OS or a plurality of containers. The storage unit 440 allocates resources for a base image for storing common data of the plurality of containers or controls a portion of the resources allocated for the plurality of containers under the control of the controller 430. Can be allocated for

To this end, the storage unit 440 may include a flash memory type, a hard disk type, a multimedia card micro type, and a card type memory (for example, SD or XD memory). Etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPEROM), programmable read-only memory (PROM), At least one type of storage medium may include a magnetic memory, a magnetic disk, and an optical disk.

6 is a flowchart illustrating a container update method according to the present invention.

Referring to FIG. 6, the container update apparatus may be operating in a standby state after the host OS is driven in a start stage.

The container update apparatus generates a plurality of containers (601). When the container update request is received through the input unit or the communication unit, the container update apparatus may generate a plurality of containers on the host OS. The container updating apparatus may be configured to divide a resource (storage space) of the storage unit, allocate the resource for each of the plurality of containers, and store data for each container in the allocated resource.

The plurality of containers may use common data. For example, the plurality of containers may be servers that are driven using common data and operate independently. The container updating apparatus stores the same common data of a plurality of containers in a separate allocated resource region, that is, a base image, so that the plurality of containers can be shared. According to various embodiments of the present disclosure, the container update apparatus may construct a base image hierarchically according to a shared hierarchical structure of common data among a plurality of containers.

In detail, the container update apparatus stores common data of a plurality of containers in a lower layer base image. In addition, when at least some of the plurality of containers use common data, the container update apparatus stores common data for at least some of the containers in the upper layer base image. The container updating apparatus stores the individual data of each of the plurality of containers in separate resources allocated for the plurality of containers.

Thereafter, when a container update event for common data occurs (602), the container update apparatus determines whether common data to be updated is stored in a base image of one layer (603).

The container update request may occur when an update package for a container is received through the input unit or the communication unit, or may be received through the input unit or the communication unit. The container update apparatus may determine whether the common data is updated based on the received container update request.

If the common data to be updated is stored in the base image of one layer, the container updating apparatus determines whether the base image storing the common data to be updated is the lowest layer base image (604).

If the base image storing the common data is the lowest hierarchical base image (in the embodiment of FIG. 5, the first hierarchical base image 520), the container updater designates the base image as the installation directory of the update package and executes the update. (605).

If the base image storing the common data is not the lowest hierarchical base image (in the embodiment of FIG. 5, the second hierarchical base images 531 and 532), the container updating apparatus may select at least one lower hierarchical base image of the base image. A subdirectory of the read-only area is designated, and the base image is designated as an upper directory of the read and write area (606). Thereafter, the container update apparatus combines and mounts at least one lower layer base image and the base image (607), and executes the update by designating a mount point as an installation directory (608).

On the other hand, if the common data to be updated is stored in the base images of the plurality of layers, the container updating apparatus first designates the lowest layer base image among the corresponding base images as an installation directory and executes the update on the lowest layer base image (609). ). Thereafter, the container updating apparatus repeatedly performs steps 606 to 608 from the next lower layer base image of the lowest layer base image to the highest layer base image until the update of the highest layer base image among the corresponding base images is completed ( 610).

Those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential features of the present invention. In addition, the embodiments disclosed in the specification and the drawings merely present specific examples to easily explain and easily understand the contents of the present invention, and are not intended to limit the scope of the present invention. Therefore, the scope of the present invention should be construed that all changes or modifications derived based on the technical spirit of the present invention are included in the scope of the present invention in addition to the embodiments disclosed herein.

400: container update device
410: input unit
420: communication unit
430: control unit
440: storage unit

Claims (10)

As a data update method of a container updater in a virtualization system for operating a plurality of virtual machine containers,
Generating, by the container updating apparatus, a plurality of containers on a host OS;
Storing first common data for all of the plurality of containers in a first hierarchical base image;
Storing second common data for at least some of the plurality of containers in a second hierarchical base image; And
If a container update request for any common data is received, performing the update in a different manner based on which hierarchical image the common data to be updated is stored in,
And the first hierarchical base image is a lower layer than the second hierarchical base image. The method of claim 1, wherein performing the update comprises:
If the common data to be updated is stored in a lowest layer base image, performing a first update operation,
The first update operation,
Designating a base image in which the common data to be updated is stored as an installation directory; And
And updating the installation directory. The method of claim 2, wherein performing the update comprises:
If the common data to be updated is not stored in the lowest hierarchical base image, performing a second update operation,
The second update operation,
Designating at least one lower layer base image of the base image storing the common data to be updated as a read-only area and designating a base image having the common data to be updated as a read and write area;
Combining and mounting the at least one lower layer base image and the common data to be updated;
Designating the mounted point as an installation directory; And
And updating the installation directory. The method of claim 3, wherein performing the update comprises:
If the common data to be updated is stored in base images of a plurality of layers, performing the first update operation on a lowest layer base image of the base layers of the plurality of layers; And
Repeating the second update operation from a next lower layer base image of the lowest layer base image to the highest layer base image until the highest layer base image of the plurality of layer base images is updated. Container update method, characterized in that. The method of claim 1, wherein the plurality of containers,
Act as a server that provides Web services,
The first common data stored in the first hierarchical base image is
Web service data necessary for providing the web service provided by all of the plurality of containers,
The second common data stored in the second hierarchical base image is
And web service data necessary to provide a specific web service provided by the at least some of the plurality of containers. Data update device that provides a virtualization system for operating a plurality of virtual machine containers,
A storage unit which stores data for a plurality of containers created on the host OS; And
Dividing a resource of the storage unit and allocating for each of the plurality of containers, storing first common data for all of the plurality of containers in a first hierarchical base image, and storing at least some of the plurality of containers Store the second common data in the second hierarchical base image, and when a container update request for any common data is received, perform the update in a different manner based on which hierarchical image the common data to be updated is stored in Including a control unit,
And the first hierarchical base image is a lower layer than the second hierarchical base image. The method of claim 6, wherein the control unit,
If the common data to be updated is stored in the lowest hierarchical base image, the first update operation is performed.
The first update operation,
And specifying a base image in which the common data to be updated is stored as an installation directory, and updating the installation directory. The method of claim 7, wherein the control unit,
If the common data to be updated is not stored in the lowest hierarchical base image, the second update operation is performed.
The second update operation,
Designating at least one lower layer base image of the base image storing the common data to be updated as a read only area, designating a base image storing the common data to be updated as a reading and writing area, and at least one lower layer base image And combining and mounting the image and the common data to be updated, and designating the mounted point as an installation directory to execute the update to the installation directory. The method of claim 8, wherein the control unit,
When the common data to be updated is stored in base images of a plurality of layers, the first update operation is performed on the lowest layer base image among the base layers of the plurality of layers, and the base images of the plurality of layers are updated. And repeating the second update operation from a next lower layer base image of the lowest layer base image to the highest layer base image until the uppermost layer base image is updated. The method of claim 6, wherein the plurality of containers,
Act as a server that provides Web services,
The first common data stored in the first hierarchical base image is
Web service data necessary for providing the web service provided by all of the plurality of containers,
The second common data stored in the second hierarchical base image is
Container service device, characterized in that the web service data necessary to provide a specific web service provided by the at least some of the plurality of containers.

Images