Resource update control system, and resource update control method

Abstract

To update a system of a client environment only when update processing of the client environment is possible.SOLUTION: A resource update control system comprises: an update-disabled reference information unit for storing update-disabled reference information for defining a reference indicating that the execution of update processing for a client environment is impossible; an update propriety determination unit for, when update of a master environment is reflected to the client environment based on difference information acquired by a difference acquiring unit, determining the propriety of the execution of the update processing for the client environment based on the difference information and the update-disabled reference information; and an update propriety information unit for storing a result relating to the propriety of the execution of the update processing for the client environment by the update propriety determination unit.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a resource update control system and a resource update control method, and is suitable for application to a resource update control system relating to a technique for controlling the update of a client environment in response to an update of a master environment, for example. [Background technology]

[0002] In recent years, the provision of services using so-called public clouds has expanded, but issues specific to public clouds have arisen in operation and maintenance work. Services using public clouds require different approaches to system monitoring, troubleshooting, security measures, etc. than services using on-premise or private clouds, which places a burden on operation and maintenance work. To reduce the burden of such operation and maintenance work, there is a demand for technologies that support the efficiency of operation and maintenance work, such as automating client environment updates.

[0003] Patent Document 1 discloses a technique for efficiently updating systems in a multiple client environment without cumbersome work. Specifically, Patent Document 1 discloses a technique in which a difference update command issuing unit on the web server group side generates a difference update command (function) according to state variables stored in a state storage unit and received events. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-318722 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the technique disclosed in Patent Document 1 does not take into account cases where updating of the client environment is not possible, and therefore there is a possibility that an update that the system cannot accept may be performed.

[0006] The present invention has been made in consideration of the above points, and aims to propose a resource update control system and a resource update control method that can update the system of a client environment only when update processing of the client environment is possible. [Means for solving the problem]

[0007] In order to solve this problem, the present invention provides a resource update control system that controls the execution of update processing for at least one client environment in accordance with an update of a master environment, and includes a difference acquisition unit that acquires difference information indicating differences between resource setting items between the master environment and the client environment, an update impossibility criteria information unit that stores update impossibility criteria information that defines criteria for which the update processing cannot be executed for the client environment, an update feasibility determination unit that, when reflecting an update of the master environment in the client environment based on the difference information, determines whether the update processing for the client environment can be executed based on the difference information and the update impossibility criteria information, and an update feasibility information unit that stores the result of the update feasibility determination unit regarding whether the update processing for the client environment can be executed.

[0008] In the present application, a resource update control method in which a difference acquisition unit controls the execution of an update process for at least one client environment in accordance with an update of a master environment includes a difference acquisition step in which difference information indicating differences between resource setting items of the master environment and the client environment; an update impossibility criteria information storage step in which an update impossibility criteria information unit stores update impossibility criteria information defining criteria for which the update process cannot be executed for the client environment; an update feasibility determination step in which, when reflecting an update of the master environment in the client environment based on the difference information, an update feasibility determination step in which an update feasibility information unit determines whether the update process for the client environment can be executed based on the difference information and the update impossibility criteria information; and an update feasibility information storage step in which the update feasibility information unit stores a result regarding whether the update process for the client environment can be executed by the update feasibility determination unit. [Effects of the Invention]

[0009] According to the present invention, it is possible to realize a resource update control system and a resource update control method that can update a system in a client environment only when update processing of the client environment is possible. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram illustrating an example of a hardware configuration of a resource update control system in a client environment according to a first embodiment. [Figure 2] 1 is a block diagram illustrating an example of a functional configuration of a resource update control system in a client environment according to a first embodiment. [Figure 3] 3 is a diagram showing an example of master environment information stored in a master environment information database shown in FIG. 2; FIG. [Figure 4] 3 is a diagram illustrating an example of client environment information stored in a client environment information database illustrated in FIG. 2. FIG. [Figure 5] 3 is a diagram showing an example of difference information stored in the difference information database shown in FIG. 2; FIG. [Figure 6]FIG. 10 is a diagram illustrating an example of update disabling criteria information of the resource update control system in the client environment of the first embodiment. [Figure 7] 3 is a diagram showing an example of update propriety information stored in the update propriety information database shown in FIG. 2. FIG. [Figure 8] FIG. 10 is a diagram showing an example of an update start instruction screen displayed on the output unit. [Figure 9] FIG. 10 is a diagram illustrating an example of a client environment selection screen displayed on an output unit. [Figure 10] 10 is a flowchart illustrating an example of a procedure for a system update control process. [Figure 11] 11 is a flowchart showing an example of detailed steps of a difference information acquisition process shown in FIG. 10. [Figure 12A] 11 is a flowchart illustrating an example of detailed steps of an update propriety information acquisition process shown in FIG. 10. [Figure 12B] 12B is a flowchart showing an example of detailed procedures following the update propriety information acquisition process shown in FIG. 12A. [Figure 13] 10 is a flowchart illustrating an example of a procedure for updating a client environment. [Figure 14] 10 is a flowchart illustrating an example of a detailed procedure of difference information acquisition processing according to the second embodiment. [Figure 15A] 10 is a flowchart illustrating an example of a detailed procedure of an update propriety information acquisition process according to the second embodiment. [Figure 15B] 15B is a flowchart showing an example of detailed procedures following the update propriety information acquisition process shown in FIG. 15A. [Figure 16] 10 is a flowchart illustrating an example of a procedure for updating a client environment according to the second embodiment. [Figure 17] 11 is a flowchart illustrating an example of a procedure for a system update control process according to the third embodiment. [Figure 18] 10 is a flowchart illustrating an example of a detailed procedure of difference information acquisition processing according to the second embodiment. [Figure 19A]13 is a flowchart illustrating an example of a detailed procedure of an update propriety information acquisition process according to the third embodiment. [Figure 19B] 19B is a flowchart showing an example of detailed procedures following the update propriety information acquisition process shown in FIG. 19A. [Figure 20] 13 is a flowchart illustrating an example of a procedure for updating a client environment according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of the present invention will be described in detail below with reference to the drawings.

