Method for updating a container-based cluster, update system for a container-based cluster, update management device, and update control program

Abstract

This update management device (300) controls the updating of a container-platform cluster (100) belonging to a first container-platform identifier (cluster1). The update management device (300) comprises: a container-platform construction unit (310) that constructs a second container-platform cluster (400) belonging to a second container-platform identifier (cluster2); an application construction unit (320); a communication control policy switching command unit (330) that sets a communication control policy; and a communication container-platform changing command unit (340) that changes the first container-platform identifier (cluster1) to the second container-platform identifier (cluster2).

Description

[Technical Field]

[0001] The present invention relates to a container-based cluster update system, an update management device, and an update control program for a container-based cluster update system that utilizes virtualization technology. [Background technology]

[0002] In recent years, Kubernetes has become popular as orchestration software for integrated management of container-based clusters (Non-Patent Document 1). In addition, in relation to this, the blue-green method has been disclosed as a method for updating applications and container platforms (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “Production-grade container management infrastructure”, [online], Kubernetes, June 5, 2020, [Retrieved June 3, 2022], Internet<https: / / kubernetes.io / ja / > [Non-patent document 2] “What is Blue-Green Deployment?”, Jan. 8, 2019. [online], Red Hat, [Retrieved June 3, 2022], Internet<https: / / www.redhat.com / ja / topics / devops / what-is-blue-green-deployment> Summary of the Invention [Problem to be solved by the invention]

[0004] During blue-green updates, multiple applications may be launched at the same time, and in applications that perform processes periodically, problems may occur due to other processes being executed at the same time.

[0005] An example of an application that executes processing periodically is an application that periodically collects database values ​​(for example, every hour) and aggregates the collected results to output statistical information. With such an application, if multiple programs are executed simultaneously, the collection intervals may become inconsistent and the statistical information may become inaccurate.

[0006] The present invention has been made in consideration of these points, and its objective is to update a container platform that runs a mixture of periodic execution applications that perform processing periodically and standby-type standby applications using a blue-green update without causing any problems. [Means for solving the problem]

[0007] The method for updating a container-based cluster of the present invention is a method for updating a first container-based cluster belonging to a first container-based identifier, in which a first container-based cluster on which a standby application and a regularly-executed application are constructed, and a first application management device are constructed, characterized in that the update management device executes the steps of constructing a second container-based cluster of a second container-based cluster belonging to a second container-based identifier, and a second application management device, constructing a standby application and a regularly-executed application on the second container-based cluster, setting a communication control policy for the standby application and the regularly-executed application constructed on the second container-based cluster in a load balancer, and changing the first container-based identifier of the load balancer to the second container-based identifier. [Effects of the Invention]

[0008] According to the present invention, a container platform on which a periodic execution application that periodically executes processing and a standby application that is a standby type run together can be updated using a blue-green update without causing any problems. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing the overall configuration of a container-based cluster update system according to an embodiment of the present invention; [Figure 2] FIG. 1 is an explanatory diagram showing the initial state of an update system for a container-based cluster. [Figure 3] 10 is a flowchart illustrating the flow of update control processing executed by an update management device of the container-based cluster update system. [Figure 4] This is an explanatory diagram showing that the container infrastructure construction unit has constructed a container infrastructure cluster with a container infrastructure identifier "cluster2", and that a container infrastructure, a container infrastructure management device, and an application management device have been constructed. [Figure 5] 10 is an explanatory diagram showing that an application construction unit constructs a standby application and a periodic execution application on a container platform through an application management device. FIG. [Figure 6] An explanatory diagram showing that the communication control policy switching instruction unit instructs the application management device to set "SG3" as the communication control policy of the standby application, and that "SG3" and "SG4" are added to the communication control policies of the load balancer. [Figure 7] 10 is an explanatory diagram showing a state in which the update management device switches a communication path from a container-based cluster to a new container-based cluster. FIG. [Figure 8] 10 is an explanatory diagram showing that the container infrastructure construction unit deletes the container infrastructure, the container infrastructure management device, and the application management device having the container infrastructure identifier "cluster1." [Figure 9]FIG. 2 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the update management device. DETAILED DESCRIPTION OF THE INVENTION

[0010] Next, an embodiment of the present invention (hereinafter referred to as "the present embodiment") will be described. <Container-based cluster update system> 1 is a block diagram showing the overall configuration of a container-based cluster update system according to this embodiment. Note that FIG. 1 shows the basic configuration during operation at the time of update.

[0011] 1, the update system 500 of the container-based cluster 100 includes a container base 110 (first container base) on which a standby application 113 and a periodic execution application 111 are constructed, a container base management device 120 (first container base management device), and an application management device 130 (first application management device), and the container base cluster 100 (first container base cluster) belonging to cluster1 (first container base identifier), an update management device 300 that controls updates of the container base cluster 100, and a load balancer 200 that transfers applications to the container base cluster 100. Different communication control policies are set for the standby application 113 and the periodic execution application 111.

[0012] Furthermore, the update system 500 of the container platform cluster 100 is configured to include a container platform cluster 400. The container platform cluster 400 (second container platform cluster) includes a container platform 410 (second container platform), a container platform management device 420 (second container platform management device), and an application management device 430 (second application management device), and belongs to cluster2 (second container platform identifier).

[0013] The container-based cluster 100 is a container-based cluster currently in operation, and corresponds to the so-called blue system (old system). On the other hand, the container-based cluster 400 is a container-based cluster that is scheduled to be updated and put into operation, and corresponds to the so-called green system (new system).

[0014] [Container-based cluster (blue)] The container-based cluster 100 is configured to include a container base 110, a container-based management device 120, and an application management device .

[0015] The container platform 110 is a container platform typified by Kubernetes, and is a system composed of a group of server devices on which applications are installed. The container platform cluster 100 always belongs to one container platform identifier. The container platform 110 is assigned the container platform identifier cluster1.

[0016] The standby application 113 is a container-type application that runs on the container base 110, and is an application that waits for communication from the outside and executes processing for the received request. The standby application 113 has a communication control policy control function and can communicate only with permitted resources (load balancer 200). SG1 is assigned to the standby application 113 as the communication control policy 114.

[0017] The periodic execution application 111 is a container-type application that runs on the container base 110, and is an application that periodically executes some processing and, as necessary, communicates with the outside of the container base cluster 100. The periodic execution application 111 has a communication control policy control function and can communicate only with permitted resources (load balancer 200). SG2 is assigned to the periodic execution application 111 as the communication control policy 112.

[0018] The container infrastructure management device 120 is a device that configures and manages the operation of the container infrastructure cluster 100. The container infrastructure management device 120 always belongs to one container infrastructure identifier. The container infrastructure management device 120 is assigned cluster1 as its container infrastructure identifier 121.

[0019] The application management device 130 is a device that manages applications running on the container board 110 for the container board 110 that has a container board identifier set for itself. The application management device 130 belongs to one or more container board identifiers. In this embodiment, the application management device 130 is assigned cluster 1 as the container board identifier 131. In this embodiment, as an example, one application management device is assigned to one container board identifier, but the application management device 130 can be shared with the application management device 430 by also belonging to cluster 2, for example.

[0020] [Load Balancer] The load balancer 200 is a device that receives communications from outside the system and transfers applications to the container base 110. The load balancer 200 is configured to include a communication control policy 210, a transfer destination management unit 220, and a communication destination container base management unit 230.

[0021] The communication control policy 210 is a communication control policy control function, and the load balancer 200 can communicate only with permitted resources (standby application 113, periodic execution application 111).

[0022] The transfer destination management unit 220 manages address information of transfer destinations to applications on the container board 110 (IP (Internet Protocol) addresses of connection destinations and communication port numbers).

[0023] The destination container infrastructure management unit 230 manages container infrastructure identifier information (cluster 1), connects to the container infrastructure management device having the set container infrastructure identifier, and obtains the container infrastructure address information (IP address and communication port number).

[0024] [Update management device] The update management device 300 is a device that manages updates of the container base 110, the periodic execution application 111, and the standby application 113. The update management device 300 is configured with a container base construction unit 310, an application construction unit 320, a communication control policy switching instruction unit 330, and a communication destination container base change instruction unit 340.

[0025] The container infrastructure construction unit 310 has the function of constructing a container infrastructure 410, a container infrastructure management device 420, and an application management device 430. The container infrastructure construction unit 310 also has the function of deleting the container infrastructure 110, the container infrastructure management device 120, and the application management device 130 in the container infrastructure cluster 100 of cluster 1.

[0026] The application construction unit 320 has a function of instructing the application management device 430 to construct the standby application 411 and the periodic execution application 413. The application construction unit 320 can also control the timing at which the application management device 130 deletes the communication control policy of the periodic execution application 111 constructed in the container base 110.

[0027] The communication control policy switching instruction unit 330 has a function of setting and changing the communication control policy for the load balancer 200 and the application management devices 130 and 430. For example, the communication control policy switching instruction unit 330 sets "SG1" and "SG2" as the communication control policy for the load balancer 200. Furthermore, the communication control policy switching instruction unit 330 sets "SG1" as the communication control policy 114 of the standby application 113, and sets "SG2" as the communication control policy 112 of the periodic execution application 111, for example.

[0028] In addition, the communication control policy switching instruction unit 330 causes the application management device 430 and the load balancer 200 to set different communication control policies for the standby application 411 and the periodically executed application 413 in cluster 2, and also causes the application management device 130 and the load balancer 200 to delete the communication control policies for the standby application 113 and the periodically executed application 111 in cluster 1.

[0029] The destination container platform change instruction unit 340 has a function of issuing an instruction to change the destination container platform to the load balancer 200. For example, the destination container platform change instruction unit 340 can change the container platform identifier from "cluster1" to "cluster2", or from "cluster2" to "cluster1".

[0030] [Container-based cluster (green)] The container-based cluster 400 is configured to include a container-based cluster 410 , a container-based management device 420 , and an application management device 430 .

[0031] The container platform 410 is a container platform typified by Kubernetes, and is a system configured from a group of server devices on which applications are installed. The container platform cluster 400 always belongs to one container platform identifier. The container platform 410 is assigned cluster2 as its container platform identifier. A standby application 411 and a periodic execution application 413 are built in the container platform 410.

[0032] The standby application 411 is a container-type application that runs on the container base 410, and is an application that waits for communication from the outside and executes processing for the received request. The standby application 411 has a communication control policy control function and can communicate only with permitted resources (load balancer 200). SG3 is assigned to the standby application 411 as the communication control policy 412.

[0033] The periodic execution application 413 is a container-type application that runs on the container base 410, and is an application that periodically executes some processing and, as necessary, communicates with the outside of the container base cluster 400. The periodic execution application 413 has a communication control policy control function and can communicate only with permitted resources (load balancer 200). SG4 is assigned to the periodic execution application 413 as the communication control policy 414.

[0034] The container infrastructure management device 420 is a device that configures and manages the operation of the container infrastructure cluster 400. The container infrastructure management device 420 always belongs to one container infrastructure identifier. The container infrastructure management device 420 is assigned cluster2 as its container infrastructure identifier 421.

[0035] The application management device 430 is a device that manages applications running on the container board 410 for the container board 410 that has a container board identifier set for itself. The application management device 430 belongs to one or more container board identifiers. In this embodiment, the application management device 430 is assigned cluster 2 as the container board identifier 431. In this embodiment, as an example, one application management device is assigned to one container board identifier, but the application management device 430 can be shared with the application management device 130 by also belonging to cluster 1, for example.

[0036] <Initial state> FIG. 2 is an explanatory diagram showing the initial state of the update system for a container-based cluster.

[0037] In the update system 500 of the container base cluster 100, the container base identifier is set to "cluster1", and the container base 110, container base management device 120, and application management device 130, all of which have the container base identifier "cluster1", are running. The communication control policies of the standby application 113 and the load balancer 200 are assigned "SG1", and are in a state where communication is possible.

[0038] The communication control policies of the periodically executed application 111 and the load balancer 200 are assigned "SG2" and are in a communication enabled state. The communication destination container platform management unit 230 of the load balancer 200 has "cluster1" set as the container platform identifier, and periodically acquires address information (IP address and communication port number) for the application on the container platform 110, and the transfer destination management unit 220 manages the address information.

[0039] <Update control process> The update management device 300 of the update system 500 for the container-based cluster 100 according to this embodiment updates the container-based cluster 100 to a container-based cluster 400 .

[0040] FIG. 3 is a flowchart showing the flow of update control processing executed by the update management device of the container-based cluster update system.

[0041] First, the update management device 300 creates a destination container platform (step S1). In this case, the container platform construction unit 310 of the update management device 300 constructs a container platform 410, a container platform management device 420, and an application management device 430 with a container platform identifier of "cluster2."

[0042] FIG. 4 is an explanatory diagram showing that the container infrastructure construction unit has constructed a container infrastructure cluster with a container infrastructure identifier "cluster2", and that a container infrastructure, a container infrastructure management device, and an application management device have been constructed.

[0043] 4, a container platform 410, a container platform management device 420, and an application management device 430, each with a container platform identifier "cluster2", are constructed in the update system 500 of the container platform cluster 100. In this way, the container platform construction unit 310 of the update management device 300 creates a container platform cluster 400 with a container platform identifier "cluster2".

[0044] Returning to FIG. 3, the explanation will continue. Next, the update management device 300 instructs the application management device 430 to construct an application (step S2). In this case, the application construction unit 320 of the update management device 300 instructs the application management device 430 to construct a standby application 411 and a periodic execution application 413.

[0045] FIG. 5 is an explanatory diagram showing that the application construction unit constructs a standby application and a periodical execution application on a container platform through an application management device.

[0046] 5, in the container-based cluster 400, a standby application 411 and a periodic execution application 413 are constructed in a container base 410. Note that although the standby application 411 and the periodic execution application 413 are in an operable state, they cannot communicate with the load balancer 200 because a communication control policy has not yet been set.

[0047] Returning to FIG. 3, the explanation will continue. Next, the update management device 300 sets a communication control policy for the standby application 411 and the load balancer 200 (step S3). In this case, the communication control policy switching instruction unit 330 of the update management device 300 instructs the application management device 430 to set "SG3" as the communication control policy for the standby application 411.

[0048] Figure 6 is an explanatory diagram showing that the communication control policy switching instruction unit instructs the application management device to set "SG3" as the communication control policy of the standby application, and that "SG3" and "SG4" are added to the communication control policies of the load balancer.

[0049] As shown in FIG. 6, the application management device 430 sets "SG3" as the communication control policy of the standby application 411 on the container board 410 via the container board management device 420.

[0050] Furthermore, the communication control policy switching instruction unit 330 of the update management device 300 adds “SG3” and “SG4” to the communication control policy 210 of the load balancer 200.

[0051] In this way, "SG3" is set as the communication control policy for the standby application 411 of the container-based cluster 400. Furthermore, "SG3" and "SG4" are added to the communication control policies of the load balancer 200.

[0052] Therefore, in the update system 500 of the container-based cluster 100, the standby application 411 and the load balancer 200 are changed to a state in which communication is permitted.

[0053] Returning to FIG. 3, the explanation will continue. Next, the update management device 300 executes communication switching (step S4). In this case, the update management device 300 issues an instruction to delete the communication control policy of the container-based cluster 100 and an instruction to set the communication control policy of the container-based cluster 400.

[0054] FIG. 7 is an explanatory diagram showing a state in which the update management device switches the communication path from one container-based cluster to another container-based cluster.

[0055] 7, the communication control policy switching instruction unit 330 of the update management device 300 instructs the application management device 130 to delete "SG2", which is the communication control policy 112 of the periodically executed application 111. The application management device 130 deletes "SG2", which is the communication control policy 112 of the periodically executed application 111 on the container base 110, via the container base management device 120. The communication control policy switching instruction unit 330 of the update management device 300 also deletes "SG2" from the communication control policy 210 of the load balancer 200. As a result, the periodically executed application 111 becomes unable to communicate with the load balancer 200 and is unable to execute processing.

[0056] Furthermore, the communication control policy switching instruction unit 330 instructs the application management device 430 to set "SG4" as the communication control policy 414 of the periodically executed application 413. In this case, the application management device 430 sets "SG4" as the communication control policy 414 of the periodically executed application 413 on the container base 410 via the container base management device 420.

[0057] The destination container infrastructure change instruction unit 340 of the update management device 300 instructs the destination container infrastructure management unit 230 of the load balancer 200 to change the container infrastructure identifier from "cluster1" to "cluster2." The destination container infrastructure management unit 230 of the load balancer 200 connects to the container infrastructure management device 420 whose container infrastructure identifier is "cluster2," obtains the address information (IP address and communication port number) of the container infrastructure 410, and changes the forwarding address information of the forwarding destination management unit 220.

[0058] As a result, the update system 500 of the container-based cluster 100 is in a state in which the communication path from the load balancer 200 has been changed from the container-based cluster 100 to the container-based cluster 400 .

[0059] Returning to FIG. 3, the explanation will continue. Next, the update management device 300 deletes the migration source system (step S5). In this case, the container infrastructure construction unit 310 of the update management device 300 issues an instruction to delete the container infrastructure cluster 100, which is the migration source system that is no longer needed.

[0060] FIG. 8 is an explanatory diagram showing that the container infrastructure construction unit deletes the container infrastructure, the container infrastructure management device, and the application management device having the container infrastructure identifier "cluster1."

[0061] 8, the container infrastructure construction unit 310 of the update management device 300 deletes the container infrastructure cluster 100, which is the migration source system. In this case, the container infrastructure construction unit 310 of the update management device 300 deletes the container infrastructure 110, the container infrastructure management device 120, and the application management device 130, which have a container infrastructure identifier of "cluster1."

[0062] Furthermore, the communication control policy switching instruction unit 330 of the update management device 300 deletes "SG1" from the communication control policy 210 of the load balancer 200. In this way, when the container infrastructure construction unit 310 of the update management device 300 deletes the container infrastructure cluster 100 and the communication control policy switching instruction unit 330 of the update management device 300 deletes "SG1" from the communication control policy 210 of the load balancer 200, the processing ends.

[0063] Furthermore, in the update system 500 of the container-based cluster according to this embodiment, in step S4 of the flowchart of FIG. 3, the update management device 300 may control the timing at which the application management device 130 deletes "SG2" of the communication control policy 112 of the regularly executed application 111 constructed on the container base 110.

[0064] For example, the communication control policy switching instruction unit 330 of the update management device 300 may control the timing of issuing an instruction to the application management device 130 to delete "SG2" of the communication control policy 112 of the periodically executed application 111. This allows the update system 500 of the container-based cluster 100 to avoid deleting "SG2" of the communication control policy 112 while the periodically executed application 111 is executing a process.

[0065] For example, if the periodically executed application 111 is executed at a fixed time in a day (for example, 0 minutes past the hour), the deletion of "SG2" in the communication control policy 112 is executed to avoid that execution time. Alternatively, the application management device 130 may obtain the next execution time of the periodically executed application 111 via the application management device 130, and the application management device 130 may execute the deletion instruction to avoid that execution time.

[0066] <Hardware configuration of the update management device> The update management device 300 according to this embodiment is realized by, for example, a computer 900 having a configuration as shown in FIG.

[0067] 9 is a hardware configuration diagram showing an example of a computer that realizes the functions of the update management device. The computer 900 has a CPU (Central Processing Unit) 901, a ROM (Read Only Memory) 902, a RAM (Random Access Memory) 903, an HDD (Hard Disk Drive) 904, an input / output I / F (Interface) 905, a communication I / F 906, and a media I / F 907.

[0068] The CPU 901 operates based on a program (update control program) stored in the ROM 902 or the HDD 904, thereby realizing a container infrastructure construction unit 310, an application construction unit 320, a communication control policy switching instruction unit 330, and a communication destination container infrastructure change instruction unit 340. The ROM 902 stores a boot program executed by the CPU 901 when the computer 900 starts up, programs related to the hardware of the computer 900, and the like.

[0069] The CPU 901 controls an input device 910 such as a mouse or keyboard, and an output device 911 such as a display or printer, via an input / output I / F 905. The CPU 901 acquires data from the input device 910 via the input / output I / F 905, and outputs generated data to the output device 911. Note that a GPU (Graphics Processing Unit) or the like may be used as a processor together with the CPU 901.

[0070] The HDD 904 stores programs executed by the CPU 901 and data used by the programs. The communication I / F 906 receives data from other devices via a communication network (e.g., NW (Network) 920) and outputs the data to the CPU 901, and also transmits data generated by the CPU 901 to other devices via the communication network.

[0071] The media I / F 907 reads a program (update control program) or data stored in the recording medium 912 and outputs it to the CPU 901 via the RAM 903. The CPU 901 loads a program related to a target process from the recording medium 912 onto the RAM 903 via the media I / F 907, and executes the loaded program. The recording medium 912 is an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), a magneto-optical recording medium such as an MO (Magneto Optical Disk), a magnetic recording medium, a semiconductor memory, or the like.

