Operation management system, operation management method, and operation management program

Abstract

To provide an operation management system, an operation management method and an operation management program capable of reducing an operation cost accompanying a change of a system.SOLUTION: An operation management system is provided with a plurality of operation templates in which at least one procedure for managing an operation of a system is described, a conflict determination unit configured to determine whether or not execution of a specific procedure included in a specific operation template among the plurality of operation templates causes a conflict that may hinder execution of another procedure included in another operation template among the plurality of operation templates, and a presentation unit that presents information related to the specific procedure to the outside before the specific procedure is actually executed when it is determined by the competition determination unit that the execution of the specific procedure causes the conflict.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an operation management system, an operation management method, and an operation management program for managing the operation of a system, and is suitable for application to an operation management system that can change the operation of a system according to each procedure described in an operation template, for example. [Background technology]

[0002] In order to keep up with the rapid changes in market needs, digital transformation (DX) of customer operations is progressing. The approach of frequently updating applications to reflect market needs, such as adding and improving functions and improving performance, is becoming more widespread. In addition to responding to market needs, security patches must be applied as soon as possible to keep applications and IT systems secure. To avoid disruptions to business operations before and after updates to business systems including these applications, it is necessary to always check whether business operations can be run and operated without problems after updates.

[0003] Regarding system operation management, Patent Document 1 describes how, in order to make it easier to create and manage work plans for the management system, setting values ​​are input at the same time as creating an operation work manual based on a template, but if a parameter as a setting value that should be input in advance is not set, an error is notified to the creator. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5848317 Summary of the Invention [Problem to be solved by the invention]

[0005] In the management system disclosed in Patent Document 1, in order to ensure stable operation after the system is changed, a skilled upper-level manager reviews the operation manual in detail and confirms that no failures occur when an operator changes the system according to the operation manual. However, such confirmation work may incur operational costs in a situation where the system is frequently changed.

[0006] The present invention has been made in consideration of the above points, and aims to propose an operations management system, an operations management method, and an operations management program that are capable of reducing the operations costs associated with system changes. [Means for solving the problem]

[0007] In order to solve this problem, the present invention provides an operation template management table that manages a plurality of operation templates, each of which describes at least one procedure for managing system operation; a conflict determination unit that determines whether execution of a specific procedure included in a specific operation template among the plurality of operation templates will cause a conflict that will interfere with the execution of other procedures included in other operation templates among the plurality of operation templates; and a presentation unit that, when the conflict determination unit determines that execution of the specific procedure will cause the conflict, presents information related to the specific procedure to the outside before the specific procedure is actually executed.

[0008] Furthermore, in the present invention, the operation management system has a conflict determination step in which a conflict determination unit determines whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates, each of which describes at least one procedure for managing the operation of the system, will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates, and a presentation step in which a presentation unit of the operation management system presents information regarding the specific procedure to the outside before the specific procedure is actually executed, if the conflict determination unit determines that execution of the specific procedure will cause the conflict.

[0009] Furthermore, in the present invention, a conflict determination step is performed on a computer to cause a conflict determination unit of the operation management system to determine whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates, each of which describes at least one procedure for managing the operation of the system, will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates, and a presentation step is performed on a computer to cause a presentation unit of the operation management system to present information regarding the specific procedure to the outside before the specific procedure is actually executed, if the conflict determination unit determines that execution of the specific procedure will cause the conflict. Effect of the Invention

[0010] According to the present invention, it is possible to realize an operations management system, an operations management method, and an operations management program that are capable of reducing the operations costs associated with system changes. [Brief description of the drawings]

[0011] [Figure 1] 1 is a system configuration diagram showing an example of the configuration of a computer system including an operation management system according to this embodiment. [Diagram 2] 2 is a system configuration diagram showing an example of the configuration of the operation management system shown in FIG. 1. [Diagram 3] 2 is a system configuration diagram showing an example of the configuration of a server constituting the customer system shown in FIG. 1. [Figure 4] 3 is a diagram illustrating an example of a configuration of a customer environment management table illustrated in FIG. 2; [Diagram 5] 3 is a diagram illustrating an example of a configuration of an operational template management table illustrated in FIG. 2. [Figure 6] 3 is a diagram showing an example of the configuration of a procedure management table shown in FIG. 2; [Figure 7] 3 is a diagram showing an example of the configuration of a customer profile management table shown in FIG. 2; FIG. [Figure 8] 3 is a diagram illustrating an example of the configuration of a namespace management table illustrated in FIG. 2; [Figure 9] 13 is a flowchart illustrating an example of a procedure for an operation template conflict detection process. [Figure 10] 13 is a flowchart illustrating an example of a procedure for detecting a customer profile conflict. [Figure 11] 13 is a flowchart illustrating an example of a procedure for searching for a solution candidate. [Figure 12] FIG. 13 is a diagram showing an example of a conflict content presentation screen. [Figure 13] FIG. 13 is a diagram showing an example of a screen presenting a conflict resolution proposal. [Figure 14] FIG. 13 is a diagram illustrating an example of a managed service screen. [Figure 15] FIG. 13 is a diagram showing an example of a state transition diagram of setting items and setting values ​​of a customer profile. [Figure 16] 13 is a diagram showing an example of state transitions of setting items and setting values ​​of a customer profile. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0013] 1 is a system configuration diagram showing an example of the configuration of a computer system including an operation management system 101 according to this embodiment. The computer system includes the operation management system 101, an operator terminal 170, an upper-level administrator terminal 180, a customer system 100, and a network switch 103 (corresponding to "NW-SW" in the figure). In the computer system, the operation management system 101, the operator terminal 170, the upper-level administrator terminal 180, and the customer system 100 are connected to the network switch 103. The network switch 103 has, for example, a MAC (Media Access Control) address table and has a function of checking what MAC address the device connected to each port has and transmitting data only to the necessary port.