[0012] (1) First embodiment In the first embodiment, after a user issues an instruction to start the update process of a client environment, the update items of each resource are identified, the resource update control system determines whether the update process of each client environment can be executed, and from the client environments determined to be capable of the update process, the user selects the client environment that he / she wishes to update, and executes the update process.

[0013] Fig. 1 is a block diagram showing an example of the hardware configuration of a resource update control system 100 according to the first embodiment. Note that the hardware configuration shown in Fig. 1 is merely an example, and other hardware configurations may be used. Note that, for example, multiple client environments (or server environments) may be implemented on one server.

[0014] The resource update control system 100 includes an update control system server 110, a master information collection system server 120, and a client update system server 130. The update control system server 110, the master information collection system server 120, and the client update system server 130 are connected to each other via a network 160.

[0015] A master environment server 140 and at least one client environment server 150 are connected to the resource update control system 100 via a network 160. In this embodiment, a client A environment server 1501-1 and a client B environment server 150-2 are exemplified as the client environment servers 150. When there is no need to particularly distinguish between the two, they are also collectively referred to as the client environment servers 150.

[0016] The update control system server 110 is a server for realizing the environment of the update system 210 described below. The update control system server 110 has an input unit 111, a communication unit 112, a control unit 113, an output unit 114, and a storage unit 115.

[0017] The input unit 111 is an input device for issuing an instruction to start execution of update processing of a client environment and for selecting a client environment for which update processing is to be executed.

[0018] The communication unit 112 is connected to a network 160 such as the Internet, receives information sent from the master information collection system server 120 and the client update system server 130, and sends information to the client update system server 130.

[0019] The control unit 113 controls the execution of the program and also controls the entire update control system server 110. The control unit 113 controls input processing by the input unit 111, communication processing by the communication unit 112, display processing of the output screen by the output unit 114, and storage processing by the storage unit 115.

[0020] The output unit 114 is a device that outputs information, such as an image display device (display), and displays, for example, a screen for inputting an instruction to start executing the update process, or a screen for selecting the client environment for executing the update.

[0021] The storage unit 115 is configured with, for example, a semiconductor storage device, a magnetic disk device, a ROM (Read Only Memory) which is a nonvolatile storage element, a RAM (Random Access Memory) which is a volatile storage element, or a combination thereof, and includes a nonvolatile storage area and a volatile storage area. The storage unit 115 stores programs executed by the control unit 113, data referenced during processing by the control unit 113, data output during processing by the control unit 113, etc.

[0022] The master information collection system server 120 is a server for realizing the environment of a master information collection system (corresponding to the master information collection system 220 in FIG. 2) described later. The master information collection system server 120 includes a communication unit 121 and a control unit 122.

[0023] The communication unit 121 connects to a network 160 such as the Internet, receives information transmitted from the master environment server 140 , and transmits the information to the update control system server 110 .

[0024] The control unit 122 controls the entire master information collection system server 120. The control unit 122 also controls communication processing by the communication unit 121.

[0025] The client update system server 130 is a server for realizing the environment of a client update control system (corresponding to the client update system 230 in FIG. 2) described later. The client update system server 130 includes a communication unit 131 and a control unit 132.

[0026] The communication unit 131 is connected to a network 160 such as the Internet, receives information sent from the update control system server 110 and the client environment server 150, and sends information to the update control system server 110 and the client environment server 150.

[0027] The control unit 132 controls the client update system server 130. The control unit 132 controls the communication processing by the communication unit 131.

[0028] The master environment server 140 is a server that constructs the master environment 240. The master environment server 140 includes a control unit 141 and a communication unit 142.

[0029] The control unit 141 controls the master environment server 140. The control unit 141 controls communication processing by the communication unit 142.

[0030] The communication unit 142 connects to a network 160 such as the Internet and transmits information to the master information collection system server 120 .

[0031] The client environment server 150 is a server that constructs the client environment 250. The client environment server 150 includes a communication unit 151 and a control unit 152.

[0032] The communication unit 151 is connected to a network 160 such as the Internet, receives information transmitted from the client update system server 130, and transmits information to the client update system server 130.

[0033] The control unit 152 controls the client environment server 150. The control unit 152 controls the communication processing by the communication unit 151.

[0034] FIG. 2 is a block diagram showing an example of the software configuration of the resource update control system 100 in a client environment.

[0035] The update system 210 controls the update processing of at least one client environment in response to an update of the master environment. The update system 210 includes an output unit 114, a master environment information collection unit 212, a master environment information DB 213, a client environment information collection unit 214, a client environment information DB 215, a difference acquisition unit 216, a difference information DB 217, an update feasibility determination unit 218, an update disapproval criteria information DB 219, an update feasibility information DB 2110, and an update instruction unit 2111.

[0036] The master environment information collection unit 212 acquires configuration information of the system on the master environment 240. The master environment information DB 213 stores master environment information 510, which is information related to the master environment.

[0037] The update system 210 has a master environment information collection unit 212 that acquires system configuration information of the master environment 240, a master environment information DB 213 as an example of a master environment information unit that stores the system configuration information of the master environment 240, a client environment information collection unit 214 that acquires the system configuration of the client environment 250, and a client environment information DB 215 as an example of a client environment information unit that stores the system configuration information of the client environment 250.

[0038] The client environment information collection unit 214 acquires configuration information of the system on the client environment information collection unit 214. The client environment information DB 215 stores client environment information 610.

[0039] The difference acquisition unit 216 acquires difference information 710 as the difference between the system on the master environment 240 and the system on the client environment 250. The difference information 710 includes, for example, a record of difference information for each time the difference was acquired. The difference acquisition unit 216 acquires difference information that indicates the difference between the setting items of resources in the master environment 240 and the client environment. The difference information DB 217 stores the difference information 710.

[0040] When reflecting updates to the master environment 240 in the client environment 250 based on the difference information 710, the update possibility determination unit 218 determines whether or not update processing for the client environment 250 can be executed based on the difference information 710 and the update impossibility criteria information 810.

[0041] The update impossibility criteria information DB219 is an example of an update impossibility criteria information section, and stores update impossibility criteria information 810 that defines criteria under which update processing cannot be performed on a client environment. Note that the update impossibility criteria information 810 may instead define criteria under which update processing can be performed on a client environment.