[0072] For example, when a computer 900 functions as the update management device 300 of the present invention, a CPU 901 of the computer 900 executes a program loaded onto a RAM 903 to realize each function of the update management device 300. Furthermore, data stored in the RAM 903 is stored in an HDD 904. The CPU 901 reads and executes a program related to a target process from a recording medium 912. Alternatively, the CPU 901 may read a program related to a target process from another device via a communication network (NW 920).

[0073] <Effects> The following describes the effects of the update control method and the like of the container-based cluster update system 500 according to the present invention.

[0074] The method for updating a container-based cluster according to the present invention is a method for updating a container-based cluster 100 (first container-based cluster) that belongs to cluster 1 (first container-based identifier) ​​and that includes a container base 110 (first container base) on which a standby application 113 and a periodic execution application 111 are built, and an application management device 130 (first application management device). The method includes: an update management device 300 updates a container-based cluster 400 (second container-based cluster) that belongs to cluster 2 (second container base identifier); The method is characterized by executing the steps of constructing a container base 410 (second container base) and an application management device 430 (second application management device), constructing a standby application 411 and a periodic execution application 413 in the container base 410, setting different communication control policies in the load balancer 200 for the standby application 411 and the periodic execution application 413 constructed in the container base 410, and changing cluster 1 of the load balancer 200 to cluster 2.