[0014] The operation management system 101 comprises a control program 110 and a management table group 111. The control program 110 is an example of an operation management program, and manages the operation of the customer system 100 using the management table group 111. Although details will be described later, the operation management system 101 is configured by a server using at least one computer, and executes an operation management method by running the operation management program on that computer.

[0015] There are multiple operator terminals 170, which are terminal devices operated by operators of the customer system 100. The operator terminal 170 plays a role of operating based on the procedures described in the work procedure manual. In this role, the operator terminal 170 does not distinguish between incidents or determine whether they can be handled. In this embodiment, the "procedure (specific procedure)" refers to at least one of an "operation procedure" and a "setting procedure."

[0016] There are a plurality of upper-level administrator terminals 180, which are terminal devices operated by an upper-level administrator (Administrator) who issues instructions to an operator (Operator) who operates the operator terminal 170. Here, the operator performs operation tasks based on the description of the operation procedure manual, and all judgments are made by the upper-level administrator or the department that developed the business application. The judgments include investigation of the cause of the failure, planning of countermeasures, and creation of recovery procedures. The operator collects information required for cause investigation (scripts for log collection and collection procedures are defined in advance in the operation procedure manual), and restarts or re-executes the application only when it is described in the operation procedure manual, according to the description in the operation procedure manual. The upper-level administrator terminal 180 plays a role of creating a work procedure manual, considering how to deal with inquiries (escalations) from operators, and instructing the operators to do the work. In this role, it separates incidents and judges whether they can be handled. The upper-level administrator terminal 180 may be divided into departments and members for each specialized field, such as infrastructure (servers, networks, storage devices), applications, and layers of equipment and software.

[0017] The customer system 100 is mainly composed of a server, and includes, as hardware, a NIC (Network Interface Card) 112F, a PCIe (Peripheral Component Interconnect Express)-SW (SWitch) 107, a HBA (Host Bus Adapter) 115, a NIC (Network Interface Card) 112B, a FC (Fiber Channel)-SW (SWitch) 108, and a storage system 105 having a plurality of logical units (corresponding to "LU1" to "LUn" in the figure). Note that the customer system 100 is not limited to the above configuration, and may have other configurations.

[0018] Fig. 2 is a system configuration diagram showing an example of the configuration of the operation management system 101 shown in Fig. 1. The operation management system 101 is configured by a server including a CPU (Central Processing Unit) 206, a memory 202, a BMC (Baseboard Management Controller) 208, a disk interface 203, a network interface 204, and a PCIe interface 205. The memory 202 includes the above-mentioned control program 110, an OS (Operating System) 216, and a management table group 111.

[0019] The management table group 111 includes an operational template management table 201, a customer profile management table 309, a procedure management table 311, a name space management table 211, and a customer environment management table 312. The management table group 111 may also include a priority management table, which will be described later.

[0020] The operation template management table 201 manages a plurality of operation templates in which at least one procedure for managing the operation of the customer system 100 is described.

[0021] The customer profile management table 309 is a table for managing customer profiles. The customer profile includes setting items and setting values ​​of the setting items of the customer system 100. The procedure management table 311 manages a plurality of operation procedures including at least one operation template.

[0022] The namespace management table 211 manages the namespace related to the setting value of the setting item of the customer profile. The namespace management table 211 manages the constraint condition that does not allow the same namespace to be overlapped for the namespace related to the setting value of the setting item of the customer profile. The determination using the constraint condition will be described later.

[0023] The client environment management table 312 is a so-called environment setting file, and is, for example, a file with a file name of “~.conf.” The client environment management table 312 will be described later.

[0024] The control program 110 includes at least an operation template conflict detection unit 131 and a customer profile conflict detection unit 130 , and preferably further includes an operation work appropriateness determination unit 120 .