[0042] The update propriety information DB 2110 is an example of an update propriety information section, and stores update propriety information 910 indicating the result of the update propriety determination section 218 as to whether or not update processing for the client environment 250 can be executed.

[0043] The update instruction unit 2111 uses the difference information 710 to send an instruction to update the client environment 250, for example, to the update implementation unit 232. Based on the difference information 710, the update instruction unit 2111 sends an instruction to update the resource settings of the client environment 250, or to add a resource, or to delete a resource.

[0044] The master information collection system 220 includes a master environment information transmission unit 221. The master environment information transmission unit 221 acquires system configuration information on the master environment 240.

[0045] The client update system 230 includes an environment information transmission unit 231 and an update implementation unit 232. The environment information transmission unit 231 acquires configuration information of the client environment 250. The update implementation unit 232 implements update processing for the client environment 250.

[0046] The update possibility determination unit 218 determines whether or not the update process of the client environment 250 can be executed (hereinafter, may be collectively referred to as "update possibility") based on the difference information 710 and the update impossibility criteria information 810 described above.

[0047] Specifically, the update possibility determination unit 218 compares the difference information 710 with the update impossibility criteria information 810, and determines whether the setting item (e.g., resource version) where the difference occurred for a resource with a difference in the difference information 710 and the difference content in the setting item (the difference between the pre-update setting value 712 and the post-update setting value 713 in Figure 5 described later) satisfy the target item (target item 811 in Figure 6 described later) that is subject to the condition under which update processing for the client environment 250 is impossible in the update impossibility criteria information 810 (e.g., the condition that version 10.0 is not allowed) and the change in the setting value (updating version 9.1 to 10.0) that makes update processing for the client environment 250 impossible for the setting item (e.g., the "version" of update item 711 in Figure 5 described later), and if the change in the setting value that makes the update processing impossible is satisfied, it determines that update processing for the relevant client environment 250 is impossible based on the client ID, which is an example of information that can uniquely identify the client environment 250 and is included in the difference information 710.

[0048] Furthermore, the update possibility determination unit 218 determines whether the client environment 250 can be updated based on the client environment information 610 and the difference information 710 .

[0049] The update feasibility determination unit 218 implements a virtual resource in a specific update control system (not shown) that can attempt update work, and if the update work of the above update process on the virtual resource fails as a result of attempting to do so, it stores the details of the update work as update impossibility criteria information 810 in the update impossibility criteria information DB 219, which is an example of an update impossibility criteria information unit.

[0050] Fig. 3 is a diagram showing an example of the master environment information 510 stored in the master environment information DB 213 shown in Fig. 2. The master environment information 510 is information indicating the configuration of a system built in the master environment 240.

[0051] The master environment information 510 includes, for example, a resource name 511 that can uniquely identify a resource in the master environment 240 , a service name 512 of the resource in the master environment 240 , and a setting item 513 of the resource in the master environment 240 .

[0052] The setting item 513 manages the item names and their setting values ​​that can be set in the resources of the master environment 240. For example, if the setting item 513 is a setting for a virtual server in a case where the master environment 240 is configured by a virtual server, the setting item 513 may manage various items such as settings for a CPU (Central Processing Unit), memory, etc., as well as software and applications to be implemented in the virtual server.

[0053] Fig. 4 is a diagram showing an example of the client environment information 610 stored in the client environment information DB 215 shown in Fig. 2. The client environment information 610 is information indicating the configuration of a system built in the client environment 250.

[0054] The client environment information 610 includes, for example, a client ID 611 that can uniquely identify the client environment 250, a resource name 511 that can uniquely identify the resource of the client environment 250, a service name 512 of the resource of the client environment 250, and a setting item 513 of the resource of the client environment 250.

[0055] The setting item 513 manages the item names and setting values ​​that can be set in the resources of the client environment 250. For example, if the setting item 513 is a setting for a virtual server in a case where the client environment 250 is configured by a virtual server, the setting item 513 may manage various items such as the settings for the CPU, memory, etc., as well as software and applications to be implemented in the virtual server.

[0056] Fig. 5 is a diagram showing an example of difference information 710 stored in the difference information DB 217 shown in Fig. 2. The difference information 710 is information indicating the differences in system configuration between the master environment information 510 and the client environment information 610.

[0057] The difference information 710 includes, for example, a client ID 611 as an example of information that can uniquely identify the client environment 250 that is compared with the master environment 240, a resource name 511 as an example of information that can uniquely identify a resource (e.g., "RDS") that has a difference in a setting item between the master environment 240 and the client environment 250, a service name 512 of a service as an example of a setting item in which a difference has occurred in the resource with a difference, an updated item 711 as an example of a setting item in which a difference has occurred in the resource with a difference, and information on the difference in the setting item (a pre-update setting value 712 that indicates the setting value in the client environment information 610 for the updated item 711, and a post-update setting value 713 that indicates the setting value in the master environment information 510 for the updated item 711).

[0058] 6 is a diagram showing an example of update disallowance criteria information of the client environment resource update control system 100 of the first embodiment. The update disallowance criteria information 810 is information that is compared with the difference information 710 to determine whether or not the client environment 250 can be updated. Hereinafter, this determination is also collectively referred to as "update allowance determination."

[0059] For example, if the difference information 710 created from the difference between the client environment 250 and the master environment 240 for a certain resource item (corresponding to the "target item 811" described below) satisfies the criteria value conditions represented by the non-update criteria information 810, it is determined that the resource item of the client environment 250 cannot be updated (hereinafter also referred to as "non-updateable").

[0060] The update disabling criteria information 810 includes, for example, a service name 512 of a resource for which update processing on the client environment 250 may be disabled, a target item 811 as an example of a target item subject to a condition (e.g., version 10.0 is not allowed) under which update processing on the client environment 250 is disabled in the service (e.g., "RDS") of the service name 512, and differences in setting values ​​for the target item 811 that disable update processing on the client environment 250 (e.g., a pre-update criteria value 812 indicating the criteria value that the update item must satisfy before the update, and a post-update criteria value 813 indicating the criteria value that the update item must satisfy after the update if the update is disabled). Note that the pre-update criteria value 812 and the post-update criteria value 813 may be set to a specific value in advance, or multiple values ​​may be set, or a range indicated by multiple values ​​may be set.