[0075] According to the method for updating a container-based cluster of the present invention, different communication control policies are set in the load balancer 200 for the standby application 411 and the periodically executed application 413 built on the container base 410. This makes it possible to switch the communication control policies for the standby application 411 and the periodically executed application 413, so that the container base 110, on which the periodically executed application 413 and the standby application 411 run together, can be updated by blue-green update without causing any problems.

[0076] In addition, the method for updating a container-based cluster according to the present invention is characterized in that the update management device 300 further executes the steps of causing the application management device 130 to delete the communication control policy of the periodically executed application 111 built in the container base 110, the update management device 300 deleting the communication control policy of the periodically executed application 111 built in the container base 110 from the load balancer 200, the update management device 300 deleting the container base 110 and the application management device 130 of the container-based cluster 100 belonging to cluster 1, and the update management device 300 deleting the communication control policy of the standby application 113 built in the container base 110 from the load balancer 200.

[0077] In this way, according to the method for updating a container-based cluster, the communication control policy 112 of the periodically executed application 111 can be deleted, and the container base 110, the container base management device 120, and the application management device 130 can also be deleted, thereby enabling effective utilization of virtualized resources.

[0078] Furthermore, the method for updating a container-based cluster according to the present invention is characterized in that the update management device 300 further executes a step of controlling the timing at which the application management device 130 deletes the regularly executed application 111 built in the container base 110.