[0025] The operational template conflict detection unit 131 is an example of a conflict determination unit, and determines whether or not the execution of a specific procedure included in a specific operational template among multiple operational templates will cause a conflict that will interfere with the execution of other procedures included in other operational templates among the multiple operational templates (presence or absence of a conflict).

[0026] The control program 110 is an example of a presentation unit, and when it is determined that the execution of a specific procedure included in a specific operational template will cause a conflict, the control program 110 displays information about the specific procedure on a screen and presents it to the outside before the specific procedure is actually executed. Details of the screen will be described later.

[0027] The customer profile conflict detection unit 130 is an example of a conflict determination unit, and determines whether an update to the setting values ​​of the setting items in a customer's profile (hereinafter also referred to as a "customer profile") will cause a conflict that may interfere with the execution of procedures included in some of the multiple operation templates.

[0028] The operational work appropriateness determining unit 120 determines the appropriateness of the setting values ​​of the setting items in the customer profile. The operational work appropriateness determining unit 120 will be described in detail later.

[0029] Fig. 3 is a system configuration diagram showing an example of the configuration of the server 104 constituting the customer system 100 shown in Fig. 1. The customer system 100 is configured so that the primary site can be switched in response to DR (Disaster Recovery) described later. The server 104 is configured by a computer including a CPU 301, a memory 302, a BMC 401, a disk interface 303, a network interface 304, and a PCIe interface 305.

[0030] The BMC 401, disk interface 303, network interface 304, and PCIe interface 305 of the server 104 have substantially the same functions as the BMC 208, disk interface 203, network interface 204, and PCIe interface 205 of the operation management system 101 described above, respectively.

[0031] An IP (Internet Protocol) address, which will be described later, can be set as an example of a setting value of a setting item of a customer profile in the network interface 304. The setting value of the setting item of the customer profile is not limited to the IP address described above, and may be a setting value of another setting item.

[0032] The memory 202 includes a plurality of VMs (Virtual Machines) 314, a hypervisor 315, and an OS 316. The VM 314 stores a plurality of containers 331 including business applications 341, and also stores a monitoring program 343. The monitoring program 343 monitors the operation status of each business application 341. Note that the above-described configuration of the server 104 is merely an example, and is not limited to the above-described configuration, and other configurations may be used.

[0033] Fig. 4 is a diagram showing an example of the configuration of the customer environment management table 312 shown in Fig. 2. The customer environment management table 312 manages the environment of the customer system 100. The customer environment management table 312 is a table for managing records including an ID (IDentifier) ​​701, a customer ID (IDentifier) ​​702, a category 703, an item 704, and a range 705.

[0034] ID 701 indicates an identifier for identifying each record from another. Customer ID 702 is an identifier for identifying each customer from another. Classification 703 indicates a classification of equipment etc. equipped in the customer system 100 indicated by customer ID 702. Item 704 indicates an item included in the classification indicated by classification 703. Range 705 indicates a range as a name space that is acceptable as a value of the item indicated by item 404.

[0035] Fig. 5 is a diagram showing an example of the configuration of the operational template management table 201 shown in Fig. 2. The operational template management table 201 is a table for managing records including an ID (IDentifier) ​​801, an operational template name 802, and a procedure 803.

[0036] An ID 801 indicates an identifier for identifying each record from another. An operation template name 802 indicates the name of each operation template. A procedure 803 indicates each procedure included in each operation template.

[0037] Fig. 6 is a diagram showing an example of the configuration of the procedure management table 311 shown in Fig. 2. The procedure management table 311 manages each procedure included in at least one of the multiple operation templates managed by the operation template management table 201 (see Fig. 5). The procedure management table 311 is a table for managing records including a procedure ID (IDentifier) ​​901, a body 902, an attribute 903, a conflict 904, and a candidate solution 905.

[0038] A procedure ID (IDentifier) ​​901 indicates an identifier for distinguishing each record from another. A body 902 indicates the contents of the body in which the procedure is described. An attribute 903 indicates information on whether or not to change the configuration of the customer system 100. For example, the attribute 903 indicates that "R (Read)" indicates only reading, i.e., no changes, and "W (Write)" indicates that writing can also be performed, i.e., changes will be made.

[0039] Conflict 904 shows the result of determining whether a conflict has occurred. Conflict 904 stores the detection result regarding which variables of which procedures are in conflict. Potential solutions 905 stores possible solutions. For example, such solutions may include presenting name candidates for resolving overlapping namespaces.

[0040] As described above, the procedure management table 311 is an example of an attribute management table, and manages information regarding whether the attribute (W) of the system operation is changeable or the attribute (R) of the system operation is not changeable. When the operation template conflict detection unit 131 refers to the attribute management table and determines that a conflict will occur if the specific procedure described in the specific operation template is a procedure that attempts to change the system operation despite having an attribute (R) that does not allow the system operation to be changed.