[0061] Fig. 7 is a diagram showing an example of the update possibility information 910 stored in the update possibility information DB 2110 shown in Fig. 2. The update possibility information 910 is information indicating whether or not the client environment 250 can be updated. The update possibility information 910 includes, for example, a client ID 611 that can uniquely identify the client environment, and an update possibility 911 that indicates whether or not an update is possible.

[0062] 8 is a diagram showing an example of an update start instruction screen 310 displayed on the output unit 114. The update start instruction screen 310 is a screen that the user operates when starting the update process of the client environment, for example. The update start instruction screen 310 displays, for example, in the center, the message "Do you want to update the client environment?"

[0063] The update start instruction screen 310 has an execute button 311 that the user operates to start the execution of the update process of the client environment 250. When the execute button 311 is operated, an update start instruction, which will be described later, is output, and the following client environment selection screen 410 is displayed.

[0064] 9 is a diagram showing an example of a client environment selection screen 410 displayed on the output unit 114. The client environment selection screen 410 has, for example, a check box 411 for selecting a client environment 250 to which the client environment server 150 to be updated belongs from among the multiple client environment servers 150, and an update button 412 for starting execution of a system update control process (see FIG. 10 described later) to be described later.

[0065] The resource update control system 100 of the client environment 250 according to the first embodiment has the above-described configuration, and next, with reference to Figures 1 to 9, a system update control process will be described as an example of the operation of the resource update control system 100. To give an overview of the system update control process, the system update control process includes the following resource update control method.

[0066] The resource update control method is a method in which the difference acquisition unit 216 controls update processing of at least one client environment 250 in accordance with an update of the master environment 240, and includes: a difference acquisition step in which an update impossibility criteria information DB219, as an example of an update impossibility criteria information unit, stores update impossibility criteria information 810 that defines criteria for why the update processing cannot be executed on the client environment 250; an update feasibility determination step in which, when reflecting an update of the master environment 240 in the client environment 250 based on the difference information 710, the update feasibility determination unit 218 determines whether or not the update processing can be executed on the client environment 250 based on the difference information 710 and the update impossibility criteria information 810; and an update feasibility information storage step in which an update feasibility information DB2110, as an example of an update feasibility information unit, stores a result regarding whether or not the update processing on the client environment 250 by the update feasibility determination unit 218 can be executed.

[0067] 10 is a flowchart showing an example of the procedure for the system update control process. The system update control process shows an example of the procedure from the start of the update process of the resource update control system 100 of the client environment 250 to the output of the client environment selection screen 410.

[0068] As a prerequisite for executing the system update control process, the environment information transmission unit 231 acquires client environment information 610 from the client environment 250 and outputs it to the client environment information collection unit 214. The client environment information collection unit 214 registers the input client environment information 610 in the client environment information DB 215. Note that this process is executed for each of the multiple client environment servers 150 included in the client environment 250.

[0069] Furthermore, based on the above premise, update non-operation criterion information 810 is registered in update non-operation criterion information DB 219. The update non-operation criterion information 810 may be created manually by a user or automatically using a computer. Alternatively, the update non-operation criterion information 810 may be generated from information on the Internet using, for example, artificial intelligence (AI).

[0070] 8, the user first operates the execute button 311 on the update start instruction screen 310, thereby inputting the update start instruction 201 to the master environment information collection unit 212. Then, in step S101, the master environment information collection unit 212 acquires the master environment information 510 from the master environment information transmission unit 221 and registers it in the master environment information DB 213.

[0071] In step S 102 , the difference acquisition unit 216 acquires the master environment information 510 from the master environment information DB 213 .

[0072] In step S103, the difference acquisition unit 216 repeatedly executes step S104, difference information acquisition processing (step S105), and update availability information acquisition processing (step S106) as described below for each of the multiple client environment servers 150 included in the client environment 250.

[0073] First, in step S104, the difference acquisition unit 216 acquires the client environment information 610 from the client environment information DB 215. Note that in steps S102 to S104, the difference acquisition unit 216 may first acquire the client environment information 610 and then acquire the master environment information 510.

[0074] In step S105, the difference acquisition unit 216 executes a difference information acquisition process to acquire the difference information 710. Details of the difference information acquisition process will be described later.

[0075] In step S106, the difference acquisition unit 216 executes an update possibility information acquisition process to acquire the update possibility information 910. Details of the update possibility information acquisition process will be described later.

[0076] In step S107, the output unit 114 outputs the client environment selection screen 410 shown in FIG. 9 based on the update possibility information 910 stored in the update possibility information DB 2110.

[0077] In the client environment selection screen 410, the check box 411 displays only records of rows of the client ID 611 where the update possibility 911 is "possible" in the update possibility information 910. The records of each row correspond to each client environment server 150. This allows the user to select the client environment server 150 that should execute the update process in the client environment 250.

[0078] Fig. 11 is a flowchart showing an example of detailed procedures of the difference information acquisition process (step S105) shown in Fig. 10. In step S201, the difference acquisition unit 216 repeatedly executes steps S202 to S205 as follows for each record of the master environment information 510 stored in the master environment information DB 213.

[0079] In step S202, the difference acquisition unit 216 compares the resource name 511 of the master environment information 510 shown in FIG. 3 with the resource name 511 of the client environment information 610 shown in FIG. 4, and determines whether there are any setting items in the client environment 250 that have changed when compared with the master environment 240 for the setting items of the resource indicated by the resource name 511.

[0080] If there are any setting items that have been changed (step S202: Yes), the difference acquisition unit 216 executes step S203, but if there are no changes (step S202: No), the difference acquisition unit 216 repeats the execution from step S201 for the next master environment information 510.

[0081] In step S203, the difference acquisition unit 216 repeatedly executes steps S204 and S205 described below for each setting item of the resource that has been changed and that has been determined in step S202.

[0082] In step S204, the difference acquisition unit 216 acquires difference information 710 for the setting item 513 of the resource corresponding to the changed resource name 511 from the master environment information 510 and the client environment information 610. The updated item 711 shown in Fig. 5 corresponds to the updated item among the setting items 513 of the updated resource name 511 in Fig. 4. Also in Fig. 5, the setting value before update 712 of the updated item 711 indicates the setting value of the item in the client environment information 610, and the setting value after update 713 indicates the setting value of the item in the master environment information 510. This makes it possible to determine the difference between the system built on the master environment 240 and the system built on the client environment 250.