[0079] In this way, according to the container-based cluster update method of the present invention, the application management device 130 controls the timing of deleting the periodically executed application 111, thereby preventing the communication control policy 112 from being deleted while the periodically executed application 111 is running.

[0080] Furthermore, an update system 500 for a container-based cluster 100 according to the present invention is an update system for a container-based cluster, comprising: a container base 110 in which a standby application 113 and a periodic execution application 111 are constructed; a container base management device 120; and an application management device 130; a container base cluster 100 belonging to cluster 1; an update management device 300 that controls updates of the container base cluster 100; and a load balancer 200 that transfers applications to the container base cluster 100; The cluster 200 is characterized by comprising a container infrastructure management device 420 and an application management device 430, a container infrastructure construction unit 310 that constructs a container infrastructure cluster 400 belonging to the container infrastructure identifier of cluster 2, an application construction unit 320 that causes the container infrastructure 410 to construct a standby application 411 and a periodic execution application 413, a communication control policy switching instruction unit 330 that causes the application management device 430 and the load balancer 200 to set different communication control policies for the standby application 411 and the periodic execution application 413 of cluster 2, and a communication destination container infrastructure change instruction unit 340 that changes cluster 1 set in the load balancer 200 to cluster 2.

[0081] According to the update system 500 for the container-based cluster 100 of the present invention, different communication control policies are set in the load balancer 200 for the standby application 411 and the periodically executed application 413 built on the container base 410. This makes it possible to switch the communication control policies for the standby application 411 and the periodically executed application 413, so that the container base 110, on which the periodically executed application 413 and the standby application 411 run together, can be updated by blue-green update without causing any problems.