[0041] Fig. 7 is a diagram showing an example of the configuration of the customer profile management table 309 shown in Fig. 2. The customer profile management table 309 manages customer profiles. The customer profile management table 309 is a table for managing records including an ID (IDentifier) ​​1001, a customer ID 1002, a variable (setting item) 1003, and a value (setting value) 1004. The customer profile includes a setting value for at least one setting item. The setting items of the customer profile will be described later.

[0042] ID 1001 indicates an identifier for identifying each record from another. Customer ID 1002 indicates an identifier for identifying each customer who operates the customer system 100 from another. A variable indicated by variable 1003 indicates a setting item of a customer profile. Value 1004 indicates a setting value of the setting item indicated by the variable 1003, and indicates, for example, an example of a so-called Config file with a file name of "~.conf".

[0043] Fig. 8 is a diagram showing an example of the configuration of the namespace management table 211 shown in Fig. 2. The namespace management table 211 manages rules for whether or not there is duplication regarding the namespaces of setting items and setting values. The namespace management table 211 is a table for managing records including an ID (IDentifier) ​​1101, a customer name 1102, an item 1103, a range 1104, whether or not there is duplication 1105, and a valid range 1106.

[0044] An ID (IDentifier) ​​1101 indicates an identifier for distinguishing each record from another. A customer name 1102 indicates the name of the customer who operates the customer system 100. An item 1103 indicates an item that places a restriction on the name space. A range 1104 indicates the usable range for the item specified in the item 1103.

[0045] The duplication possibility 1105 indicates whether duplication of the same item is permitted for the item specified in the item 1103. The validity range 1106 indicates the range in which the namespace restriction is valid (whether only within a specific customer or across multiple customers). In the validity range 1106, "all" indicates whether the restriction is imposed across multiple customers. For example, in the validity range 1106, if the duplication possibility 1105 is "NG", it indicates that duplication is not permitted even between different customers, whereas if the duplication possibility 1105 is "OK", it indicates that duplication is permitted even between different customers. The following case is given as an example of "all". For example, in an email service, an email address is unique key information, and the same email address is not permitted within the same service. It is necessary to restrict duplication across multiple customers.

[0046] 9 is a flowchart showing an example of a procedure for the operation template conflict detection process. The operation template conflict detection process is executed by the operation template conflict detection unit 131 shown in FIG.

[0047] In step S901, the operational template conflict detection unit 131 refers to the operational template management table 201 (see Figure 5) using the ID of the operational template as a search key to obtain each procedure, and also refers to the procedure management table 311 using each procedure as a search key to refer to the attribute of attribute 903 corresponding to each procedure, and confirms whether the attribute is "R (reference only)".

[0048] If the attribute is "R (reference only)", the operation template conflict detection unit 131 executes step S904 described below, whereas if the attribute is not "R (reference only)", the operation template conflict detection unit 131 executes step S903.

[0049] In step S903, the operation template conflict detection unit 131 checks whether there is a conflict. This is because, if the status is not "R (reference only)" as described above, a conflict may occur if there is a change in the system configuration of the customer system 100 or the setting value of the setting item.

[0050] In step S904, the operation template conflict detection unit 131 determines whether or not there is an unconfirmed conflict. Specifically, the operation template conflict detection unit 131 checks whether or not there is an unconfirmed conflict. If there is no unconfirmed conflict, the operation template conflict detection unit 131 ends the operation template conflict detection process, whereas if there is an unconfirmed conflict, the operation template conflict detection unit 131 returns to the above-mentioned step S902 and executes step S902 and subsequent steps.

[0051] When there are no unconfirmed conflicts and the operational template conflict detection process is terminated, the operational work validity determination unit 120 executes an operational template validity determination process. In the operational template validity determination process, the operational work validity determination unit 120 determines whether or not the implementation of each procedure included in the operational template is valid from the perspective of continuous operation of the system, taking into account the detected conflicts.

[0052] Here, the operation management method of the operation management system 101 according to this embodiment includes a conflict determination step in which the operation template conflict detection unit 131 as an example of a conflict determination unit of the operation management system 101 determines whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates in which at least one procedure for managing the operation of the customer system 100 is described will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates, and a presentation step in which the conflict content presentation screen 1200 as an example of a presentation unit of the operation management system 101 presents information regarding the specific procedure to the outside before the specific procedure is actually executed, if the operation template conflict detection unit 131 determines that execution of the specific procedure will cause a conflict.

[0053] In addition, in this embodiment, the above-mentioned control program 110 causes the operation template conflict detection unit 131, as an example of a conflict determination unit of the operation management system 101, to determine whether or not execution of a specific procedure included in a specific operation template among multiple operation templates in which at least one procedure for managing the operation of the customer system 100 is described will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the multiple operation templates; and a presentation step, on the computer, causes the conflict content presentation screen 1200, as an example of a presentation unit of the operation management system 101, to present information regarding the specific procedure to the outside before the specific procedure is actually executed, if the operation template conflict detection unit 131 determines that the execution of the specific procedure will cause a conflict.