[0083] In step S205, the difference acquisition unit 216 registers the difference information 710 acquired in step S205 in the difference information DB 217.

[0084] Figures 12A and 12B are flowcharts each showing an example of detailed steps of the update propriety information acquisition process (step S106) shown in Figure 10. The flowchart shown in Figure 12B is a continuation of the flowchart shown in Figure 12A.

[0085] In step S301, the update permission determination unit 218 repeatedly executes steps S302 to S313 for each record of the difference information 710 in the difference information DB 217.

[0086] In step S302, the update possibility determination unit 218 acquires difference information 710 from the difference information DB 217. In step S303, the update possibility determination unit 218 repeatedly executes steps S304 to S308 for each record of update impossibility criterion information 810 stored in the update impossibility criterion information DB 219.

[0087] First, in step S304, the update possibility determination unit 218 registers the update possibility criterion information 810 in the update possibility criterion information DB 219. Next, in step S305, the update possibility determination unit 218 determines whether the service name 512 in the difference information 710 matches the service name 512 in the update possibility criterion information 810. If they do not match (step S305: No), the update possibility determination unit 218 repeats the process from step S304 for the next update possibility criterion information 810, but if they match (step S305: Yes), the update possibility determination unit 218 executes step S306.

[0088] In step S306, the update possibility determination unit 218 determines whether the update item 711 in the difference information 710 matches the target item 811 in the update impossibility criteria information 810. If they do not match (step S306: No), the update possibility determination unit 218 repeats the process from step S304 for the next update impossibility criteria information 810, but if they match (step S306: Yes), it executes step S307.

[0089] In step S307, the update possibility determination unit 218 determines whether the pre-update setting value 712 of the difference information 710 satisfies the pre-update reference value 812 of the update impossibility reference information 810. If the pre-update reference value 812 is not satisfied (step S307: No), the update possibility determination unit 218 repeatedly executes step S304 for the next update impossibility reference information 810, whereas if the pre-update reference value 812 is satisfied (step S307: Yes), the update possibility determination unit 218 executes step S308.

[0090] In step S308, the update possibility determination unit 218 determines whether the post-update setting value 713 of the difference information 710 satisfies the post-update reference value 813 of the update impossibility criterion information 810. If the post-update reference value 813 is not satisfied (step S308: No), the update possibility determination unit 218 repeatedly executes step S304 for the next update impossibility criterion information 810, whereas if the post-update reference value 813 is satisfied (step S308: Yes), the update possibility determination unit 218 executes step S315, which will be described later. By performing steps S305 to S308 as described above, the update possibility determination unit 218 can determine whether the client environment 250 cannot be updated (is not updateable) based on the update impossibility criterion information 810.

[0091] In step S309, the update possibility determination unit 218 acquires client environment information 610 from the client environment information DB 215. In step S310, the update possibility determination unit 218 implements the resource for which it is determining whether it can be updated based on the service name 512 and setting item 513 of the client environment information 610 acquired in step S309, in the update control system environment, for example, in the trial environment. The update possibility determination unit 218 acquires the resource name 511 of the resource for which it is determining whether it can be updated from the difference information 710, and implements, for example, the resource having the same resource name 511 in the client environment information 610 in the setting item 513.

[0092] In step S311, the update possibility determination unit 218 updates the setting item 513 of the resource implemented in step S310 using the update item 711 and the post-update setting value 713 of the difference information 710, and then erases the resource implemented in step S310, for example, in a trial environment.

[0093] Step S312: The update possibility determination unit 218 determines whether the resource update performed in step S311 was successful. If the resource update was successful (step S312: Yes), the update possibility determination unit 218 repeatedly executes step S301 and subsequent steps for the next difference information 710, whereas if the resource update was not successful (step S312: No), the update possibility determination unit 218 executes step S315.

[0094] As described above, by steps S309 to S312, the update permission determining unit 218 can determine whether or not an update is possible even for update content that is not listed in the update disallowance criteria information 810.

[0095] In step S313, the update possibility determination unit 218 registers the contents of the difference information 710 as update immobilization criteria information 810 in the update immobilization criteria information DB 219. At this time, the update item 711, pre-update setting value 712, and post-update setting value 713 of the difference information are registered as the target item 811, pre-update criteria value 812, and post-update criteria value 813 of the update immobilization criteria information 810. This allows the update system 210 to automatically add the update immobilization criteria information 810 to the update immobilization criteria information DB 219.

[0096] In step S314, the update permission determination unit 218 determines that the client environment 250 corresponding to the client ID 611 is updatable, and registers the update permission information 910 in the update permission information DB 2110. At this time, the update permission 911 is registered as "permitted".

[0097] In step S315, the update permission determination unit 218 determines that the client environment 250 corresponding to the client ID 611 is not updatable, and registers the update permission information 910 in the update permission information DB 2110. At this time, the update permission 911 is registered as "not possible".

[0098] Fig. 13 is a flowchart showing an example of the procedure for updating the client environment 250. In preparation for updating the client environment 250, the user selects the client environment 250 for which the update process is to be performed from the client environment selection screen 410 shown in Fig. 9. The user selects the client environment 250 by checking a check box 411 displayed based on the record in the same row as the client ID 611 corresponding to the client environment server 150 of the client environment 250 for which the update process is to be performed, and then presses an update button 412, thereby starting each procedure in the flowchart shown in Fig. 13.

[0099] In step S401, the update instruction unit 2111 repeatedly executes steps S402 and S403 for each client environment server 150 of the client environment 250 selected on the client environment selection screen 410.

[0100] In step S402, the update instruction unit 2111 acquires the difference information 710 of the client environment 250 from the difference information DB 217, and transmits it to the update implementation unit 232. The update instruction unit 2111 acquires, as the difference information 710, all information that matches the client ID 611 of the client environment 250 to be updated.