[0082] In addition, the update system 500 for the container-based cluster 100 of the present invention is characterized in that the container-based construction unit 310 deletes the container based 110, the container based management device 120, and the application management device 130 in the container based cluster 100 of cluster 1, and the communication control policy switching instruction unit 330 causes the application management device 130 to delete the communication control policy of the periodically executed application 111 of cluster 1, and deletes the communication control policies of the periodically executed application and standby application of cluster 1 from the load balancer 200.

[0083] In this way, according to the update system 500 for the container-based cluster 100 of the present invention, it is possible to delete the container base 110, the container-based management device 120, and the application management device 130, as well as delete the communication control policies of the regularly executed applications and standby applications of cluster 1, thereby enabling effective utilization of virtualized resources.

[0084] Furthermore, the update management device 300 according to the present invention is configured with a container base 110 in which a standby application 113 and a periodic execution application 111 are configured, a container base management device 120, and an application management device 130, and controls updates of the container base cluster 100 belonging to cluster 1, and is equipped with a container base 410, a container base management device 420, and an application management device 430, and includes a container base construction unit 310 that constructs the container base cluster 400 belonging to cluster 2. The cluster 2 is characterized by comprising an application construction unit 320 that constructs a standby application 411 and a periodic execution application 413 in a container base 410, a communication control policy switching instruction unit 330 that causes an application management device 430 and a load balancer 200 to set different communication control policies for the standby application 411 and the periodic execution application 413 of cluster 2, respectively, and a communication destination container base change instruction unit 340 that changes cluster 1 set in the load balancer 200 to cluster 2.