[0054] 10 is a flowchart showing an example of a procedure for the customer profile conflict detection process. This customer profile conflict detection process is executed by the customer profile conflict detection unit 130 shown in FIG.

[0055] As described above, the operation management system 101 according to this embodiment manages setting items for managing the operation of the system, and includes, as the setting items, a customer profile as an example of a profile including setting items indicating system attributes and setting values ​​of the setting items. The customer profile conflict detection unit 130 is an example of a conflict determination unit, and determines whether or not an update of the setting values ​​of the setting items of the customer profile will cause a conflict that may interfere with the execution of procedures included in some of the operation templates among multiple operation templates.

[0056] In step S1001, the customer profile conflict detection unit 130 refers to the customer environment management table 312 using the customer profile ID as a search key to acquire setting items and setting values. In step S1002, the customer profile conflict detection unit 130 determines whether there is any overlap in the setting items and setting values.

[0057] If the customer profile conflict detection unit 130 determines that there is no overlap in the setting items and setting values, it executes step S1005 described below, but if it determines that there is overlap in the setting items and setting values, it executes step S1003.

[0058] In step S1003, the customer profile conflict detection unit 130 refers to the namespace management table 211 to obtain a rule for whether or not the namespaces of the setting items and the setting values ​​are allowed to overlap. The namespace management table 211 manages, as the rule, a constraint condition that does not allow the same namespace to overlap with the namespaces of the setting values ​​of the setting items.

[0059] In step S1004, the customer profile conflict detection unit 130 refers to the namespace management table 211 and determines whether or not there is a violation of the above-mentioned constraint conditions. If there is no violation, the customer profile conflict detection unit 130 returns to step S1002, and if there is a violation, the customer profile conflict detection unit 130 executes step S1005.

[0060] In step S1005, the customer profile conflict detection unit 130 classifies the level of violation due to duplication, and stores the duplicated setting items and setting values ​​in a predetermined area of ​​the memory 202. The customer profile conflict detection unit 130 presents at least the setting items and setting values ​​on a conflict content presentation screen 1200 described later.

[0061] The operational work validity determination unit 120 executes a customer profile validity determination process. In the customer profile validity determination process, the operational work validity determination unit 120 determines whether or not the setting values ​​of the setting items of the customer profile are valid from the viewpoint of continuous operation of the system, taking into account the content of the violation.

[0062] 11 is a flowchart showing an example of a procedure for searching for a solution candidate. The search for a solution candidate is executed by the operation work validity determination unit 120. In step S1101, the operation work validity determination unit 120 refers to the namespace management table 211 and acquires the setting item and the setting value of the part where the violation occurs, and the rule for whether or not duplication is allowed in the namespace.

[0063] In step S1102, the operational work validity determination unit 120 acquires the type of the violation target. In step S1103, the operational work validity determination unit 120 judges whether or not it is possible to set a value (setting value) that avoids duplication for the setting item. If the operational work validity determination unit 120 determines that it is not possible to set a value that avoids duplication, it executes step S1105, which will be described later, whereas if it determines that it is possible to set a value that avoids duplication, it executes step S1104.

[0064] In step S1104, the operation work adequacy determination unit 120 sets a value (setting value) for the setting item, and stores it in the customer environment management table 312. In step S1105, the operation work adequacy determination unit 120 judges whether or not any violations remain. If any violations remain, the operation work adequacy determination unit 120 returns to and executes step S1101 described above, whereas if no violations remain, it ends the search process for solution candidates.

[0065] 12 is a diagram showing an example of a conflict content presentation screen 1200. The conflict content presentation screen 1200 includes an ID (IDentifier) ​​1201, a customer ID 1202, a conflicting part 1203, a competitor 1204, and a reason 1205.

[0066] An ID (identifier) ​​1201 is an identifier for identifying each operation template from another. A customer ID 1202 is an identifier for identifying the customer who operates the operation template indicated by the ID 1201 from other customers.

[0067] Conflict part 1203 indicates the source of the conflict that may cause a conflict, either the procedure of the operation template, the setting value of a setting item in the customer profile, or the customer name. Competitor 1204 indicates the procedure of the operation template or the setting value of a setting item in the customer profile that may cause a conflict. If no conflict occurs (for example, if ID 1201 is "n"), "no conflict" is displayed in competitor 1204. Reason 1205 indicates the reason why the conflict occurred.

[0068] In this embodiment, the conflict content presentation screen 1200 is an example of a presentation unit, and when the operation template conflict detection unit 131 (conflict determination unit) determines that the execution of a specific procedure will cause a conflict, information about the specific procedure is presented to the outside before the specific procedure is actually executed.