[0101] In step S403, the update implementation unit 232 updates all of the client environment servers 150 in the client environment 250 based on the difference information 710 sent by the update instruction unit 2111. As part of the update process, the update implementation unit 232 changes the setting value of the update item 711 to the post-update setting value 713 for the resource corresponding to the resource name 511 in the difference information 710. Note that the contents of the difference information 710 may be reflected in the client environment 250 in any order. For example, they may be reflected in record order, or may be reflected simultaneously by resource name, or may all be reflected simultaneously.

[0102] According to this embodiment, the resource update control system 100 of the client environment 250 can determine whether or not an update is possible on the client environment 250. Furthermore, since the update process is performed only on the differences between the system on the client environment 250 and the system on the master environment 240, the update process can be performed in a short time.

[0103] In this embodiment, the update may be performed by determining whether or not an update is possible for each resource in the client environment 250. In this case, the update possibility determination unit 218 may determine whether or not each resource can be updated, and the update possibility information 910 may record whether or not each resource can be updated.

[0104] Furthermore, on the client environment selection screen 410, it may be possible to select whether to perform an update for each client environment 250, or to select whether to perform an update for each resource of the client environment 250.

[0105] (2) Second embodiment The resource update control system according to the second embodiment has the same configuration and operation as the resource update control system 100 according to the first embodiment, so a description of the similar configuration and operation will be omitted and the following description will focus on the differences.

[0106] Unlike the first embodiment, the second embodiment assumes a case where a task of adding a new resource occurs during an update task of the client environment 250. In the following description, only the points that are different from the first embodiment will be mentioned with reference to Figs. 1 to 13.

[0107] Fig. 14 is a flowchart showing an example of detailed procedures of the difference information acquisition process (step S105) in the second embodiment. The flowchart shown in Fig. 14 is almost the same as the flowchart shown in Fig. 10. Step S201 is the same as step S201 in the first embodiment, and therefore its description will be omitted.

[0108] In step S202A, instead of determining whether there are any setting items that have been changed as in the first embodiment, the difference acquisition unit 216 assumes that updates have occurred in all item names of the setting items 513 for the newly added resource name 511, and proceeds to step S203. Explanation of step S203 will be omitted.

[0109] In step S204A, the difference acquisition unit 216 acquires difference information 710 for the setting item 513 of the newly added resource name 511 from the master environment information 510. Furthermore, the setting value before update 712 of the update item 711 is set to be blank, and the setting value of the item in the master environment information 510 is set to the setting value after update 713. Explanation of step S205 will be omitted.

[0110] 15A and 15B are flowcharts showing an example of detailed steps of the update possibility information acquisition process (see step S106 in FIG. 10) in the second embodiment. The flowchart shown in FIG. 15B is a continuation of the flowchart shown in FIG. 15A. The flowcharts shown in FIGS. 15A and 15B are almost the same as the flowcharts shown in FIGS. 12A and 12B, respectively. Step S301 is the same as step S301 in the first embodiment, and therefore its description will be omitted.

[0111] In step S302A, the update possibility determination unit 218 acquires the difference information 710 from the difference information DB 217. At that time, the update possibility determination unit 218 determines whether the pre-update setting value 712 of the difference information 710 is blank. If the pre-update setting value 712 is blank, the update possibility determination unit 218 executes step S301 described above for the next record in the difference information 710, and if the pre-update setting value 712 is not blank, the update possibility determination unit 218 executes step S303. Steps S303 to S315 are the same as steps S303 to S315 shown in Figures 12A and 12B.

[0112] Fig. 16 is a flowchart showing an example of the procedure for updating the client environment 250 in the second embodiment. The flowchart shown in Fig. 16 is almost the same as the flowchart shown in Fig. 13, so a description of the same procedure will be omitted. Therefore, a description of step S401 and step S402 will be omitted.

[0113] In step S403A, the update implementation unit 232 updates the client environment 250 based on the difference information 710 etc. sent by the update instruction unit 2111. At that time, for any difference information 710 where only the pre-update setting value 712 is blank, the update implementation unit 232 newly implements a resource in the client environment 250 for each resource name 511, and accordingly sets the contents of the setting item 513 to the contents of the update item 711 and the post-update setting value 713.

[0114] According to the second embodiment, when updating the client environment 250, it is possible to implement new resources.

[0115] (3) Third embodiment The resource update control system according to the third embodiment has the same configuration and operation as the resource update control system 100 according to the first embodiment and the resource update control system according to the second embodiment, so we will omit the explanation of the similar configuration and operation and focus on the differences below.

[0116] The third embodiment differs from the first and second embodiments in that it is assumed that a task of deleting a resource occurs during an update task of the client environment 250. In the following description, only the points that are different from the first and second embodiments will be mentioned with reference to Figs. 1 to 13.

[0117] Fig. 17 is a flowchart showing an example of the procedure of a system update control process in the third embodiment. The flowchart shown in Fig. 17 is almost the same as the flowchart shown in Fig. 10, and therefore a description of the same procedure will be omitted.

[0118] When the user operates the execute button 311 on the update start instruction screen 310 displayed on the output unit 114, the update start instruction 201 is input to the master environment information collection unit 212. Then, in step S101A, the master environment information collection unit 212 acquires master environment information 510 from the master environment information transmission unit 221 and registers it in the master environment information DB 213. At that time, the master environment information collection unit 212 also registers in the master environment information DB 213 the resources that have been deleted from the master environment.

[0119] The master environment information collection unit 212 sets the setting item 513 to blank for the record of the resource name 511 of the resource deleted in the master environment in the master environment information 510, and registers it in the master environment information DB 213. Steps S102 to S107 are the same as steps S102 to S107 of the first embodiment shown in FIG.

[0120] Fig. 18 is a flowchart showing an example of detailed steps of the difference information acquisition process (step S105) in the second embodiment. The flowchart shown in Fig. 14 is almost the same as the flowchart shown in Fig. 10, so a description of the same steps will be omitted. Therefore, a description of steps S201 to S203 will be omitted.

[0121] In step S204, the difference acquisition unit 216 registers only one record of the difference information 710 for the resource name 511 for which the setting item 513 was blank in the master environment information 510, with the update item 711, the setting value before update 712, and the setting value after update 713 set to blank, in the difference information DB 217. Explanation of step S205 will be omitted.