[0085] In this way, according to the update management device 300 of the present invention, different communication control policies are set in the load balancer 200 for the standby application 411 and the periodically executed application 413 built on the container base 410. This makes it possible to switch the communication control policies for the standby application 411 and the periodically executed application 413, so that the container base 110, on which the periodically executed application 413 and the standby application 411 run together, can be updated by blue-green update without causing any problems.

[0086] Furthermore, the update management device 300 according to the present invention is characterized in that the container base construction unit 310 deletes the container base 110, the container base management device 120, and the application management device 130 in the container base cluster 100 of cluster 1, and the communication control policy switching instruction unit 330 causes the application management device 130 to delete the communication control policy of the periodically executed application 111 of cluster 1, and deletes the communication control policies of the periodically executed application and standby application of cluster 1 from the load balancer 200.

[0087] In this way, the update management device 300 of the present invention can delete the container base 110, the container base management device 120, and the application management device 130, as well as delete the communication control policies of the regularly executed applications and standby applications of cluster 1, thereby enabling effective utilization of virtualized resources.

[0088] The present invention is not limited to the above-described embodiments, and many modifications can be made by a person skilled in the art within the technical concept of the present invention. [Explanation of symbols]

[0089] 100 container-based cluster (first container-based cluster) 110 Container Platform (First Container Platform) 111 Scheduled Applications 112 Communication Control Policy 113 Standby Application 114 Communication Control Policy 120 Container infrastructure management device (first container infrastructure management device) 121 Container Base Identifier (First Container Base Identifier) 130 Application management device (first application management device) 131 Container Base Identifier (First Container Base Identifier) 200 Load Balancer 210 Communication Control Policy 220 Transfer Management Department 230 Destination Container Infrastructure Management Unit 300 Update management device 310 Container Infrastructure Construction Department 320 Application Development Department 330 Communication control policy switching instruction unit 340 Communication destination container platform change instruction part 400 container-based cluster (second container-based cluster) 410 Container Platform (Second Container Platform) 411 Standby Application 412 Communication Control Policy 413 Scheduled Applications 414 Communication Control Policy 420 Container infrastructure management device (second container infrastructure management device) 421 Container Base Identifier (Second Container Base Identifier) 430 Application management device (second application management device) 431 Container Base Identifier (Second Container Base Identifier) 500 Update System