[0069] When the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict, the conflict content presentation screen 1200 presents to the outside, together with the specific procedure, information about the customer system 100 on which the specific procedure is to be executed, such as the customer name.

[0070] 13 is a diagram showing an example of a conflict resolution proposal presentation screen 1300. The conflict resolution proposal presentation screen 1300 includes an ID (IDentifier) ​​1301, information 1302, a customer ID 1303, a conflicting part 1304, a competitor 1305, and a solution proposal 1306.

[0071] In this embodiment, when it is determined that a conflict occurs regarding a customer profile, for example, the customer profile conflict detection unit 130 presents at least the setting values ​​of the setting items on a conflict resolution proposal presentation screen 1300 (presentation unit).

[0072] The ID 1301 is an identifier for identifying each customer profile or each operation template from each other. The information 1302 indicates information according to the degree of the conflict, with "Warning" being displayed if it is at a warning level, "Error" being displayed if it is at a level that will cause a disruption to the operation of the system, and "Information" being displayed if it is merely a level of reference information.

[0073] The customer ID 1203 is an identifier for identifying the customer who is using the customer profile or operation template indicated by the ID 1301 from other customers. The conflicting part 1304 indicates the specific part (setting value of the setting item, procedure) of the customer profile and operation template that is determined to be in conflict.

[0074] Competitor 1305 indicates a competitor as a specific counterpart that is a conflicting portion where a conflict may occur in each customer profile or each operation template. Solution proposal 1306 indicates a solution proposal for the conflicting portion indicated by competitor 1204. For example, it is indicated that "$hostName" of "000-0001" of "customer profile" indicated by conflicting portion 1304 with ID 1301 of "2" conflicts with "$hostName" of "step 2-1" of "operation template 2" indicated by competitor 1305, and is determined to conflict with "$hostName" of "step 3-3" of "operation template 3" indicated by competitor 1305. Note that if there is no competitor in the customer profile (for example, ID 1301 is "n"), competitor 1305 indicates "no conflict."

[0075] A solution proposal 1306 shows a solution proposal for at least one of a customer profile and an operation template. The solution proposal 1306 shows a solution proposal for avoiding a problem when an update of a procedure of an operation template causes a problem in the execution of a procedure of another operation template, or when an update of a value of a setting item of a customer profile may cause a problem in the execution of a procedure of an operation template.

[0076] In this embodiment, the priority management table (not shown) of the management table group 111 manages which of the other procedures that cause a conflict and the specific procedure should be prioritized when the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict. When the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict, it may refer to the priority management table and present the priority on a managed service screen 1400 (presentation unit) described later.

[0077] Fig. 14 is a diagram showing an example of a managed service screen 1400. The managed service screen 1400 includes an ID (IDentifier) ​​1301, information 1302, person in charge 1307, conflicting part 1304, competitor 1305, and priority 1308. The contents indicated by the ID (IDentifier) ​​1301, information 1302, conflicting part 1304, and competitor 1305 on the managed service screen 1400 are similar to the contents indicated by the ID (IDentifier) ​​1301, information 1302, conflicting part 1304, and competitor 1305 on the conflict resolution proposal presentation screen 1300 shown in Fig. 13 described above, respectively, and therefore description thereof will be omitted.

[0078] The person in charge 1307 indicates the name of the team in charge corresponding to the information indicated by each piece of information 1302. The priority 1308 indicates the priority of the response, and for example, the priority is set in the order of "S", "A", "B", "C", etc. from highest to lowest.

[0079] 15 is a diagram showing an example of the state transition of the setting items and setting values ​​of a customer profile. As shown in the figure, the customer profile is registered as the primary site of the DR (Disaster Recovery) setting by executing "Step yyy01-2" of the operation template named "xxx01". As a result, the IP (Internet Protocol) address, which is an example of a setting item in the customer profile, is updated to, for example, "10.0.0.10".

[0080] Next, the customer profile is switched to the secondary site for DR switching by executing "Step yyy03-1" of the operation template named "xxx03". As a result, the IP address, which is an example of a setting item in the customer profile, is updated to, for example, "10.0.254.10".

[0081] Next, the customer profile performs "Step yyy0n-1" of the operation template named "xxxn", and the primary site returns to the original site for DR switchback (after recovery). As a result, the IP address, which is an example of a setting item in the customer profile, is updated to, for example, "10.0.0.10".

[0082] Fig. 16 is a diagram showing an example of state transitions of setting items and setting values ​​of a customer profile according to the state transition example of Fig. 15. The above-mentioned customer profile is for a customer with customer ID 1502 of "000-0001", and the IP address of the primary site shown in variable 1504 has been changed as shown in value 1505, triggered by the trigger shown in trigger 1506.