[0122] 19A and 19B are flowcharts showing an example of detailed procedures of the update possibility information acquisition process (step S106 in FIG. 10) in the third embodiment. The flowchart shown in FIG. 19B is a continuation of the flowchart shown in FIG. 19A. The flowcharts shown in FIGS. 19A and 19B are almost the same as the flowcharts shown in FIGS. 12A and 12B. Step S301 is the same as step S301 in the first embodiment, and therefore description thereof will be omitted.

[0123] In step S302B, the update possibility determination unit 218 registers the difference information 710 in the difference information DB 217. At that time, the update possibility determination unit 218 determines whether the pre-update setting value 712 of the difference information 710 is blank. If the pre-update setting value 712 is blank, the update possibility determination unit 218 executes step S301 described above for the next record in the difference information 710, and if the pre-update setting value 712 is not blank, the update possibility determination unit 218 executes step S303. Steps S303 to S315 are the same as steps S303 to S315 shown in Figures 12A and 12B.

[0124] Fig. 20 is a flowchart showing an example of the procedure for updating the client environment 250 in the third embodiment. The flowchart shown in Fig. 20 is almost the same as the flowchart shown in Fig. 13. Explanation of steps S401 and S402 will be omitted.

[0125] In step S403B, the update implementation unit 232 updates the client environment 250 based on the difference information 710 sent by the update instruction unit 2111. At that time, if the update item 711, the pre-update setting value 712, and the post-update setting value 713 of the difference information 710 are blank, the update implementation unit 232 deletes the resource of the client environment 250 that matches the resource name 511.

[0126] According to the third embodiment, when updating the client environment 250, processing for deleting resources becomes possible.

[0127] The resource update control system according to this embodiment is an update control system server 110 as an example of an update control system that controls the execution of update processing for at least one client environment 250 in accordance with an update of the master environment 240, and includes: a difference acquisition unit 216 that acquires difference information 710 indicating the differences between resource setting items of the master environment 240 and the client environment 250; an update impossibility criteria information DB 219 as an example of an update impossibility criteria information unit that stores update impossibility criteria information 810 that defines the criteria for which execution of update processing for the client environment 250 is impossible; an update feasibility determination unit 218 that determines whether or not to execute update processing for the client environment 250 based on the difference information 710 and the update impossibility criteria information 810 when reflecting an update of the master environment 240 in the client environment 250 based on the difference information 710; and an update feasibility information DB 2110 as an example of an update feasibility information unit that stores the results of the update feasibility determination unit 218 regarding whether or not to execute update processing for the client environment 250.

[0128] The resource update control method of the resource update control system according to this embodiment is a method in which the difference acquisition unit 216 controls the execution of an update process for at least one client environment 250 in response to an update of the master environment 240, and includes the following steps: a difference acquisition step in which the difference acquisition unit 216 acquires difference information 710 indicating differences between resource setting items between the master environment 240 and the client environment 250; an update impossibility criteria information storage step in which an update impossibility criteria information DB 219, as an example of an update impossibility criteria information unit, stores update impossibility criteria information 810 that defines criteria for why the update process cannot be executed for the client environment 250; an update feasibility determination step in which, when reflecting an update of the master environment 240 in the client environment 250 based on the difference information 710, the update feasibility determination unit 218 determines whether the update process for the client environment 250 can be executed based on the difference information 710 and the update impossibility criteria information 810; and an update feasibility information storage step in which an update feasibility information DB 2110, as an example of an update feasibility information unit, stores a result regarding whether the update process for the client environment 250 can be executed by the update feasibility determination unit 218.

[0129] In this way, depending on the result of the update possibility determination unit 218 as to whether or not the update process for the client environment 250 can be executed, the system of the client environment can be updated only if the update process for the client environment is possible.

[0130] In this embodiment, the difference information 710 includes, for example, a client ID 611 as an example of information that can uniquely identify the client environment 250 to be compared with the master environment 240, a resource name 511 as an example of information that can uniquely identify a resource (e.g., "RDS") having a difference in a setting item between the master environment 240 and the client environment 250, a service name 512 of a service as an example of a setting item in which a difference has occurred in the resource having a difference, an update item 711 as an example of a setting item in which a difference has occurred in the resource having a difference, and information on the difference in the setting item (e.g., a pre-update setting value 712 that indicates the setting value in the client environment information 610 for the update item 711, and a post-update setting value 713 that indicates the setting value in the master environment information 510 for the update item 711). In this way, the system of the client environment can be updated more accurately only when the update processing for the client environment is possible, depending on the result of the update feasibility determination unit 218 regarding whether or not to execute the update processing for the client environment 250 based on the difference information 710 and the update disallowance criteria information 810, which include the above specific information.

[0131] In this embodiment, the update disabling criteria information 810 includes, for example, the service name 512 of a resource for which update processing on the client environment 250 may be disabled, a target item 811 as an example of a target item that is subject to a condition that disables the update processing on the client environment 250 in the service of the service name 512, and difference contents of setting values ​​for the target item 811 that disable the update processing on the client environment 250 (a pre-update criteria value 812 indicating the criteria value that the update item satisfies before the update, and, if the update is disabled, a post-update criteria value 813 indicating the criteria value that the update item satisfies after the update). In this way, the system of the client environment can be updated more accurately only when the update processing on the client environment is possible, depending on the result of the update feasibility determination unit 218 regarding whether or not to execute the update processing on the client environment 250, which is based on the update disabling criteria information 810 and the difference information 710 including the above specific information.

[0132] In this embodiment, the update possibility determination unit 218 compares the difference information 710 with the update impossibility criteria information 810, and determines whether the setting item in which the difference occurred for the resource with a difference in the difference information 710 and the difference content of the setting item satisfy the target item (target item 811 in Figure 6 described later) that is subject to the conditions under which update processing for the client environment 250 becomes impossible in the update impossibility criteria information 810, and the change content of the setting value that makes update processing for the client environment 250 impossible for the setting item (for example, the ``version'' of update item 711 in Figure 5 described later), and if the change content of the setting value that makes the update processing impossible is satisfied, it determines that update processing for the relevant client environment 250 is impossible based on the client ID, which is an example of information that can uniquely identify the client environment 250 included in the difference information 710. In this way, the system of the client environment can be updated more accurately only when the update processing of the client environment is possible, depending on the result of the update impossibility determination unit 218 regarding whether or not to execute the update processing for the client environment 250 based on the update impossibility criteria information 810 and the difference information 710, which include the conditions under which the update processing for the specific client environment 250 described above is impossible.