Claims

1. A method for updating a first container-based cluster belonging to a first container-based identifier, the method comprising: configuring a first container-based cluster in which a standby application and a periodic execution application are configured; and configuring a first application management device; The update management device constructing a second container platform of a second container platform cluster belonging to a second container platform identifier and a second application management device; A step of constructing a standby application and a periodic execution application on the second container platform; setting different communication control policies in a load balancer for the standby application and the periodic execution application built on the second container platform; changing the first container base identifier of the load balancer to the second container base identifier; How to update a container-based cluster running

2. The update management device: causing the first application management device to delete a communication control policy of the periodically executed application built on the first container platform; deleting, from the load balancer, a communication control policy of the periodically executed application built on the first container platform; deleting the first container platform and the first application management device from the container-based cluster that belongs to the first container platform identifier; deleting, from the load balancer, a communication control policy of the standby application built on the first container platform; The method of claim 1 , further comprising:

3. The update management device a step of controlling a timing for causing the first application management device to delete a communication control policy of a periodically executed application built on the first container platform; The method of claim 2, further comprising:

4. An update system for a container-based cluster, comprising: a first container platform on which a standby application and a periodic execution application are built; a first container platform management device; a first container platform cluster on which a first application management device is built and which belongs to a first container platform identifier; an update management device that controls updates of the first container platform cluster; and a load balancer that transfers applications to the first container platform cluster, different communication control policies are set for the standby application and the periodic execution application, The update management device a container infrastructure construction unit including a second container infrastructure, a second container infrastructure management device, and a second application management device, and configured to construct a second container infrastructure cluster belonging to the second container infrastructure identifier; an application construction unit that constructs a standby application and a periodic execution application on the second container platform; a communication control policy switching instruction unit that causes the second application management device and the load balancer to set different communication control policies for a standby application and a periodic execution application of the second container-based identifier; a destination container platform change instruction unit that changes the first container platform identifier set in the load balancer to the second container platform identifier; An update system for a container-based cluster, comprising:

5. The container infrastructure construction unit Deleting the first container platform, the first container platform management device, and the first application management device in the container platform cluster of the first container platform identifier; The communication control policy switching instruction unit causing the first application management device to delete a communication control policy of the periodically executed application having the first container-based identifier, and deleting communication control policies of the periodically executed application and standby application having the first container-based identifier from the load balancer; The update system for a container-based cluster according to claim 4 .

6. A first container platform on which a standby application and a periodic execution application are built, a first container platform management device, and an update management device on which the first application management device is built and which controls updates of a first container platform cluster belonging to a first container platform identifier, a container infrastructure construction unit including a second container infrastructure, a second container infrastructure management device, and a second application management device, and configured to construct a second container infrastructure cluster belonging to the second container infrastructure identifier; an application construction unit that constructs a standby application and a periodic execution application on the second container platform; a communication control policy switching instruction unit that causes the second application management device and the load balancer to set different communication control policies for a standby application and a periodic execution application of the second container-based identifier; a destination container platform change instruction unit that changes the first container platform identifier set in the load balancer to the second container platform identifier; An update management device comprising:

7. The container infrastructure construction unit Deleting the first container platform, the first container platform management device, and the first application management device in the container platform cluster of the first container platform identifier; The communication control policy switching instruction unit causing the first application management device to delete a communication control policy of the periodically executed application having the first container-based identifier, and deleting communication control policies of the periodically executed application and standby application having the first container-based identifier from the load balancer; 7. The update management device according to claim 6.

8. An update control program for causing a computer to function as the update management device according to claim 6 or 7.

Images