[0083] As described above, in this embodiment, the conflict resolution proposal presentation screen 1300 is an example of a presentation unit, and when the customer profile conflict detection unit 130 (conflict determination unit) determines that the execution of a specific procedure will cause a conflict, information regarding the specific procedure is presented to the outside before the specific procedure is actually executed.

[0084] The operation management system 101 according to this embodiment includes an operation template management table that manages a plurality of operation templates, each of which describes at least one procedure for managing the operation of a customer system 100; a conflict determination unit that determines whether execution of a specific procedure included in a specific operation template among the plurality of operation templates will cause a conflict that will interfere with the execution of other procedures included in other operation templates among the plurality of operation templates; and a presentation unit that, when the conflict determination unit determines that execution of the specific procedure will cause the conflict, presents information regarding the specific procedure to the outside before the specific procedure is actually executed.

[0085] The operation management method according to this embodiment includes a conflict determination step in which an operation template conflict detection unit 131 as an example of a conflict determination unit of the operation management system 101 determines whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates in which at least one procedure for managing the operation of the customer system 100 is described will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates, and a presentation step in which a conflict content presentation screen 1200 as an example of a presentation unit of the operation management system 101 presents information regarding the specific procedure to the outside before the specific procedure is actually executed, if the operation template conflict detection unit 131 determines that execution of the specific procedure will cause a conflict.

[0086] The control program 110 (operation management program) according to this embodiment executes on a computer a conflict determination step in which an operation template conflict detection unit 131, as an example of a conflict determination unit of the operation management system 101, determines whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates in which at least one procedure for managing the operation of the customer system 100 is described will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates, and a presentation step in which, if the operation template conflict detection unit 131 determines that execution of the specific procedure will cause a conflict, a conflict content presentation screen 1200, as an example of a presentation unit of the operation management system 101, presents information regarding the specific procedure to the outside before the specific procedure is actually executed.

[0087] In this way, executing a procedure based on an operational template can be prevented from affecting other procedures based on other operational templates, thereby reducing the operational costs associated with system changes.

[0088] The operation management system 101 according to this embodiment includes a procedure management table 311 (attribute management table) that manages information on whether the system operation is to be set to an attribute "W" that makes the system operation changeable, or an attribute "R" that makes the system operation not changeable. When a specific procedure described in a specific operation template is a procedure that attempts to change the system operation despite having an attribute "R" that does not make the system operation changeable as a result of referring to the procedure management table 311, the operation work validity determination unit 120 (conflict determination unit) determines that a conflict will occur. In this way, by referring to the attribute, it is possible to prevent the execution of a specific procedure described in a specific operation template from affecting the execution of other procedures described in other operation templates.

[0089] In the operation management system 101 according to this embodiment, the procedure management table 311 manages each procedure included in at least one of the multiple operation templates managed by the operation template management table 201. In this way, even if each procedure managed in the procedure management table 311 is executed based on the operation template, it is possible to prevent other procedures based on other operation templates from being affected.

[0090] In this embodiment, when the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict, the conflict content presentation screen 1200 presents, together with the specific procedure, information on the customer system 100 on which the specific procedure is to be executed, such as the customer name, to the outside. In this way, it becomes possible to grasp in advance the specific procedure that may cause a conflict, as well as the customer name that may be affected when the procedure is executed.

[0091] The operation management system 101 according to this embodiment includes a priority management table that manages which of the specific procedure and other procedures that cause a conflict should be prioritized when the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict. When the operation template conflict detection unit 131 determines that the execution of a specific procedure will cause a conflict, the operation template conflict detection unit 131 may refer to the priority management table and present the priority on the conflict content presentation screen 1200. In this way, even if there is a risk of a conflict occurring, it becomes clear whether the procedure should be given priority for execution.

[0092] The operation management system 101 according to this embodiment manages setting items for managing the operation of the system, and includes a customer profile including setting items and setting values ​​of the setting items that indicate the attributes of the customer system 100 as setting items, and the operation template conflict detection unit 131 determines whether or not updating the setting value of a specific setting item in the customer profile will cause a conflict that may interfere with the execution of procedures included in some of the operation templates among multiple operation templates. In this way, it is possible to know in advance whether updating the setting value of a specific setting item in the customer profile will cause a conflict that may interfere with the execution of procedures included in some of the operation templates.

[0093] The operation management system 101 according to this embodiment includes a namespace management table 211 that manages the constraint condition that does not allow the same namespace to overlap for the namespace related to the setting value of the setting item. The operation template conflict detection unit 131 judges whether or not the constraint condition that does not allow the same namespace to overlap is violated as a result of referring to the namespace management table 211. If it is determined that there is a violation, the operation template conflict detection unit 131 presents at least the setting value of the setting item on the conflict content presentation screen 1200. In this way, it is possible to prevent the occurrence of a failure due to a system change that violates the set constraint condition.