[0133] In this embodiment, the update feasibility determination unit 218 implements a virtual resource in a specific update control system that can attempt to perform update work, and if the update work of the above-mentioned update process on the virtual resource fails as a result of the trial, it stores the details of the update work in the update disabling criteria information DB 219, which is an example of an update disabling criteria information unit, as update disabling criteria information 810. In this way, the system of the client environment can be updated only when the update process of the client environment is possible, while taking into consideration the results of the trial update process described above.

[0134] The resource update control system according to this embodiment includes a master environment information collection unit 212 that acquires system configuration information of the master environment 240, a master environment information DB 213 as an example of a master environment information unit that stores the system configuration information of the master environment 240, a client environment information collection unit 214 that acquires the system configuration of the client environment 250, and a client environment information DB 215 as an example of a client environment information unit that stores the system configuration information of the client environment 250.

[0135] In this embodiment, the update instruction unit 2111 uses the difference information 710 to transmit an instruction to update the client environment 250. In this way, in accordance with the update instruction for the client environment 250 transmitted in accordance with the difference information 710, it is possible to more accurately update the system of the client environment only when the update process for the client environment is possible.

[0136] In this embodiment, the update instruction unit 2111 transmits an instruction to update the resource settings of the client environment 250, or to add or delete resources, based on the difference information 710. In this way, in accordance with the update instruction for the client environment 250 transmitted in accordance with the difference information 710, it is possible to more accurately update the resource settings of the system of the client environment, or to add or delete resources, only when the update process for the client environment is possible.

[0137] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, the elements described in parallel in the present embodiment may be configured such that at least one of the elements is connected in series to the other elements.

[0138] In this embodiment, information such as programs, tables, files, etc. that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC (Integrated Circuit) card, an SD card, or a DVD (Digital Versatile Disc). [Industrial Applicability]

[0139] The present invention can be applied to information systems that provide various services using technology to update systems in client environments that acquire data from IOT (Internet of Things) devices, such as sensors installed in large numbers on factory lines. [Explanation of symbols]

[0140] 212...Master environment information collection unit, 213...Master environment information DB, 214...Client environment information collection unit, 215...Client environment information DB, 216...Difference acquisition unit, 217...Difference information DB, 218...Update feasibility determination unit, 219...Update non-operation criterion information DB, 2110...Update feasibility determination DB, 2111...Update instruction unit, 221...Master environment information transmission unit, 231...Environment information transmission unit, 232...Update implementation unit, 240...Master environment, 250...Client environment, 510...Master environment information, 610...Client environment information, 710...Difference information, 810...Update non-operation criterion information, 910...Update feasibility information

Claims

1. An update control system that controls execution of an update process for at least one client environment in response to an update of a master environment, a difference acquisition unit that acquires difference information indicating differences between resource setting items between the master environment and the client environment; an update impossibility criteria information unit that stores update impossibility criteria information that defines criteria for making it impossible to execute the update process for the client environment; an update possibility determination unit that, when updating the master environment based on the difference information and the update prohibition criteria information, determines whether or not the update process for the client environment can be executed, an update possibility information unit that stores a result of the update possibility determination unit as to whether the update process for the client environment can be executed; An update control system comprising:

2. The difference information is information that can uniquely identify the client environment to be compared with the master environment; Information that can uniquely identify resources that have differences in configuration items between the master environment and the client environment; A setting item in which a difference has occurred in the resource having the difference; Information on differences in the setting items; 2. The resource update control system according to claim 1, further comprising:

3. The update non-permitting criteria information is a service name for a service for which the update process for the client environment may be impossible; In the service with the service name, a target item that is subject to a condition that makes the update process for the client environment impossible; and A difference in the setting value that makes the update process for the client environment impossible for the target item; 2. The resource update control system according to claim 1, further comprising:

4. The update possibility determination unit comparing the difference information with the update disablement criteria information, and determining whether or not the setting item in which the difference has occurred for the resource having a difference in the difference information, and the difference content in the setting item, satisfy the target item that is the subject of the condition that makes the update process for the client environment impossible in the update disablement criteria information, and the change content of the setting value in the setting item that makes the update process for the client environment impossible; If the change content of the setting value that makes the update process impossible is satisfied, it is determined that the update process for the corresponding client environment is impossible based on information that can uniquely identify the client environment included in the difference information.

2. The resource update control system according to claim 1.

5. The update possibility determination unit A virtual resource is implemented in a specific update control system that can attempt to perform update work, and if the update work of the update process is attempted on the virtual resource and fails, the content of the update work is stored in the update disabling criterion information unit as the update disabling criterion information.

2. The resource update control system according to claim 1.

6. a master environment information collection unit that acquires system configuration information of the master environment; a master environment information unit for storing system configuration information of the master environment; a client environment information collection unit that acquires a system configuration of the client environment; a client environment information unit for storing system configuration information of the client environment; 2. The resource update control system according to claim 1, further comprising:

7. an update instruction unit that uses the difference information to send an update instruction to the client environment; 2. The resource update control system according to claim 1.

8. The update instruction unit Based on the difference information, an instruction is sent to update the resource settings of the client environment, or to add or delete a resource.

8. The resource update control system according to claim 7.

9. A resource update control method in which a difference acquisition unit controls execution of an update process for at least one client environment in response to an update of a master environment, a difference acquisition step of acquiring difference information indicating differences between resource setting items between the master environment and the client environment; an update impossibility criterion information storage step in which an update impossibility criterion information unit stores update impossibility criterion information that defines a criterion for making it impossible to execute the update process for the client environment; an update possibility determination step in which, when reflecting the update of the master environment in the client environment based on the difference information, an update possibility determination unit determines whether or not the update process for the client environment can be executed based on the difference information and the update impossibility criterion information; an update possibility information storage step in which an update possibility information unit stores a result of the update possibility determination unit as to whether or not the update process regarding the client environment can be executed; A resource update control method comprising:

Images