[0094] In this embodiment, when the operation template conflict detection unit 131 or the customer profile conflict detection unit 130 (conflict determination unit) determines that there is a violation of the constraint conditions, the operation work validity determination unit 120 determines whether or not it is possible to set a setting value that avoids duplication for the setting item, and when it determines that it is possible to set a setting value, sets the setting value for the setting item. In this way, by determining the validity of the setting value before actually setting the setting value of the setting item of the customer profile, it is possible to prevent the operation of the system from being hindered.

[0095] Although the present embodiment has been described above, the technical scope of the present invention is not limited to the scope described in the above embodiment. It is clear from the claims that the technical scope of the present invention also includes various modifications or improvements to the above embodiment. In the above embodiment, an IP address is given as an example of a setting value of a setting item of a customer profile, but the present invention is not limited to this and other setting items may be used. [Industrial Applicability]

[0096] The present invention can be applied to an operation management system that can change the operation of the system according to each procedure described in an operation template. [Explanation of symbols]

[0097] 100...customer system, 101...operation management system, 110...operation management program, 111...management table group, 131...operation template validity judgment section, 130...setting item validity judgment section, 201...operation template management table, 211...namespace management table, 301...customer profile management table, 311...procedure management table.

Claims

1. an operation template management table for managing a plurality of operation templates each describing at least one procedure for managing the operation of the system; a conflict determination unit that determines whether or not execution of a specific procedure included in a specific operation template among the plurality of operation templates will cause a conflict that will interfere with the execution of other procedures included in other operation templates among the plurality of operation templates; a presentation unit that presents information about the specific procedure to an outside before the specific procedure is actually executed when the conflict determination unit determines that the execution of the specific procedure will cause the conflict; and An operation management system comprising:

2. an attribute management table for managing information on whether the attribute of the system operation is a changeable attribute or an attribute of the system operation is an unchangeable attribute; The conflict determination unit When the result of referring to the attribute management table shows that the specific procedure described in the specific operation template is a procedure that attempts to change the operation of the system despite the attribute not allowing the operation of the system to be changed, it is determined that the procedure will cause the conflict.

2. The operation management system according to claim 1 .

3. The attribute management table includes: Manage each procedure included in at least one of the plurality of operational templates managed by the operational template management table.

2. The operation management system according to claim 1 .

4. The presentation unit is When the conflict determination unit determines that the execution of the specific procedure will cause the conflict, the specific procedure and information about the system in which the specific procedure is to be executed are presented to the outside.

2. The operation management system according to claim 1 .

5. a priority management table for managing which of the other procedures causing the conflict and the specific procedure should be given priority when the conflict determination unit determines that the conflict will occur, The conflict determination unit When it is determined that the execution of the specific procedure will cause the conflict, the priority management table is referenced and the presentation unit is caused to present a priority.

2. The operation management system according to claim 1 .

6. managing setting items for managing the operation of the system, the setting items being provided with a profile including setting items indicating attributes of the system and setting values ​​of the setting items; The conflict determination unit A determination is made as to whether or not a conflict that may cause a hindrance to the execution of a procedure included in a part of the operation templates among the plurality of operation templates occurs due to an update of a setting value of a specific setting item of the profile.

2. The operation management system according to claim 1 .

7. a namespace management table for managing a constraint condition that does not allow the same namespace to be duplicated with respect to the namespace related to the setting value of the setting item; The conflict determination unit determining whether or not there is a violation of the constraints as a result of referring to the namespace management table; When the conflict determination unit determines that a violation exists, the presentation unit presents at least the setting values ​​of the setting items.

7. The operation management system according to claim 6.

8. and a validity determination unit that, when it is determined by the conflict determination unit that there is a violation of the constraint condition, determines whether or not it is possible to set a setting value that avoids duplication for the setting item, and when it is determined that it is possible to set the setting value, sets the setting value for the setting item. The operation management system according to claim 7 .

9. a conflict determination step in which a conflict determination unit of the operation management system determines whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates, each of which describes at least one procedure for managing the operation of the system, will cause a conflict that may interfere with the execution of other procedures included in other operation templates among the plurality of operation templates; a presentation step of a presentation unit of the operation management system presenting information about the specific procedure to an outside before the specific procedure is actually executed when the conflict determination unit determines that the execution of the specific procedure will cause the conflict; 13. An operation management method comprising:

10. a conflict determination step of causing a conflict determination unit of the operation management system to determine whether or not execution of a specific procedure included in a specific operation template among a plurality of operation templates, each of which describes at least one procedure for managing the operation of the system, causes a conflict that may interfere with the execution of another procedure included in another operation template among the plurality of operation templates; a presentation step of causing a presentation unit of the operation management system to present information about the specific procedure to an outside before the specific procedure is actually executed when the conflict determination unit determines that the execution of the specific procedure will cause the conflict; 2. An operation management program for executing the above on a computer.

Images