WO2018047325A1

WO2018047325A1 - Management machine for managing computer system to be managed, method, and computer program

Info

Publication number: WO2018047325A1
Application number: PCT/JP2016/076765
Authority: WO
Inventors: 香緒里仲野; 崇之永井; 裕教江丸
Original assignee: 株式会社日立製作所
Priority date: 2016-09-12
Filing date: 2016-09-12
Publication date: 2018-03-15
Also published as: JP6748724B2; JPWO2018047325A1

Abstract

During execution of a configuration change or a setting change for a computer system, when a problem occurs in the computer system, whether the problem has occurred due to the influence of the configuration change or the setting change or not is determined. A rule defining an influence event of the configuration change or the setting change is defined for each type of the configuration change or the setting change. When a problem occurs in the computer system, the influence event due to the configuration change or the setting change being executed is identified on the basis of configuration information relating to the computer system, parameters of the configuration change or the setting change, and an execution state of the configuration change or the setting change.

Description

Management machine, method, and computer program for managing a computer system to be managed

The technology disclosed in this specification relates to a management computer that manages a computer system.

In the management of a computer system, it is required that the devices constituting the computer system, their components, and the services provided by the computer system continue to operate normally. For this reason, recovery processing and prevention processing may be executed in order to solve a problem when a problem occurs in the computer system and to prevent the problem from occurring. For example, if a problem occurs in which the performance of a device that constitutes a computer system is abnormally reduced, the configuration or setting of the device or software may be changed based on the past performance values of the software running on that device. The problem may be resolved. Also, configuration changes are frequently made to provide new services. In recent years, these changes may be implemented without stopping services provided by the computer system.

Therefore, if a problem with the computer system or the service provided is detected during the execution of the change, it may be necessary to take action such as interrupting or reviewing the operation to change the series of configurations (hereinafter referred to as the change process). is there. Whether or not to interrupt the change process must be determined by the administrator of the computer system based on whether or not the problem that has occurred is due to the effect of the change process.

The influence of the change process is, for example, a decrease in the performance of the device or software caused by the load on the device or the consumption of resources that occurs when the change process is executed. However, the configuration of a computer system in recent years is large and complicated, and the influence caused by the contents of the configuration change and the setting change and the progress is different. For this reason, it is difficult to determine whether the change event should be identified and whether the change process should be interrupted or reviewed. For this reason, the computer system administrator may make an erroneous determination such as interrupting a change process that does not need to be interrupted.

JP2009-217587 WO2015 / 040688

According to the technique disclosed in Patent Document 1, in the field of batch job management of batch processing, there is a technique for interrupting specific processing according to the state of computer resources used by the batch job. However, in the technique disclosed in Patent Document 1, the computer resources consumed by the batch processing and the batch job constituting the batch processing are fixed, whereas in the case of a computer system change process, the contents of the processing to be executed and the execution The affected range and event vary depending on the target and the execution state of the process.

According to one embodiment of the present invention, a management computer that manages a computer system to be managed has a central processing unit and a storage device. The storage device includes configuration information relating to a configuration of a component constituting the management target computer system and change process information relating to a change process for changing a configuration of the component of the management target computer system. Change process information including a task and parameters to be executed, an influence rule for specifying an influence event generated by executing the task for each task type, and an execution status of the task constituting the change process. The central processing unit is configured to identify an influence event for each task when the change process is executed based on a task type of the task constituting the change process information and the influence rule, and an execution status of the task A task that is being executed is specified based on the above, and an influence event of the task that is being executed is specified.

According to the present invention, when a problem occurs in the computer system, the change process of the computer system can be appropriately managed in consideration of the influence of the change process.

1 schematically shows an embodiment of the present invention. 1 illustrates an example of exemplary hardware and logical configurations to which the method and apparatus of the present invention can be applied. 3 shows an exemplary data structure of a performance information table according to the first embodiment. 2 shows an exemplary data structure of a configuration information table according to the first embodiment. An exemplary data structure of change process DB of a 1st embodiment is shown. An exemplary data structure of change process DB of a 1st embodiment is shown. 3 shows an exemplary data structure of an influence rule table according to the first embodiment. 3 shows an exemplary data structure of an influence event management table according to the first embodiment. 3 shows an exemplary data structure of a change process status table of the first embodiment. The example of a process of the influence analysis program of 1st Embodiment is shown. The processing example of the change process influence management program of 1st Embodiment is shown. An example of the change process management screen which a display program of a 1st embodiment displays on a display is shown. 3 shows an exemplary data structure of a change process status table of the first embodiment. An example data structure of a control rule template table of a 2nd embodiment is shown. 6 illustrates an exemplary data structure of a control rule according to the second embodiment. The process example of the control rule production | generation program of 2nd Embodiment is shown. The processing example of the system information management program of 2nd Embodiment is shown. The process example of the change process control program of 2nd Embodiment is shown. The example of the change process management screen which the display program of 2nd Embodiment displays on a display is shown. An example data structure of an influence rule table of a 3rd embodiment is shown. An example data structure of an influence event management table of a 3rd embodiment is shown. The example data structure of the control rule template table of 3rd Embodiment is shown. The example data structure of the control rule template table of 3rd Embodiment is shown. The process example of the change process influence management program of 3rd Embodiment is shown. 6 illustrates an exemplary data structure of a control rule according to a third embodiment. An example of the change process management screen which a display program of a 3rd embodiment displays on a display is shown. 3 shows an exemplary data structure of a performance increase rate table. An example of a condition in the case where “the magnitude of influence by a task” is added to the condition part of the control rule template is shown.

In the following detailed description of the present invention, reference is made to the accompanying drawings that form a part of the disclosure, which illustrate exemplary embodiments in which the present invention may be practiced and are not intended to limit the present invention. In these drawings, the same reference numerals denote the same components throughout the drawings. Further, while the detailed description provides various exemplary embodiments, as described and illustrated below, the present invention is not limited to the embodiments described and illustrated herein, and is understood by those skilled in the art. It should be noted that the present invention can be extended to other embodiments known or later known.

References herein to “this embodiment” are intended to mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, the appearance of these phrases in various places in this specification does not necessarily indicate the same embodiment.

In the following detailed description, numerous specific details are disclosed in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that not all of these specific details are required in order to practice the present invention. In other circumstances, well-known structures, materials, circuits, processes, and interfaces may not be described in detail and / or shown in block diagram form in order not to obscure the present invention unnecessarily.

Furthermore, the following detailed description is shown as an algorithm and symbolic representation of the internal operation of the computer. These algorithmic descriptions and symbolic representations are the means used by those skilled in the data processing arts to effectively convey the substance of their invention to others skilled in the art. An algorithm is a series of defined steps that reach a desired final state or result. In the present invention, the steps performed require physical manipulation of tangible quantities to achieve tangible results.

Usually, but not necessarily, these quantities are in the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, to refer to these signals as bits, values, elements, symbols, characters, items, numbers, instructions, or the like because of their common use in principle. However, it should be noted that all of these and similar items are to be associated with appropriate physical quantities and are merely convenient labels attached to these physical quantities.

Unless specifically stated otherwise, terms such as “process”, “calculate”, “calculate”, “determine”, “display” and the like will be understood throughout the present specification, as will be apparent from the following description. The description used is to manipulate data represented as physical (electronic) quantities in a computer system or in the computer system's registers and memory to store, transmit or transmit information in the computer system's memory or registers or other information. Operation and processing of other information processing devices that convert into other data similarly expressed as physical quantities in the display device may be included.

The present invention also relates to an apparatus for performing the operations in this specification. The apparatus may be specially constructed for the required purposes, or may include one or more general purpose computers that are selectively activated or reconfigured by one or more computer programs. Such a computer program can be stored, for example, on a computer readable storage medium such as an optical disk, magnetic disk, read only memory, random access memory, solid state device and drive, or any other medium suitable for storing electronic information. However, it is not limited to these.

The algorithms and displays shown herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs and modules in accordance with the teachings herein, but it may prove convenient to construct a more specialized apparatus for performing the desired method steps. The structure of these various systems will become apparent from the description disclosed below. The present invention also does not assume any specific programming language. It will be appreciated that various programming languages may be used to implement the teachings of the invention, as described below. Program language instructions may be executed by one or more processing units, eg, a central processing unit (CPU), a processor, or a controller.

In the following description, the information of the present invention will be described using expressions such as “aaa table”, “aaa list”, “aaaDB”, etc., but these information are expressed in other than data structures such as tables, lists, relational databases, etc. It may be. Therefore, “aaa table”, “aaa list”, “aaaDB”, etc. may be referred to as “aaa information” in order to show that they do not depend on the data structure.

Furthermore, in describing the contents of each information, the expressions “identification information”, “name”, and “ID” are used, but these can be replaced with each other.

In the following description, there is a case where “program” is used as the subject. However, since the program performs processing determined by being executed by the processor using the memory and the communication port (communication control device), the processor is used as the subject. The explanation may be as follows. Further, the processing disclosed with the program as the subject may be processing performed by a computer such as a management server or an information processing apparatus. Further, part or all of the program may be realized by dedicated hardware.

Various programs may be installed in each computer by a program distribution server or a storage medium that can be read by the computer.

The management computer has input / output devices. Examples of input / output devices include a display, a keyboard, and a pointer device, but other devices may be used. As an alternative to an input / output device, a serial interface or an Ethernet interface is used as an input / output device, a display computer having a display or a keyboard or a pointer device is connected to the interface, and display information is transmitted to the display computer. By receiving the input information from the display computer, the display computer may perform the display, or the input may be replaced by the input / output device by receiving the input.

Hereinafter, a set of one or more computers that manage a computer system and display information for display may be referred to as a management system. When the management computer displays the display information, the management computer may be a management system. The management system may be a combination of the management computer and the display computer. In addition, in order to increase the speed and reliability of management processing, multiple computers may perform processing equivalent to that of the management computer. In this case, these multiple computers (for display when the display computer performs display) (Including computers) may be a management system. “Displaying display information” by the management computer may mean displaying the display information on a display device included in the management computer, or the management computer (for example, a server) may be a remote display computer (for example, a client). ) May be transmitted to display information. Also, in the following description, when the same type of element is described separately, the reference numeral of the element is used, and when the same type of element is not distinguished, the common parent of the reference numerals of the element is used. A sign may be used. For example, the server 202 may be described when the server is not particularly distinguished, and may be described as the servers 202a and 202b when the individual server is described separately.

In the following description, one or a plurality of operations for changing the configuration and one or a plurality of operations for changing the setting applied to the computer system for a certain purpose are referred to as a “change process”. Called. Furthermore, each change operation constituting the change process is called a “task”, and a setting value set for the task to execute the task is called a “parameter”.
<< First Embodiment >>

According to the present embodiment, in the management of the devices constituting the computer system, when the change process is started with respect to the device and software, the device that displays the influence event due to the change process according to the progress of the change process, Methods and computer programs are provided.

In this embodiment, the influence event of the change process is determined by the progress status of the change process, the rule for determining the influence event caused by the change process, and the execution contents of the change process.

FIG. 1 is a diagram showing an outline of a computer system in this embodiment.

According to the present embodiment, the management computer 201 is a computer that manages at least one device that constitutes the management target computer system 101. The devices that constitute the management target computer system 101 include, for example, a computer represented by a server and a network device represented by an IP (Internet Protocol) switch. Moreover, in the field of IoT (Internet of Things), it may be a device connected to the Internet or a device (IoT device) attached with a computer. In addition, logical or physical elements included in one managed device include, for example, a port, a processor, a storage resource, a physical storage device, a program, and a virtual machine.

In this embodiment, the storage area of the management computer 201 stores data in the following table format, for example.

The configuration information table 400 is a table that stores configuration information of the management target computer system collected by the system information management program 221. The change process DB 500 is a table that stores tasks that constitute a change process to be executed and parameters thereof. The task and its parameters may be, for example, an API for operating devices and software constituting the computer system and its arguments. The change process may be a script that executes an API. The influence rule table 600 stores a task and an influence phenomenon exerted by the task in a format that does not depend on a task execution target. The change process status table 800 stores the change process being executed and the progress of the task.

Hereinafter, an outline of processing in the present embodiment will be described.

The management computer 201 activates the impact analysis program 222 when a change process to be newly executed is registered in the change process DB 500. The influence analysis program 222 derives the influence phenomenon of each task constituting the registered change process from the influence rule table 600. Then, the impact analysis program 222 stores the configuration information of the computer system related to the registered change process and the impact events of each task constituting the derived change process in the impact event management table 700. The change process influence management program 225 has an influence event according to the progress of the change process as information for determining control (for example, suspension) of the change process based on the change process status and the influence event management table 700. Is displayed.

In the present embodiment, when a problem in a computer system (for example, an abnormal decrease in performance of a service provided by an apparatus constituting a computer system or a computer system) is detected, the change process causes the change process according to the progress of the change process. Impacting events are identified. This identified impact event may be displayed as requested by the computer system administrator. As a result, the administrator can compare the content of the detected problem with the influence event caused by the change process, and check whether the problem that has occurred is caused by the influence event of the change process. That is, the administrator can appropriately control the change process in a short time.

Hereinafter, the first embodiment will be described in detail.
<Configuration of computer system and management computer>

FIG. 2 shows a configuration example of the computer system and the management computer 201 according to the first embodiment. The computer system includes one or more physical servers (or other computers) 230a, 230b, and 230c. The physical server 230 is communicably connected via a network 220 such as a LAN (local area network).

The management computer 201 includes a CPU 211, a memory 212, a disk 213, an input device 214, a network interface device (network I / F) 215, and an output device 217, and a general-purpose computer to which these devices are connected via a system bus 216. It's okay. The disk 213 is, for example, an HDD (Hard Disk Drive), but another nonvolatile storage device such as an SSD (Solid State Drive) may be employed instead. As logical modules of the management computer 201, for example, a system information management program 221, an influence analysis program 222, a change process status management program 223, a control rule generation program 224, a change process influence management program 225, a display program 226, and a change process control program 227 Have. The management computer 201 also includes, for example, a performance information table 300, a configuration information table 400, a change process DB 500, an influence rule table 600, an influence event management table 700, a change process status table 800, and a control rule template table 900.

The performance information table 300 and the configuration information table 400 are databases that store performance information and configuration information of managed devices collected from the managed devices by the system information management program 221 and physical and logical elements constituting the managed devices. is there. The performance information table 300 and the configuration information table 400 are not included in the management computer 201, but may be held by each management target device. In that case, when referring to the configuration information or the performance information, the management computer 201 may access each managed device via the network 220 and acquire the information.

The system information management program 221, the influence analysis program 222, the change process status management program 223, the control rule generation program 224, the change process influence management program 225, the display program 226, and the change process control program 227 are stored in the memory 212 and the CPU 211 It is executed by. The performance information table 300, the configuration information table 400, the change process DB 500, the influence rule table 600, the influence event management table 700, the change process status table 800, the control rule template table 900, and the like are stored in the disk 213. At least one of these programs or at least one data may be stored in another appropriate storage area that the CPU 211 can refer to.

The details of the control rule generation program 224, the change process control program 227, and the control rule template table 900 described in FIG. 2 will be described in the second embodiment.

The network I / F 215 acquires information on the device and its components, such as configuration information and performance information, from a management target device such as the physical server 230 connected via the network 220. The output device 217 is a device that outputs (typically displays) information from the display program 226. The input device 214 is a device that accepts user instruction input. For example, a keyboard, a pointer device, or the like can be used as the input device 214, and a display, a printer, or the like can be used as the output device 217, but other devices may be used.

The physical server 230 may be a managed device that executes a program such as an application. The server 230 may be a general-purpose computer including a memory 232, a network I / F 233, and a CPU 231 connected thereto. The physical server 230 may have a nonvolatile storage device such as an HDD in addition to the memory 232. The physical server 230 may include a hypervisor 235 that can logically generate and execute the virtual machine 234. The hypervisor 235 can control a plurality of virtual machines 234 at a time. Each virtual machine 234 can execute an application program as if it were a stand-alone physical computer by dividing and allocating computer resources such as the CPU 231 and the memory 232 of the physical server 230 by the hypervisor 235.

The hypervisor 235 monitors the configuration and performance of the physical server 230 and the virtual machine 234. The hypervisor 235 may further have a function of transmitting configuration information and performance information of the physical server 230 and the virtual machine 234 via the network 220 when requested by the management computer 201.

As means for collecting the configuration information and performance information of the managed computer system including the physical server 230, the physical server 230 has a monitoring agent (program) instead of collecting the information that the hypervisor 235 has. The agent may transmit at an arbitrary timing.

The hypervisor 235 may have a virtual machine (VM) live migration function of moving a virtual machine 234 operating on a physical server 230 to another physical server 230 while operating.
<Performance information table>

The performance information table 300 stores performance information of a management target device or its constituent elements (hereinafter, the management target device and constituent elements may be collectively referred to as a management target component). This performance information may be collected by the system information management program 221 from the hypervisor 235 or the like or a monitoring agent. The system information management program 221 may start processing periodically and update the information in the performance information table 300. Alternatively, the system information management program 221 may start processing at the timing when the performance information is transmitted from the monitoring agent to the management computer 201, and the information in the performance information table 300 may be updated.

FIG. 3 is a diagram for explaining an example of the data structure of the performance information table 300.

The performance information table 300 includes five fields, that is, a component ID 301, a metric type 302, a time 303, a performance value 304, and a status 305.

The component ID 301 stores a value that uniquely identifies the managed component. The metric type 302 stores a value for identifying the performance observation item of the managed component. The time 303 stores the time when the performance of the managed component is observed. The performance value 304 stores a value observed as the performance of the managed component. The performance value 304 may store a unit together with a numerical value. The status 305 stores a determination result as to whether the observed value is abnormal. An example in which the determination result “abnormal” is stored in the status 305 may be a case where the value stored in the performance value 304 exceeds a preset static threshold for each metric type. Further, when a performance value threshold is set in advance for each metric type and managed component pair, it may be determined as “abnormal” when the observed performance value exceeds the threshold. The threshold value may be calculated dynamically. For example, for a specific metric type of a specific managed component, a dynamic threshold value may be set based on a past performance value for a certain period. Furthermore, in this embodiment, only “normal” and “abnormal” are defined as identification information indicating the status, but three or more statuses are defined by defining a plurality of threshold values for one metric type. May be. In the present embodiment, a combination of a managed component and a metric type stored as “abnormal” in the status 305 is detected as a problem occurring in the managed computer system 101, and the system information management program 221 notifies the administrator. This may be notified using the mail function or the output device 217.

For example, the entry 314 in FIG. 3 indicates the following contents. That is, for the observation item (here, the usage rate of the CPU 231b) identified by “PS / CPU / Utilization” of the management component (here, the physical server 230b in FIG. 2) identified by the identifier “PS2”. A performance of “90%” was observed at 2016/01/01/0: 00. The performance value is “abnormal” based on a certain determination condition, and is detected as a problem occurring in the managed computer system 101.
<Configuration information table>

The configuration information table 400 stores configuration information of managed devices acquired by the system information management program 221 from the hypervisor 235 or the like. The configuration information includes related information indicating the connection relationship, dependency relationship, and the like between the management target device and its components. The system information management program 221 may start processing periodically and update or add information in the configuration information table 400. Alternatively, the system information management program 221 may start processing at the timing when it is transmitted from the monitoring agent to the management computer 201, and the information in the configuration information table 400 may be updated.

FIG. 4 is a diagram illustrating an example of the data structure of the configuration information table 400 that stores the configuration information of the physical server 230.

Note that the data representation format or data structure of each item stored in the configuration information table 400 may not be the same as the data representation format or data structure of the managed device. Further, when the management computer 201 receives each of these items from the management target device, it may be received in the data structure or data representation format of the management target device.

Also, the configuration information table 400 may be updated as the configuration of the managed component changes. When the information in the configuration information table 400 is updated, information before the update may be recorded and stored as history information so that past configuration information can be referred to.

The configuration information table 400 includes two fields, that is, a physical server ID 401 and a virtual machine ID 402. The physical server ID 401 stores a value that uniquely identifies the physical server. The virtual machine ID 402 stores a value that uniquely identifies the virtual machine. The values stored in the physical server ID 401 and the virtual machine ID 402 may be the same as the values stored in the component ID 301 of the performance information table 300 in FIG.

For example, the entry 411 in FIG. 4 includes a virtual machine identified by the identifier “vm1” on the physical server identified by the identifier “PS1” (here, the physical server 230a in FIG. 2), and “vm2”. The virtual machines identified by the identifier (here, the

virtual machines

234a and 234b in FIG. 2) are operating.

In the present embodiment, only the relationship between the physical server and the virtual machine is stored in the configuration information table 400, but the identification information of the components constituting the physical server, such as the CPU 231, the memory 232, and the network I / F 233, and those The specs and model of the may be stored. In addition, information on application programs operating on a physical server or a virtual machine may be stored.
<Change process DB>

The change process DB 500 stores information related to a change process that is scheduled to be executed, is being executed, or has been executed for the managed computer system 101. The change process consists of tasks and parameters.

In this embodiment, a task is a minimum unit of a configuration change operation or a setting change operation to be executed for a management target device and a program operating on the device. That is, a task is the minimum unit of a configuration or setting change operation that can execute control processing such as interruption processing when controlling a change process. For example, the task may be an API or command for configuration / setting change, a program for executing configuration / setting change, or a minimum unit of configuration / setting change operation executed by an administrator. The parameter may be an API, a command or program argument, or a setting value input in an operation executed by the administrator. A change process is a process consisting of one or more tasks executed on a computer system for a certain purpose. The change process may be defined by an API, a command or a script for executing a program, an orchestration software workflow represented by vRealize Orchestrator (registered trademark), or an operation procedure or plan executed by an administrator. .

The value stored in the change process DB 500 may be stored by the management computer 201 analyzing the script. Alternatively, the management computer 201 may acquire workflow information from the orchestration software and store it. Or it may input according to the procedure manual of the operation etc. which an administrator performs. Alternatively, the management computer 201 may acquire and store plan information derived by the configuration change plan generation function represented by Patent Document 2.

The administrator may input whether or not the process is scheduled to be executed or whether it is a change process that is being executed. Alternatively, when the execution scheduler function of batch job management software or orchestration software is used, information may be acquired from the scheduler function to determine the execution state of the change process.

In the present embodiment, information related to the change process is stored in the change process DB 500 of the storage area of the management computer 201. However, a method of acquiring information from a script file, orchestration software, etc. at the timing of using the information may be used. .

5A and 5B are diagrams for explaining an example of the data structure of the change process DB 500. FIG.

In this embodiment, VM live migration is given as an example of a task that constitutes a change process. Therefore, in this embodiment, the change process DB 500 includes a change process list table 591 that stores a change process list and a VM live migration parameter table 592 that stores parameters of VM live migration tasks that constitute the change process. .

As shown in FIG. 5A, the change process list table 591 includes four fields, that is, a change process ID 501, a task ID 502, a task type 503, and a parameter ID 504. The change process ID 501 stores a value that uniquely identifies the change process. The task ID 502 stores a value that uniquely identifies the task. In the present embodiment, even if the contents of the change process and the contents of the task are the same, different IDs are assigned to the change processes or tasks executed at different timings. For example, if the change process is a script and the task included in the change process is an API, even if the contents of the script file to be executed, that is, the API described in the script and the arguments passed to the script are all the same, When the scripts are executed in different scenes, different IDs are assigned to each other. The task type 503 stores a value for identifying the type of task. The task type is information for determining which API or command is used, for example. The parameter ID 504 stores a value that uniquely identifies a combination of one or more parameters used in the task.

For example, the entry 511 in FIG. 5A indicates that the change process identified by the identifier “Proc1” includes two tasks identified by the identifiers “Task1” and “Task2”. Furthermore, these two tasks belong to the type identified by the identifier “VM_LiveMigration” (here, VM live migration), and the parameters identified by “Param1” and “Param2” may be passed to the two tasks, respectively. It is shown.

As shown in FIG. 5B, the VM live migration parameter table 592 includes four fields, that is, a parameter ID 521, a migration virtual machine ID 522, a migration destination physical server ID 523, and a migration source physical server ID 524.

The parameter ID 521 stores information for uniquely identifying a set of one or more parameters to be passed to one task. The value stored in the parameter ID 521 may be equal to the value stored in the parameter ID 504 of the change process list table 591, for example. The migration virtual machine ID 522 stores a value that uniquely identifies a virtual machine to be migrated in one VM live migration task. The value stored in the migration virtual machine ID 522 may be equal to, for example, the value stored in the virtual machine ID 402 of FIG. The migration destination physical server ID 523 stores a value that uniquely identifies the migration destination physical server of the virtual machine designated by the migration virtual machine 522. The value stored in the migration destination physical server ID 523 may be equal to the value stored in the physical server ID 401 in FIG. 4, for example. The migration source physical server ID 524 stores a value that uniquely identifies the migration source physical server of the virtual machine designated by the migration virtual machine 522. The value stored in the migration source physical server ID 524 may be equal to, for example, the value stored in the physical server ID 401 in FIG.

Note that parameters of tasks other than the task type “VM_LiveMigration” may be stored in a separate table. In that case, each set of parameters may be uniquely identified by a parameter ID.

For example, the entry 511 in FIG. 5A indicates that the set of parameters specified for the VM live migration task identified by “Task1” is “Pram1”. Furthermore, in the entry 531 in FIG. 5B, the virtual machine to be moved is “vm1” (here, the virtual machine 234a in FIG. 2) in the VM live migration executed by “Task1”, and the destination physical server is “ PS2 "(here, physical server 230b in FIG. 2), and the source physical server is" PS1 "(here, physical server 230a in FIG. 2).
<Influence rule table>

The influence rule table 600 stores a rule for deriving an influence phenomenon for each task constituting the change process registered in the change process DB 500. In the present embodiment, as one example of the influence event, the performance of the managed component whose value fluctuates when affected by one task is given. This is an example, and the impact event is not limited to the performance of the managed component. The influence event may be an event that can be observed by the administrator of the management computer 201 or the computer system 101. For example, it may be status information expressed by “success” or “failure” of another task.

In this embodiment, the influence event is a set of a managed component and a performance metric type that one task affects, but may be expressed using other information.

FIG. 6 is a diagram for explaining an example of the data structure of the influence rule table 600.

The influence rule table 600 includes four fields, that is, a rule ID 601, a task type 602, an influence component information acquisition query 603, and an influence metric type 604.

The rule ID 601 stores a value for uniquely identifying the influence rule. The task type 602 stores a value for identifying the type of task to which the influence rule is applied. The value stored in the task type 602 may be equal to the value stored in the task type 503 in FIG. 5A, for example. The influence component information acquisition query 603 stores a query for acquiring information on managed components that a certain task affects. In the present embodiment, as an example of information stored in the affected component information acquisition query 603, an SQL statement that is acquired from the configuration information table 400 or the change process DB 500 and acquires the ID of the component that the task affects is given. ing. “@Param” in the SQL statement is a variable, and indicates that a value stored in the parameter ID 504 of the change process list table 591 in FIG. 5A is substituted. In the present embodiment, the SQL statement is given as an example of means for acquiring information on components affected by a task, but other acquisition means may be used. The information acquisition source is not limited to the information recorded in the storage area of the management computer, and may be the management target computer system 101, the hypervisor 235 that manages execution of the VM live migration, or orchestration software that manages the change process, or the like. Good. The influence metric type 604 stores a value that uniquely identifies the metric type that a certain task affects. The value stored in the influence metric type 604 may be, for example, a value equal to the metric type 302 in FIG.

For example, the entry 611 in FIG. 6 indicates that in the influence rule of the identifier “ImpactRule1”, the application target of the influence rule is a task belonging to the type identified by the identifier “VM_LiveMigration”. Information on the management target component affected by the task is acquired from the migration destination physical server ID 523 of the VM live migration parameter table 592 based on the parameter ID of the task. Further, the entry 611 indicates that the metric type affected by the task is the metric type identified by the identifier “PS / CPU / utilization”.
<Influence event management table>

The influence event management table 700 stores information on the influence event of each task derived based on the influence rule stored in the influence rule table 600 of FIG. In this embodiment, the impact event is expressed as a set of the ID of the managed component affected by one task and the metric type that is an observation item of performance, but may be expressed as other information. . The impact event may be other than the performance of the managed component.

FIG. 7 is a diagram for explaining an example of the data structure of the influence event management table 700.

The impact event management table 700 includes seven fields, that is, an ID 701, a change process ID 702, a task ID 703, a task type 704, an impact component ID 705, an impact metric type 706, and a status 707.

ID 701 stores a value that uniquely identifies a set of task and impact event. The change process ID 702 stores a value that uniquely identifies the change process. The value stored in the change process ID 702 may be a value equal to the value stored in the change process ID 501 of the change process list table 591 in FIG. 5A, for example. The task ID 703 stores a value that uniquely identifies the task. The value stored in the task ID 703 may be a value equal to the value stored in the task ID 502 of the change process list table 591 in FIG. 5A, for example. The task type 704 stores a value for identifying the type of task. The value stored in the task type 704 may be a value equal to the value stored in the task type 503 of the change process list table 591 in FIG. 5A, for example. The affected component ID 705 stores a value that uniquely identifies the managed component that is affected by the task indicated by the identifier stored in the task ID 703. The value stored in the affected component ID 705 may be, for example, a value equal to the value stored in the physical server ID 401 or the virtual machine ID 402 in the configuration information table 400 of FIG. The influence metric type 706 stores a value that uniquely identifies the metric type that the task indicated by the identifier stored in the task ID 703 affects. The value stored in the influence metric type 706 may be, for example, a value equal to the metric type 302 in FIG. The status 707 stores the determination result as to whether or not the performance value uniquely identified by the influence component ID 705 and the influence metric type 706 is abnormal. The value stored in the status 707 may be equal to, for example, the value stored in the status 305 of the performance information table 303 in FIG. In addition, whenever the system information management program 221 collects performance information of managed components and updates the performance information table 300, the value of the status 707 may be updated together.

For example, entry 711 in FIG. 7 indicates that the impact event identified by “Impact1” has the following contents. That is, in the change process “Proc1”, the event that “Task1” whose task type is “VM_LiveMigration” affects “VM3” of the virtual machine (here, the virtual machine 234c in FIG. 2) identified by “vm3”. It indicates a metric identified by “CPU / contention” (here, CPU contention rate of VM). Further, the entry 711 indicates that the current performance value of “VM / CPU / contention” is “abnormal”.

In this embodiment, the impact event is stored and managed in a table, but the information corresponding to the information in the impact event management table is generated each time using the impact rule and the performance information table 300 at a necessary timing. May be.
<Change process status table>

The change process status table 800 stores information on the progress status of the change process and tasks monitored by the change process status management program 223. The task progress status may be acquired from the hypervisor 235 when the task to be executed is VM live migration. In the case of another type of task, it may be acquired from a program that manages each task.

Also, when the change process is executed by the orchestration software, the progress status may be acquired from the orchestration software. Further, the progress status may be derived based on the information related to the execution contents of the change process stored in the change process DB 500 and the change in the configuration information of the management target computer system 101.

The change process status management program 223 may register a new entry in the change process status table 800 when a new change process is registered in the change process DB 500.

FIG. 8 is a diagram for explaining an example of the data structure of the change process status table 800.

The change process status table 800 includes five fields, that is, ID 801, change process ID 802, change process status 803, task ID 804, and task status 805. The ID 801 stores a value that uniquely identifies an entry in the change process status table 800. The change process ID 802 stores a value that uniquely identifies the change process. The value stored in the change process ID 802 may be, for example, a value equal to the value stored in the change process ID 501 of the change process list table 591 in FIG. 5A. The change process status 803 stores a value for identifying the execution status of the change process. In the present embodiment, the execution status of the change process may be divided into three states of “completed”, “under execution”, and “not executed”, and identification information indicating these may be stored in the change process status 803. The task ID 804 stores a value that uniquely identifies the task. The value stored in the task ID 804 may be equal to the value stored in the task ID 502 of the change process list table 591 in FIG. 5A, for example. The task status 805 stores a value that identifies the execution status of the tasks that constitute the change process. In the present embodiment, the task execution status may be divided into three states of “completed”, “being executed”, and “not executed”, and identification information indicating these may be stored in the task status 805.

For example, in the entry 812, the execution status of the change process identified by the identifier “Proc1” is “executing”, and the task identified by “Task2” among the tasks constituting the change process “Proc1” Indicates that it is “running”.
<Effect analysis program processing>

The impact analysis program 222 identifies the impact event due to the change process and the task based on the information in the configuration information table 400, the change process DB 500, and the impact rule table 600, and registers the information in the impact event management table 700.

FIG. 9 is a flowchart of an example of processing of the influence analysis program of the first embodiment.

The impact analysis program 222 may start this process when new change process information is registered in the change process DB 500. Further, this process may be started at the timing when the information of the change process is updated in the change process DB 500. The new change process information is registered in the change process DB 500 or the information of the registered change process is updated, and then explained in the control rule generation program 224, the change process influence management program 225, or the second embodiment. This process may be started at an arbitrary timing until the change process control program 227 to be started is started. In addition, if the task being executed is for executing a configuration change of the managed computer system 101, the influence of other tasks may also change depending on the completion of the task, so that each time one task is completed. This process may be started.

In step S901, the impact analysis program 222 acquires an entry from the change process list table 591 of the change process DB 500. The entries to be acquired may be all entries, a newly registered entry, an updated entry, or an entry having a change process ID equal to the updated entry.

Note that when the updated entry or all entries are acquired and the subsequent processing proceeds, the acquired change process DB among the entries in the impact event management table 700 is updated in order to update the information on the impact event. An entry related to the entry may be deleted.

In step S902, the impact analysis program 222 repeats the processing in steps S903 to S909 for all the entries in the change process DB 500 acquired in step S901.

In step S903, the impact analysis program 222 acquires from the impact rule table 600 an impact rule having a value equal to the task type 503 of the change process DB entry in the task type 602.

In step S904, the impact analysis program 222 repeats the processing in steps S905 to S909 for all the impact rules acquired in step S903.

In step S905, the impact analysis program 222 assigns the value stored in the parameter ID 504 of the change process DB entry to the variable of the impact component information acquisition query 603 of the impact rule, executes the query, and affects the task. All the identification information (influence component ID) of the managed component to be received is acquired.

In step S906, the influence analysis program 222 repeats the processes in steps S907 to S909.

In step S907, the impact analysis program 222 adds the ID 701 to the impact metric type 706 based on the information stored in the impact component ID, the impact rule, and the change process DB entry in the impact event management table 700. Register an entry that stores a value in each field.

In step S908, the impact analysis program 222 identifies from the performance information table 300 the entry having the component ID 301 and the metric type 302 having the values stored in the impact component ID 705 and the impact metric type 706 of the entry registered in step S907, The value stored in the status 305 of the entry is acquired.

In step S909, the influence analysis program 222 stores the value of the status 305 acquired in step S908 in the status 707 of the entry registered in step S907.

A specific example of the processing in FIG. 9 is as follows.

For example, when the entry 511 in FIG. 5A is acquired in step S901, the

entries

611 and 612 in FIG. 6 are acquired from the influence rule table 600. When the process is executed for the entry 611 in the repetitive process of step S904, the parameter ID “Param1” is substituted for the variable of the affected component information acquisition query 603 in step S905, and the query shown below is generated and executed. As the affected component ID, “PS2” is acquired from the migration destination physical server ID 523 of the VM live migration parameter table 592 of FIG. 5B.
SELECT destination physical server ID FROM VM_LiveMigration_Parameter
WHERE parameter ID = “Param1” (1)

In step S907, information from the ID 701 of the entry 711 to the influence metric type 706 in FIG. 7 is stored. In step S908, the entry 314 is acquired from the performance information table 300 in FIG. 3. In step S909, the entry 711 Information “abnormal” stored in the status 305 of the entry 314 is stored in the status 707.
<Processing of change process impact management program>

The change process impact management program 225 displays the impact event of the change process according to the progress of the change process based on the impact event management table 700 and the change process status table 800.

FIG. 10 is a flowchart of an example of processing of the change process influence management program 225 according to the first embodiment.

The change process influence management program 225 may start processing upon receiving an input of a display instruction by an administrator or the like. The opportunity for the administrator to input a display instruction may be that the system information management program 221 detects that a problem has occurred in the managed computer system 101 and notifies the administrator.

In step S1001, the change process influence management program 225 acquires all entries from the change process status table 800.

In step S1002, the change process influence management program 225 repeats the processes in steps S1003 to S1006 for the change process status entry acquired in step S1001.

In step S1003, the change process influence management program 225 acquires an entry having the value stored in the task ID 804 of the change process status entry as the task ID 703 from the influence event management table 700.

In step S1004, the change process influence management program 225 determines whether or not the value stored in the task status 805 of the entry of the change process status table 800 is “executing”. If the result of this determination is true (S1004: YES), the process proceeds to step S1005. If the result of this determination is false (S1004: NO), the process proceeds to step S1006.

In step S1005, the change process influence management program 225 stores the set of the entry of the change process status table 800 and the entry acquired from the influence event management table 700 in step S1003 in the memory as an “ongoing” group.

In step S1006, the change process influence management program 225 activates the display program 226, and based on the acquired entry of the change process status table 800 and the information stored in the memory in step S1005, the change process, task, and Is displayed on the output device 217 on the event that has an effect at the start of the change process influence management program 225.

A specific example of the processing in FIG. 10 is as follows.

For example, in step S1001, the change process influence management program 225 acquires all entries stored in the change process status table 800 of FIG. If the entry 812 is targeted in the repetitive processing in step S1002, the change process influence management program 225 acquires the entry 713 and the entry 714 in FIG. 7 in step S1003. In the determination process in step S1004, “execution” is stored in the task status 805 of the entry 812, and thus the process proceeds to step S1005. In step S1005, the change process influence management program 225 executes the entry 812 and the entry. A pair of 713 and 714 is recorded in the memory as an “ongoing” group, and in step S1006, a display program is started and information is displayed on the output device 217.

FIG. 11 shows an example of a screen displayed by the display program 226 in step S1006 in the first embodiment. The change process management screen 1100 shown in the figure is an example of a screen that displays the contents of the change process, the progress status, and the influence event based on the information acquired and stored by the change process influence management program 225.

The change process management screen 1100 may have a display area 1101 for displaying information for each change process. In addition, the display area 1101 may include three fields, that is, a change process name 1111, a change process status 1112, and a task and influence event display area 1113.

In the change process name 1111, the identification information of the change process may be displayed in a format that can be understood by the administrator based on the information of the change process ID 802 of the entry of the change process status table 800 acquired in step S 1001 of FIG. . In the change process status 1112, the progress of the change process may be displayed based on the information of the change process status 803 of the entry of the change process status table 800 acquired in step S1001 of FIG.

In the task and influence event display area 1113, information on the tasks constituting the change process and the influence events may be displayed. The display area 1113 may include five fields, that is, a task name 1121, an execution content 1122, a status 1123, an influence event 1124, and a performance status 1125. These five pieces of information may constitute and display one entry for each task constituting the change process.

In the task name 1121, task identification information may be displayed in a format that can be understood by the administrator based on the information of the task ID 804 of the entry in the change process status table 800 acquired in step S1001 of FIG. Execution content 1122 is displayed in a format in which information acquired from the change process DB 500 can be understood by the administrator based on the information of the task ID 804 of the entry in the change process status table 800 acquired in step S1001 of FIG. May have been. The status 1123 may display task status information based on the task status 805 information of the entry of the change process status table 800 acquired in step S1001 of FIG. In the influence event 1124, the influence event for each task may be displayed based on the entry information of the influence event management table 700 acquired in step S1003 of FIG. If the entry of the impact event management table 700 acquired in step S1003 is stored in the memory as an “ongoing” group in step S1005, an “ongoing” identifier is displayed as shown in the display area 1144. Or highlight it. In the performance status 1125, the status of the performance information indicated by the influence event may be displayed based on the information of the status 707 of the entry in the influence event management table 700 acquired in step S1003 of FIG. The performance status 1125 may be displayed only when the value of the status 707 of the entry in the influence event management table 700 is “abnormal”.

When the administrator displays “abnormal” in the performance status 1125 and the impact event displayed in the impact event 1124 belongs to the “ongoing” group, the administrator determines that the problem has occurred due to the effect of the change process. Then, a control process such as interrupting the change process may be executed. Therefore, in the display example of the change process management screen 1100 shown in FIG. 11, since the problem that has occurred is not due to the influence of the change process, the administrator can determine that the execution of the process of the change process should be continued.

The change process management screen 1100 shown in FIG. 11 is one embodiment, and it is not necessary to display all the information shown in FIG. For example, the change process name 1111 and the influence event displayed together with the identifier of “ongoing” in the influence event 1124 (that is, information on the entry of the influence event management table 700 stored in the memory as the “ongoing” group in step S1005) ) May be displayed.

In this embodiment, the change process influence management program 225 is executed in response to an input of a display instruction by an administrator or the like. However, the information acquired or derived in the memory by starting the processing periodically is recorded. When the display instruction input by the administrator or the like is received, the screen of FIG. 11 may be displayed on the output device 217 based on the information recorded in the memory.

In this embodiment, when the value of the status 707 of the entry in the influence event management table 700 of the influence event belonging to the “ongoing” group is “abnormal”, the change process displayed in the change process name 1111 is You may display that it is a candidate cause of the problem which occurred.

As described above, according to the first embodiment, execution is performed based on the influence rules that define the influence events of the computer system, which are affected by the tasks constituting the change process, for each task type and the progress of the change process. It is possible to identify the influence event of the change process in the middle according to the progress of the change process. As a result, when a problem occurs in the managed computer system, the administrator can determine whether the problem that has occurred is due to the effect of the change process that is being executed. Only can make decisions such as interrupting and reviewing the change process. That is, even if a problem occurs in the managed computer system, it is possible to prevent an administrator from making an erroneous determination such as interrupting a change process that does not need to be interrupted if it is not affected by the change process.
<< Second Embodiment >>

Next, a second embodiment will be described. In the following description, differences from the first embodiment will be mainly described, and descriptions of equivalent components, programs having equivalent functions, and tables having equivalent items will be omitted or simplified.

In the first embodiment, when a problem occurs in the managed computer system, the influence event of the computer system affected by the change process is displayed on the screen according to the progress of the change process, and the problem that the administrator has occurred. By comparing the displayed impact events, it was determined whether the problem was due to the impact of the change process and whether the change process should be interrupted.

However, whether or not the change process should be interrupted depends not only on whether or not the problem is caused by the influence of the change process, but also on the contents of the tasks constituting the change process and the progress of the task. For example, there are things that can be interrupted depending on the task type and those that are not. In addition, if the progress rate of the change process or task is equal to or greater than a certain value, the change process or task can be affected in a short time, so it may be appropriate to continue execution of the change process or task. These determinations require knowledge about the type of task (for example, VM live migration). For this reason, an administrator who does not have detailed knowledge about the task may make a mistake in determining whether or not the control process of the change process is necessary only with the method exemplified in the first embodiment, or it may take time to make a determination. May take. The change process control process is, for example, a change process interruption process. In addition, in the method shown in the first embodiment, since it is necessary to make an administrator's judgment in determining whether or not to execute the control process of the change process, the control process of the change process is automatically determined and executed by software. Can not do it.

In the second embodiment, an example will be described in which execution is performed up to the determination of the necessity of control processing of the change process.

The same performance information table 300, configuration information table 400, change process DB 500, influence rule table 600, and influence event management table 700 as those used in the description of the second embodiment are used. The configuration of each table is the same as in the first embodiment.

In the second embodiment, the control rule template table 1300 of FIG. 2 is added as new data and the change process status table 800 is changed to explain the process for determining the control process of the change process. In addition, a control rule generation program 224 and a change process control program 227 are added as new programs, and processing executed by the system information management program 221 is added. In the second embodiment, the control rule generation program 224 generates new information called control rule information 1400.
<Change Process Status Table of Second Embodiment>

FIG. 12 is a diagram for explaining an example of the data structure of the change process status table 800 in the second embodiment.

The configuration of the change process status table 800 in the second embodiment is substantially the same as the configuration of the change process status table 800 in the first embodiment. The change process status table 800 has five fields, that is, an ID 801, a change process ID 802, a change process status 803, a task ID 804, and a task status 805, in order to store information related to the change process or task execution status. On the other hand, the change process status table 800 in the second embodiment stores information on the progress rate of the task being executed in order to determine whether or not the control process of the change process is necessary based on the task progress rate. It may further have a task progress rate 806 that is a field.

For example, in the entry 1212 shown in FIG. 12, among the tasks constituting the change process identified by the identifier “Proc1”, the task identified by “Task2” is “executing”, and the progress rate of the task is It indicates “80%”.
<Control rule template table>

The control rule template table 1300 is a table newly added in the second embodiment.

The control rule template table 1300 stores information related to the control rule template. The control rule template is information indicating a determination criterion for control processing execution and a control content in order to determine whether or not to execute a specific control processing for the change process when a problem occurs in the managed computer system 101. It is. The control rule template is defined for each task type in a format that does not depend on a specific task or a task execution target (that is, a parameter).

FIG. 13 is a diagram for explaining an example of the data structure of the control rule template table 1300.

The control rule template table 1300 includes nine fields, that is, a rule template ID 1301, a task type 1302, a table 1303, a field 1304, an ID acquisition query 1305, an operator 1306, a value 1307, a control target 1308, and a control process 1309.

The fields of the control rule template table 1300 are roughly divided into a condition part 1331 and a conclusion part 1332 excluding the rule template ID 1301 and the task type 1302. The condition part 1331 has five fields: a table 1303, a field 1304, an ID acquisition query 1305, an operator 1306, and a value 1307. In the condition part 1331, information related to a change process or a condition for executing control processing on a task is defined. The conclusion unit 1332 has two fields of a control target 1308 and a control process 1309. In the conclusion section 1332, information related to the control process executed when all the conditions defined in the condition section 1331 are satisfied is defined.

The rule template ID 1301 stores information for uniquely identifying the control rule template. The task type 1302 stores information for identifying the type of task to which the control rule template is applied. The value stored in the task type 1302 may be a value equal to the value stored in the task type 503 of the change process list table 591 in FIG. 5A, for example. The table 1303 stores the table name of the table storing information used for determining the condition of the control rule. The field 1304 stores the field name of the field in which information used for determining the condition of the control rule in the table specified by the table 1303 is stored. The ID acquisition query 1305 stores a query for acquiring the ID of an entry in which information used for determining a control rule condition is stored.

In the present embodiment, as an example of information stored in the ID acquisition query 1305, an SQL statement for acquiring an ID of an entry storing condition information from the influence event management table 700 or the change process status table 800 is cited. . “@TaskId” in the SQL statement is a variable and indicates that the value stored in the task ID 502 of the change process list table 591 in FIG. 5A is substituted. In the present embodiment, the SQL sentence is taken as an example of means for acquiring information used for determining the condition of the control rule, but other acquisition means may be used. The acquisition destination is not the information recorded in the storage area of the management computer, but may be the management target computer system 101, the hypervisor 235 that manages execution of the VM live migration, orchestration software that manages the change process.

The operator 1306 stores an operator used for determining the condition of the control rule. The value stored in the operator 1306 may be, for example, comparison operators “>”, “=”, “≦”, “≠”, and the like. The value 1307 stores a value for determining whether or not the information specified by the table 1303, the field 1304, and the ID acquisition query 1305 satisfies the condition. The control target 1308 stores information for identifying the type of target for which the control process is executed when the condition unit 1331 satisfies the condition. In the present embodiment, the type “change process” is stored, but other values such as “task” may be used. The control process 1309 stores information for identifying a control process executed when the condition unit 1331 satisfies the condition. In the present embodiment, information for identifying the control process “suspend” is stored. As other control processes, “continue”, “standby”, “rollback”, “correction”, “reduction”, etc. It may be. Moreover, those combinations may be sufficient. “Correction” is, for example, a process in which the change process is interrupted, the contents of the remaining tasks are changed and executed so that the change process achieves its purpose and does not affect the detected problem. It may be. “Reduction” may be, for example, a process of reducing the number of parallel executions when a plurality of tasks are executed in parallel.

In this embodiment, the control rule template is defined for each task type, but may be defined for each type of change process. For example, a control rule template may be defined for each configuration change execution script file for which no parameter is input or for each general-purpose plan of the configuration change plan generation function represented by Patent Document 2.

For example, the entry 1311 in FIG. 13 is a control rule template identified by an identifier “CntlRuleTemplate1”. In this control rule template, when the task to be applied is “VM_LiveMigration” and all the conditions of the condition part 1331 are satisfied, the “change process” to which the task to be applied belongs belongs to the control target and is called “suspend”. Indicates that control processing is executed. Further, the control rule generated by the control rule template indicated by the entry 1311 has three conditions. In the entry 1321 indicating one of the three conditions, a table storing information used for condition determination is “Impact_management”, the field is “status”, the entry is determined by the task ID, and its value Indicates that the condition is satisfied when “is abnormal” and “is equal”.
<Control rules>

The control rule information 1400 is information updated by the control rule generation program 224 in the second embodiment.

The control rule information 1400 is a rule generated based on the information of the control rule template and the change process DB 500. The control rule information is information indicating control process execution conditions and control contents in order to determine whether or not to execute a specific control process for the change process when a problem occurs in the managed computer system 101. . The control rule template is defined for each task type in a format that does not depend on the task execution target (ie, parameter), whereas the control rule information is defined for each task based on the information in the change process DB 500. It includes the status of the specific impact event determined based on the task execution target and the progress status of the specific task.

FIG. 14 illustrates an example of a data structure of control rule information 1400 generated based on the control rule template “CtrlRuleTemplate1” indicated by the entry 1311 in FIG. 13 and the change process “Proc1” indicated by the

entries

511 and 512 in FIG. 5A. It is a figure to do.

In this embodiment, the control rule information is expressed by the data structure of a relational database table, but may be in another data format.

The control rule information 1400 includes 10 fields, that is, a control rule ID 1401, a change process ID 1402, a task ID 1403, a table 1404, a field 1405, an ID 1406, an operator 1407, a value 1408, a control target 1409, and a control process 1410.

The fields of the control rule information 1400 are divided into a condition part 1431 and a conclusion part 1432 like the control rule template table 1300 except for the fields 1401 to 1403. The condition part 1431 has five fields: a table 1404, a field 1405, an ID 1406, an operator 1407, and a value 1408. The condition part 1431 defines information related to a change process or a condition for executing control processing on a task. The conclusion unit 1432 has two fields of a control target 1409 and a control process 1410. The conclusion part 1432 defines information related to the control process that is executed when all the conditions defined in the condition part 1431 are satisfied.

The control rule ID 1401 stores information for uniquely identifying control rule information. The change process ID 1402 stores information for identifying the change process to which the control rule is applied. The value stored in the change process ID 1402 may be a value equal to the value stored in the change process ID 501 of the change process list table 591 in FIG. 5A, for example. The task ID 1403 stores information for uniquely identifying the task to which the control rule is applied. The value stored in the task ID 1403 may be, for example, a value equal to the value stored in the task ID 502 of the change process list table 591 in FIG. 5A. The table 1404 stores the table name of the table storing information used for determining the condition of the control rule. The value stored in the table 1404 may be, for example, a value equal to the table 1403 of the control rule template table 1300 in FIG. In the field 1405, the field name of the field in which information used for determining the condition of the control rule is stored in the table specified by the table 1403 is stored. The value stored in the field 1405 may be, for example, a value equal to the table 1404 of the control rule template table 1300 in FIG. The ID 1406 stores the ID of an entry that stores information used for determining the condition of the control rule in the table specified by the table 1403. The operator 1407 stores an operator used for determining the condition of the control rule. The value stored in the operator 1407 may be, for example, a value equal to the operator 1306 in the control rule template table 1300 in FIG. A value 1408 stores a value for determining whether or not the information specified by the table 1404, the field 1405, and the ID 1406 satisfies the condition. The value stored in the value 1408 may be, for example, a value equal to the value 1307 of the control rule template table 1300 in FIG.

The control target 1409 stores information for identifying a target on which the control process is executed when the condition unit 1431 satisfies the condition. In this embodiment, a value for identifying the change process is stored, but other values such as a task ID may be used. The control process 1410 stores information for identifying a control process executed when the condition unit 1431 satisfies the condition. The value stored in the control process 1410 may be, for example, the same value as the control process 1309 of the control rule template table 1300 in FIG.

For example, the entry 1411 in FIG. 14 indicates a control rule identified by the identifier “CntlRule 1-1”. This control rule is applied to the task “Task1” of the change process “Proc1”, and when all the conditions of the condition part 1431 are satisfied, the control “suspend” is controlled for the change process “Proc1”. The process is to be executed. The control rule indicated by the entry 1411 has three conditions. The contents of the entry 1421 indicating one of the three conditions are as follows. That is, the table storing information used for condition determination is “Impact_management”, the field is “Status”, the entry ID is “Impact1”, and the condition is “equal” to “abnormal”. Indicates that it is satisfied.

In the present embodiment, information for determining the location where information for condition determination is stored is stored in the condition part of the control rule template, and the control rule template is controlled based on the information in the change process DB 500. Is generated, and the condition part of the control rule stores information on the location where information for condition determination is stored. However, as another means, information on means for acquiring information for condition determination is stored in the control rule template, and each time a change process control program 227 described later is executed, the information is stored in the change process DB 500. Thus, information corresponding to the control rule information may be generated and the condition determination may be performed.
<Processing of control rule generation program>

The control rule generation program 224 is a program newly added in the second embodiment.

The control rule generation program 224 stores information in the control rule template table 1300 and the change process DB 500 in order to determine whether or not to execute a specific control process for the change process when a problem occurs in the managed computer system 101. Based on the control rule information 1400 is generated.

FIG. 15 is a flowchart of an example of processing of the control rule generation program 224 of the first embodiment.

The control rule generation program 224 may start this process when new change process information is registered in the change process DB 500. Also, this process may be started at the timing when the information on the impact event is updated in the impact event management table 700. Further, this process may be started when the execution of the change process is started. Further, when a problem of the management target computer system 101 is detected by the system information management program 221, this process may be started. This process may be started at an arbitrary timing from when new change process information is registered in the change process DB 500 or when the information in the influence event management table 700 is updated until the change process control program 227 is activated.

In step S1501, the control rule generation program 224 acquires an entry from the change process list table 591 of the change process DB 500. The entries to be acquired may be all entries, a newly registered entry, an updated entry, or an entry having a change process ID equal to the updated entry.

Note that when the updated entry or all entries are acquired and the subsequent processing proceeds, the control rule information 1400 related to the acquired change process DB entry is deleted in order to update the control rule information. You can do it.

In step S1502, the control rule generation program 224 repeats the processing in steps S1503 to S1507 for all the entries in the change process DB 500 acquired in step S1501.

In step S1503, the control rule generation program 224 acquires from the control rule template table 1300 all control rule templates having the same value as the task type 1302 stored in the task type 503 of the change process DB entry.

In step S1504, the control rule generation program 224 repeats the processing in steps S1505 to S1507 for all the control rule templates acquired in step S1503.

In step S1505, the control rule generation program 224 executes by assigning the value of the task ID 502 of the change process DB entry to all the variables stored in the ID acquisition query 1305 of the control rule template, and is designated by the table 1303. Get the ID set of the table. In this embodiment, the task ID is assigned to the query variable. However, when a control rule template is defined for each type of change process, the change process ID may be used.

In step S1506, the control rule generation program 224 acquires the ID belonging to the type indicated by the identifier stored in the control target 1308 of the control rule template from the change process DB entry. In the case of the control rule template shown in FIG. 13 of this embodiment, since “change process” is stored in the control target 1308, the ID of the change process is acquired from the change process ID 501 of the change process DB entry.

In step S1507, the control rule generation program 224 generates control rule information 1400 based on the information of the change process DB entry, the ID acquired in steps S1505 and S1506, and the control rule template. Specifically, the control rule ID 1401 of the control rule information 1400 stores identification information for uniquely identifying the control rule, and the change process ID 1402 and the task ID 1403 contain the values of the change process ID 501 and task ID 502 of the change process DB entry. The table 1404, the field 1405, the operator 1407, the value 1408, and the control process 1410 store the table 1303, the field 1304, the operator 1306, the value 1307, and the control process 1309 of the control rule template, respectively. The ID acquired in step S1505 is substituted for ID 1406, and the ID acquired in step S1506 is stored in the control object 1409.

A specific example of the processing of FIG. 15 is as follows.

For example, when the control rule generation program 224 acquires the entry 511 in FIG. 5A in step S1501, the control rule template indicated by the entry 1311 in FIG. 13 is further acquired in step S1503. In step S1505, the control rule generation program 224 executes the query by substituting the task ID “Task1” of the entry 511 for the variable of the ID acquisition query 1305, and the ID of the entry in which information for determining the condition is stored. To get. For example, in the case of the control rule template of FIG. 13, when “Task1” is substituted into the query variable of the entry 1321 of the condition part 1331 and executed, the ID “Impact1” of the entry 711 of the influence event management table 700 of FIG. , “Impact2” of entry 715 is acquired. When “Task1” is substituted into the query variables of the entry 1322 and the entry 1323 and executed, the ID “ProcSt1” of the change process status table 800 of FIG. 8 is acquired. In step S1506, “Proc1” stored in the change process ID 501 of the entry 511 is acquired based on the identification information “change process” stored in the control target 1308 of the entry 1311. In step S1507, the acquired information Based on this, control rule information indicated by the entry 1411 and the entry 1412 in FIG. 14 is generated.

In the present embodiment, when at least one influence event of a task is detected, control rule information 1400 for executing control processing is generated. Therefore, as in the above example, a plurality of IDs are obtained from one query in step S1505. When acquired, the condition part 1431 may be generated with a combination of acquired IDs, and control rule information may be generated for the number of acquired IDs. In the case of the above-described example, when “Task1” is substituted into the query variable of the entry 1321, two IDs “Impact1” and “Impact2” are acquired. Furthermore, when the queries of the entry 1322 and the entry 1323 are executed, the ID “ProcSt1” is acquired. As a result, two

control rules

1411 and 1412 shown in FIG. 14 are generated. If it is desired to generate control rule information for executing the control process including the influence event of all tasks, the control rule information 1400 having all the IDs acquired in step S1505 in the condition part 1431 may be generated. . Further, control rule information for executing a control process when X% satisfies the condition among the conditions generated by the entry 1321 that has the condition of detecting the influence event as a condition may be generated. Further, an identifier for switching the control rule information generation method for each task type may be defined in the control rule template and the control rule.
<Processing of System Information Management Program of Second Embodiment>

In the first embodiment, the system information management program 221 collects performance information or configuration information of managed components from the hypervisor 235 or a monitoring agent, and performs performance information table 300, configuration information table 400, or influence. Information on the status 707 in the event management table is updated. In addition, in the second embodiment, the system information management program 221 executes the process of the change process control program 227 of the second embodiment when the status of the performance information changes to “abnormal”.

FIG. 16 is a flowchart of an example of processing of the system information management program 221 of the second embodiment.

The system information management program 221 may start processing periodically, or the system information management program 221 may start processing at the timing transmitted from the monitoring agent to the management computer 201.

In step S1601, the system information management program 221 acquires performance information or configuration information of the management target component from the hypervisor 235 or the like.

In step S1602, the system information management program 221 stores the information acquired in step S1601 in the performance information table 300 or the configuration information table 400.

In step S1603, the system information management program 221 updates the value of the status 707 in the influence event management table 700 according to the value stored in the performance information table 300.

In step S1604, when the system information management program 221 updates the value of the performance information table 300 in step S1602, the system information management program 221 determines the status from the previous update for the metric uniquely identified by the combination of the component ID 301 and the metric type 302. It is determined whether or not there is even one metric whose value of 305 has changed from “normal” to “abnormal”. If the result of this determination is true (S1604: YES), the process proceeds to step S1605. If the result of this determination is false (S1604: NO), the process ends.

In step S1605, the system information management program 221 executes processing of the change process control program 227 (processing will be described later) of the second embodiment.

For example, when the system information management program 221 stores the entry 314 of FIG. 3 and the previous performance information of “PS / CPU / utilization” of the metric “PS2” indicated by the entry 314 is the entry 316 in step S1602 Since the status 305 of the entry 316 is “normal” and the status 305 of the entry 314 is “abnormal”, the determination in step S1604 is true, and the process of the change process control program 227 is executed.

In the present embodiment, the processing of the change process control program 227 is executed when the value of the status 305 changes to “abnormal” for all, but the status 707 of the influence event management table 700 is executed. It may be limited to the case where the value of changes to “abnormal”.
<Processing of change process control program>

In the first embodiment, the change process influence management program 225 displays the change process influence event according to the change process progress based on the influence event management table 700 and the change process status table 800. In addition, in the second embodiment, the change process control program 227 displays control processing to be executed for the change process based on the control rule information 1400.

FIG. 17 is a flowchart of an example of processing of the change process control program 227 of the second embodiment.

The execution of the change process control program 227 may be started by the system information management program 221 as shown in FIG. Further, the change process control program 227 may start processing upon reception of an input of a display instruction by an administrator or the like. The opportunity for the administrator to input a display instruction may be that the system information management program 221 detects that a problem has occurred in the managed computer system 101 and notifies the administrator.

In step S1701, the change process control program 227 acquires the value of the change process ID 802 from the change process status table 800. In this embodiment, the change process ID to be acquired may be stored in an entry whose change process status 803 is “executing” or “not executed”.

In step S1702, the change process control program 227 repeats the processes in steps S1703 to S1708 for all the change process IDs acquired in step S1701.

In step S1703, the change process control program 227 acquires all the control rule information in which the change process ID 1402 stores a value equal to the change process ID among the control rule information 1400 generated by the control rule generation program 224. .

In step S1704, the change process control program 227 repeats the processing in steps S1705 to S1708 for all the control rule information acquired in step S1703.

In step S1705, the change process control program 227 acquires all data from the table 1404, the field 1405, and the field and entry of the table indicated by the ID 1406 in the condition part 1431 of the control rule information.

In step S1706, the change process control program 227 determines whether each data acquired in step S1705 satisfies the conditions indicated by the operator 1407 and the value 1408 of the control rule information. That is, it is determined whether or not each condition indicated by the condition part 1431 of the control rule information is satisfied.

In step S1707, the change process control program 227 determines whether all the conditions of the condition unit 1431 are satisfied based on the determination result in step S1705. If the result of this determination is true (S1707: YES), the process proceeds to step S1708. If the result of this determination is false (S1707: NO), the process continues to repeat the process of step S1704.

In step S1708, the change process control program 227 acquires the values stored in the control target 1409 and the control processing 1410 of the conclusion part 1432 of the control rule information, and stores them in the memory.

In step S1709, the change process control program 227 activates the display program 226, and displays information on control processing to be executed on the output device 217 based on the information stored in the memory in step S1708.

A specific example of the processing of FIG. 17 is as follows.

For example, in step S1701, the change process ID “Proc1” stored in the entry 1212 of FIG. 12 is acquired from the table of the change process status table 800. In step S1703, the

entries

1411 and 1412 are selected from the control rule information 1400 of FIG. , 1413 and 1414 are acquired. In the repetitive processing in step S1704, as processing for the entry 1413, “normal” stored in the status 707 of the entry 713 in FIG. 7 and “task” stored in the task status 805 of the entry 1212 in FIG. “Execution in progress” and “80%” stored in the progress rate 806 are acquired. In step S1706, for example, when focusing on the condition indicated by the entry 1441, the value acquired in step S1705 is “normal”, whereas the operator 1407 of the entry 1441 indicates “=” and the value 1408 indicates “ Since “abnormal” is stored, it is determined that the condition is not satisfied. Accordingly, in step S1707, it is determined to be false, and the iterative process of step S1704 is continuously executed. If it is determined to be true in step S1707, a combination of information “Proc1” identifying the change process stored in the control target 1409 of the entry 1413 and information “suspend” identifying the control process to be executed. Is stored in the memory. In step S 1709, the display program 226 is activated and information is displayed on the output device 217.

Note that the process of the change process influence management program 225 of the first embodiment shown in FIG. 10 may be executed before, after, or simultaneously with the process shown in FIG.

In the second embodiment, an example of the screen displayed by the display program 226 in step S1709 is shown in FIG. The change process management screen 1100 is an example of a screen that displays recommended control processing based on information acquired or stored by the change process control program 227.

The configuration of the change process management screen 1100 in the second embodiment is substantially the same as the configuration of the change process management screen 1100 in the first embodiment. A change process name 1111, a change process status 1112, and a task and influence event display area 1113 are displayed to display an influence event according to the progress of the change process. On the other hand, the change process management screen 1110 in the second embodiment may further include a recommended control process display area 1814 for displaying control processes to be executed for the change process. In the display area 1814, a control process that is recommended to be executed may be displayed based on the information of the control target 1409 and the control process 1410 stored in the memory in step S1708 of FIG. In addition, a program for executing the control process defined by the control rule template is prepared in advance, and a button 1840 for starting the displayed program for executing the recommended control process is displayed in the display area 1814 for management. When the person selects the button, the program may be executed by inputting parameters for executing the recommended control processing into the program. In the change process management screen 1100 of FIG. 18, the value of the status 707 of the entry 713 of the influence event management table 700 of FIG. 7 is “abnormal” and the value of the status 707 of the

entries

711, 712, and 714 is “normal”. A display example is given.

In addition, when the set of the control target and the control process stored in the memory in step S1708 is duplicated, the recommended control process to be displayed may be one. Further, in the combination of the control target and the control process stored in the memory in step S1708, when there are a plurality of sets having the same control target and different control processes, all the sets may be displayed, or the control process to be displayed is displayed. May be limited to one. As a method of limiting the control processing to be displayed, priority is set to the identification information stored in the control rule template or the control target 1308 or the control processing 1309 of the control rule template table 1300, and the display with the highest priority is called A method may be adopted.

In addition, when the display content of the recommended control processing display area 1814 is updated, the administrator has a function of notifying the administrator of information of the recommended control processing display area 1814 by e-mail before displaying the screen. Also good.

The change process influence management program 225 and the change process control program 227 may be executed sequentially or in parallel, or only one of them may be executed. Therefore, in this embodiment, the recommended control process display area 1814 is added to the change process management screen 1100 in the first embodiment, but only the recommended control process display area 1814 may be displayed.

Further, in this embodiment, the control process recommended for the change process is displayed on the screen, and the final decision as to whether or not to execute the control process is left to the administrator. A program for executing the defined control process may be prepared in advance, and the change process control program 227 may input parameters to the control process execution program and automatically execute the recommended control process.

Further, in this embodiment, the problem that occurred in the managed computer system is intended to interrupt the change process when the problem is caused by the effect of the change process. An example has been described in which the change process is interrupted when they are equal. However, even if the problem that occurred is not due to the effect of the task being executed, the problem that occurred by executing the unexecuted task is further aggravated if the effect of the unexecuted task is equal to the problem that occurred. In some cases, it may be appropriate to interrupt the change process or cancel execution. Therefore, as exemplified in the entry 1312 of FIG. 13, in order not to exacerbate the problem that has occurred, a control rule template is defined that interrupts the change process when the influence event of an unexecuted task becomes abnormal. May be.

In this embodiment, the control rule generation program 224 generates control rule information from the control rule template in advance for all change processes and influence events. However, a problem in the managed computer system 101 is detected. When the control rule information is generated from, only the control rule information having an influence event equivalent to the detected problem in the condition unit 1431 may be generated. As a result, the consumption of the storage area of the management computer 201 can be reduced, and the processing speed can be improved by reducing the number of repetitive processes in step S1704 of FIG. 17 executed by the change process control program 227.

As described above, according to the second embodiment, the influence events of the computer system exerted by the tasks constituting the change process are changed with respect to the influence rule for each task type, the progress of the change process, and the change process. Whether or not a specific control process (for example, an interrupt process) should be executed for the change process when a problem occurs in the managed computer system based on the control process execution condition and the control rule template indicating the control content Can be determined. Thereby, even an administrator who does not have detailed knowledge about the task can appropriately determine whether or not the control process of the change process is necessary, or can determine in a short time. Alternatively, the control process of the change process can be automatically determined and executed by a program.
<< Third Embodiment >>

Next, a third embodiment will be described. In the following description, differences from the first embodiment or the second embodiment will be mainly described, and the same components, programs having equivalent functions, tables having equivalent items, and the like will be described. The description may be omitted or simplified.

In the first embodiment and the second embodiment, it is assumed that a specific managed component is affected during the execution of the tasks constituting the change process. In other words, when a problem occurs in the managed computer system 101, a problem occurs due to the influence of a task being executed, or a problem is further aggravated by starting execution of an unexecuted task. Gave an example of executing the interruption process (or other control process) of the change process.

However, depending on the type of task, there are things that affect specific managed components not only during task execution but also after task completion.

For example, live migration of a virtual machine, which is one of the task types mentioned in the first embodiment and the second embodiment, moves a physical server while the virtual machine continues to operate. Therefore, during the migration process, the CPU load for the migration process not only occurs on both the migration source and migration destination physical servers, but also the virtual machine migrated on the migration destination physical server after the migration process is completed CPU load is continuously generated due to operation.

As described above, when the influence of the task continues to exist even after the task execution is completed, there is a case where it is desired to interrupt the execution of the change process regardless of the task progress rate. In addition, when the influence of a task continues to exist, there is a case where it is desired to execute control processing such as rollback on the change process even when a problem occurs after the execution of the task or the change process is completed.

On the other hand, there are some impact events that occur only during task execution. For example, as described above, during execution of live migration of a virtual machine, a CPU load due to live migration processing occurs on the migration source physical server, but no load due to live migration occurs after completion of execution. In this way, for a temporary influence during task execution, it is not necessary to execute control processing such as rollback even when a problem occurs after task execution is completed.

Therefore, when a problem occurs in the managed computer system 101, whether or not the task that has been executed continuously affects a specific managed component as well as the influence event of the task being executed. Is preferably presented to the administrator. Also in the control rule described in the second embodiment, it is preferable to define a condition including an influence event caused by a task that has been executed.

In the third embodiment, an example will be described in which the control process of the change process is determined including whether or not the task that has been executed continuously affects a specific managed component.

Regarding the performance information table 300, the configuration information table 400, and the change process DB 500 used in the description of the third embodiment, the same information as in the first embodiment may be used. The change process status table 800, control rule template table 1300, and control rule information 1400 used in the description of the third embodiment may be the same as those in the second embodiment. The configuration of each table and each data may be the same as in the first embodiment or the second embodiment. However, in the third embodiment, the values stored in the control rule template table 1300 and the control rule information 1400 are changed for explanation.

In the third embodiment, the influence rule table 600 and the influence event management table 700 are changed. This is for explaining the process of determining the control process of the change process including whether or not the task that has been executed continuously affects a specific managed component. Further, the process executed by the change process influence management program 225 is also changed.
<Influence Rule Table of Third Embodiment>

FIG. 19 is a diagram for explaining an example of the data structure of the influence rule table 600 according to the third embodiment.

The configuration of the influence rule table 600 in the third embodiment is substantially the same as the configuration of the influence rule table 600 in the first embodiment. The influence rule table 600 has four fields, that is, a rule ID 601, a task type 602, an influence component information acquisition query 603, and an influence metric type 604 in order to store information on the influence rule. In addition to these, the influence rule table 600 according to the third embodiment has an influence period of the influence event of the task derived by the influence rule in order to determine whether the influence event continuously affects even after the task execution is completed. It may further have an influence period 605 which is a field for storing the information. In the present embodiment, the influence period is “In (influence only during task execution)”, “After (influence after task execution completion)”, “In & After (influence after task execution and after execution completion)” Any of these may be stored as identification information in the influence period 605, but identification information indicating other patterns may be stored.

For example, the entry 1911 in FIG. 19 indicates the following. That is, in the influence rule identified by the identifier “ImpactRule1”, the task type to which the influence rule is applied is “VM_LiveMigration”, and the managed component that the task affects is based on the VM parameter ID of the task. The metric type that is acquired from the migration destination physical server ID 523 of the table 592 and the task affects is “PS / CPU / utilization”, and the influence period of the influence event of the task derived by the influence rule is “in execution” And “after completion of execution”.
<Influence Event Management Table of Third Embodiment>

FIG. 20 is a diagram for explaining an example of the data structure of the influence event management table 700 according to the third embodiment.

The configuration of the impact event management table 700 in the third embodiment may be substantially the same as the configuration of the impact event management table 700 in the first embodiment. The influence event management table 700 has seven fields, namely, ID 701, change process ID 702, task ID 703, task type 704, influence component ID 705, influence metric type 706, and status 707 in order to store information on the influence event for each task. have. In addition to these, the influence event management table 700 in the third embodiment stores information on the influence period of the influence event of the task in order to determine whether the influence event continuously affects even after the task execution is completed. It may have an influence period 708 that is a field. In the present embodiment, the influence periods are “In (influence only during task execution)”, “After (influence after task execution completion)”, and “In & After (influence after task execution and after execution completion)” Any of these may be stored as identification information in the influence period 708, but identification information indicating other patterns may be stored.

For example, the entry 2011 in FIG. 20 indicates the following. That is, the influence event identified by the identifier “Impact1” is “Proc1” for the change process, “Task1” for the task, and “VM_LiveMigration” for the task type. Further, the event that the task “Task1” affects is “VM / CPU / contention” (here, the CPU contention rate of the VM) of the virtual machine (here, the virtual machine 234c in FIG. 2) identified by “vm3”. ) And the current performance value is “normal”. Then, it indicates that the influence period of the influence event of the task is “during execution and after completion of execution” of the task.

The values stored in the impact event management table 700 shown in FIG. 20 are based on the change process DB 500 in FIG. 5AB, the performance information table 300, and the impact rule table 600 in FIG. It is generated by executing the process 222. In the processing of the impact analysis program 222 of the third embodiment, when the entry is stored in the impact event management table 700 in step S907 in FIG. 9, the value of the impact period 605 in the impact rule table 600 in FIG. Processing to be stored in the influence period 708 of the influence event management table 700 of FIG. 20 is added.

For the sake of description of the third embodiment, values stored in the status 707 of the influence event management table 700 in FIG. 20 are the performance information table 300 in FIG. 3 of the first embodiment and the influence event in FIG. It is different from the value stored in the management table 700.
<Control Rule Template Table of Third Embodiment>

21A and 21B are diagrams for explaining an example of the data structure of the control rule template table 1300 in the third embodiment.

The configuration of the control rule template table 1300 in the third embodiment may be substantially the same as the configuration of the control rule template table 1300 in the second embodiment. In order to explain the third embodiment, the data stored in FIGS. 21A and 21B is different from that of the second embodiment.

In the control rule template according to the third embodiment, the determination of the value of the influence period 708 of the influence event management table 700 is added to the query conditional expression stored in the ID acquisition query 1305. This is for determining whether or not to execute the control process for the change process, including whether or not the influence event continuously affects even after the task execution is completed.

For example, if the control rule template “CtrlRuleTemplate3” indicated by the entry 2111 in FIG. 21A has an abnormality due to the influence of the task being executed and the influence period is “In (only during execution)”, the progress rate is 90%. If it is less, it indicates that the change process is interrupted. That is, if the progress rate is 90% or more, the period for generating a problem is sufficiently short, and the change process is continued without interruption. On the other hand, in the control rule template “CtrlRuleTemplate4” indicated by the entry 2112, an abnormality occurs due to the influence of the task being executed, and the influence period is “After (after execution is completed)” or “In & After (after execution and after completion of execution). ")" Indicates that even if the task is completed in a short time, the change process is interrupted regardless of the progress rate of the task because the influence continuously occurs after the task is completed.

In addition, when a task or change process that has been executed continuously affects a specific managed component and a problem occurs as a result, rollback control processing is executed for the change process. An example is shown in entry 2113 in FIG. 21B.

In the third embodiment, control rules are generated by the processing of the control rule generation program 224 shown in FIG. 15 of the second embodiment based on these control rule templates, the influence event management table 700, and the change process status table 800. Information 1400 is generated.
<Control Rule of Third Embodiment>

FIG. 23 is a diagram for explaining an example of the data structure of the control rule information 1400 in the third embodiment.

The configuration of the control rule information 1400 in the third embodiment may be substantially the same as the configuration of the control rule information 1400 in the second embodiment. In order to explain the third embodiment, the data stored in FIG. 23 is different from that of the second embodiment.

The four control rules shown in FIG. 23 are based on the control rule template “CntlRuleTemplate4” indicated by the entry 2112 in FIG. 21A, the change process status table 800 in FIG. 12, and the influence event management table 700 in FIG. It is a control rule generated by the processing of the control rule generation program 224.

In the third embodiment, the control process to be executed for the change process is determined based on the control rule of the control rule information 1400 by the process of the change process control program 227 shown in FIG. 17 of the second embodiment. The In the third embodiment, the change process ID may be acquired from all entries stored in the change process status table 800 in step S1701 of the change process control program 227 shown in FIG. Alternatively, the change process ID to be acquired may be selected based on a designated condition. For example, a new field for recording the completion time of the change process is added to the change process status table 800. The change process ID acquired in step S1701 may be the change process ID of an entry whose change process status is “executing” or “not executed”. Alternatively, the change process ID of an entry whose change process status is “completed” and whose completion time is within a certain time from the current time may be used.
<Processing of Change Process Impact Management Program of Third Embodiment>

In the first embodiment, the change process influence management program 225 displays the change process influence event according to the progress of the change process as described with reference to FIG. In the third embodiment, the display method of the influence event of the change process of the first embodiment described in FIG. 10 may be changed according to the value of the influence period 708 in FIG.

FIG. 22 is a flowchart of an example of processing of the change process influence management program 225 of the third embodiment.

The start timing of the change process influence management program 225 may be the timing described in the first embodiment. Further, as described in the second embodiment, the process of the change process influence management program 225 may be started before or after or in parallel with the process of the change process control program 227 shown in FIG.

In step S2201, the change process influence management program 225 acquires all entries from the change process status table 800.

In step S2202, the change process influence management program 225 repeats the processes in steps S2203 to S2211 for all the entries in the change process status table acquired in step S1201.

In step S2203, the change process influence management program 225 acquires all entries having the task ID 703 having the value stored in the task ID 804 of the change process status entry from the influence event management table 700.

In step S2204, the change process impact management program 225 repeats the processing in steps S2205 to S2211 for all entries in the acquired impact event management table.

In step S2205, the change process impact management program 225 acquires the value of the impact period 708 of the entry in the impact event management table.

In step S2206, the change process influence management program 225 determines whether or not the value stored in the task status 805 of the entry of the change process status table 800 is “executing”. If the result of this determination is true (S2206: YES), the process proceeds to step S2207. If the result of this determination is false (S2206: NO), the process proceeds to step S2208.

In step S2207, the change process influence management program 225 determines whether or not the value of the influence period acquired in step S2204 is “In” or “In & After”. If the result of this determination is true (S2207: YES), the process proceeds to step S2210. If the result of this determination is false (S2207: NO), the process continues to repeat the process of step S2202.

In step S2208, the change process influence management program 225 determines whether or not the value stored in the task status 805 of the entry of the change process status table 800 is “complete”. If the result of this determination is true (S2208: YES), the process proceeds to step S2209. If the result of this determination is false (S2208: NO), the process continues to repeat the process of step S2202.

In step S2209, the change process influence management program 225 determines whether the value of the influence period acquired in step S2204 is “After” or “In & After”. If the result of this determination is true (S2209: YES), the process proceeds to step S2211, and if the result of this determination is false (S2209: NO), the process continues to repeat the process of step S2202.

In step S2210, the change process impact management program 225 records the entry of the impact event management table 700 in the memory as an “ongoing” group.

In step S2211, the change process impact management program 225 records the entry of the impact event management table 700 in the memory as a “completed / ongoing” group.

In step S2212, the change process influence management program 225 activates the display program 226. The display program 226 is based on the acquired entry of the change process status table 800 and the information stored in the memory in steps S2210 and S2211, and the change process, task, and the effect of these changes at the start of the change process influence management program 225. Is displayed on the output device 217.

In step S2201, when the change process influence management program 225 acquires an entry from the change process status table 800, the entry to be acquired may be selected based on a specified condition. For example, a field for recording the completion time of the change process is newly added to the change process status table 800, and the entry acquired in step S2201 may be an entry whose change process status is “executing” or “not executed”. Alternatively, the entry may be limited to entries whose change process status is “complete” and whose completion time is within a certain time from the current time.

A specific example of the processing of FIG. 22 is as follows.

For example, in step S2201, the change process influence management program 225 acquires all the entries stored in the change process status table 800 of FIG. When the entry 1212 is targeted in the repetitive processing in step S2202, in step S2203, the change process influence management program 225 acquires the entry 2013, entry 2014, and entry 2017 in FIG. Next, when the process is executed on the entry 2013 in the repetition process of step S2204, the task status of the entry 1212 of the change process status table 800 is “being executed”, and the value of the influence period 708 of the influence event management table 700 is “In & After”. Therefore, the process proceeds to step S2210 by the determination process in steps S2206 and S2207. In step S2210, the entry 2013 is recorded in the memory as an “ongoing” group. In step S2212, the display program is activated and information is displayed on the output device 217.

FIG. 24 shows an example of a screen displayed by the display program 226 in step S2212 in FIG. 22 and step S1709 in FIG. 17 in the third embodiment. The change process management screen 1100 is based on the information acquired or stored by the change process influence management program 225 of FIG. 22 and the change process control program 227 of FIG. It is an example of a screen on which a control process is displayed.

The configuration of the change process management screen 1100 in the third embodiment may be substantially the same as the configuration of the change process management screen 1100 in the second embodiment. The change process management screen 1100 has a change process name 1111, a change process status 1112, and a task and influence event display area 1113 in order to display an influence event according to the progress of the change process. Further, the change process management screen 1100 may further include a recommended control process display area 1814 to display control processes to be executed for the change process.

In this embodiment, the recommended control processing display area 1814 is added to the change process management screen 1100 in the first embodiment, but a screen having only the recommended control processing display area 1814 may be displayed.

In the influence event 1124 of the third embodiment, the influence event for each task may be displayed based on the entry information of the influence event management table 700 acquired in step S2203 of FIG. In the case where the information is stored in the memory as the “ongoing” group or the “completed / ongoing” group in step S2210 or step S2211, as shown in the display area 1144 in FIG. 24, the “ongoing” identifier, Alternatively, the “completed / ongoing” identifier may be displayed or highlighted.

If the administrator displays “abnormal” in the performance status 1125 and the impact event displayed in the impact event 1124 belongs to the “ongoing” or “completed / ongoing” group, the problem that has occurred is changed. Control processing such as interruption or rollback of the change process may be executed.

As described in the second embodiment, the change process influence management program 225 and the change process control program 227 may be executed sequentially or in parallel, or only one of them may be executed.

In this embodiment, when the value of the status 707 of the entry of the influence event management table 700 belonging to the “ongoing” group or the “completed / ongoing” group is “abnormal”, as shown in FIG. The change process displayed in the change process name 1111 may be displayed as a cause candidate of the problem that has occurred.

As described above, according to the third embodiment, it is defined whether or not the influence of the task continues after the completion of the task execution for the influence rule, and the influence event of the change process is determined based on the definition. Or whether a specific control process for the change process should be performed. This makes it necessary to execute the control process of the change process, considering whether the tasks that make up the change process affect specific managed components only during execution, or whether they will continue to affect after execution completes. Judgment can be made.

In the first to third embodiments described above, live migration in which a physical server is moved while a virtual machine is operated is given as an example of a task. However, other change processes may be used.

For example, the task may be volume migration in which a logical volume (logical storage device) of the storage apparatus moves between RAID (Redundant Arrays of Independent Disks) groups. A RAID group is a group in which a plurality of physical storage devices are collected by RAID technology, and a logical volume is a LU (particular physical area of a RAID group cut out and logically accessible as one storage resource from a computer). Logical Unit). For example, the impact events caused by volume migration include an increase in the operation rate of the migration destination RAID group and a decrease in the response time of the logical volume on the migration destination RAID group. In addition, when a copy function such as taking snapshots periodically is applied to the logical volume on the storage device that performs volume migration, the copy speed of the logical volume to which the copy function is applied decreases. The impact event that occurs. As described in the third embodiment, there are an impact event that occurs only during task execution and a continuous event that occurs even after task execution is completed. Decreasing the response time of the volume is an continuously occurring influence event. On the other hand, a decrease in logical volume copy speed is an adverse event that occurs only during volume migration. Using volume migration as described above as one of the tasks, and using the methods described in the first to third embodiments for the above-mentioned influence events, the change events are displayed or recommended for the change process. Display of control processing may be performed.

Also, the task may be a server scale-out process in which a server running the same application is added and the load is distributed in order to improve the performance of the service provided by the computer system.

Also, the task may be a setting change process of an application operating on the server or an application program update process.

Also, the task may be a batch job in batch processing.

The task may be a control process for controlling an IoT device connected to the Internet via the Internet in the IoT field.

In the second embodiment and the third embodiment, the control rule template is defined for each task type, and when an influence event of a specific task occurs, it is the same regardless of the content of the influence event. Although control processing has been executed, a control rule template may be defined for each set of task type and influence metric type. For example, by defining a query to be stored in the ID acquisition query 1305 of the entry 1321 in FIG. 13 as follows, when executing live migration of a virtual machine, “CPU usage rate (PS / CPU / utilization) of a destination physical server” It is possible to define the control process separately when an "abnormality" occurs and when any other abnormality occurs.
SELECT ID FROM Impact_Management
WHERE Task ID = @TaskId AND Impact metric type = PS / CPU / utilization
... (2)

In the control rule template of the second embodiment or the third embodiment, whether or not the control process needs to be executed is determined based on whether or not the influence event caused by the task is in an “abnormal” state. The condition part 1331 may define a condition that considers “the magnitude of the influence of the task”.

For example, in the example of live migration of the virtual machine described in the second embodiment, the virtual machine (vm1) moves from the physical server (PS1) to the physical server (PS2). This live migration causes an effect of increasing the CPU usage rate (PS / CPU / utilization) of the physical server (PS2). However, the CPU usage rate of the physical server (PS2) also increases due to the load of the virtual machine (vm3) running on the physical server (PS2). At this time, if the CPU usage rate and the memory usage amount of the moving virtual machine (vm1) are small while the CPU usage rate of the virtual machine (vm3) is large, the contribution to the increase of the CPU usage rate of the physical server (PS2) It can be determined that the load of the virtual machine (vm3) is larger than that of the live migration. Therefore, in this case, there is a high possibility that the CPU usage rate abnormality of the physical server (PS2) cannot be solved even if the movement of the virtual machine (vm1) is interrupted. is there.

Such a determination may be incorporated in the condition part 1331 of the control rule template. For example, the following condition, that is, the CPU usage rate (VM / CPU / utilization) of the migration virtual machine is acquired from the performance information table 300 in the condition part 1331 of the control rule template in FIG. May be added. In addition, it is possible to calculate a rate of increase in the CPU usage rate of the moving virtual machine and add a condition for determining that the value is true when the CPU usage rate exceeds a certain value.

The increase rate is a value that can be calculated by the following expression when the CPU usage rates at a certain time t1 and a certain time t2 are pt1 and pt2, respectively.
Rate of increase = (pt2-pt1) / (t2-t1) (3)

Further, the control rule template condition part 1331 of FIG. 13 compares the following conditions, that is, the increase rate of the CPU usage rate of the migration virtual machine and the increase rate of the CPU usage rate of the virtual machine on the migration destination physical server. Further, a condition for determining as true when the rate of increase in the CPU usage rate of the moving virtual machine is high may be added.

For example, as shown in FIG. 25, a performance increase rate table 2500 that stores the increase rate of the performance value calculated based on the equation (3) is shown. The performance increase rate table 2500 may be stored in the disk 213 of the management computer 201.

FIG. 26 shows a modification of the condition part 1331 of the control rule template table 1300. The condition part 1331 of the modification shown in FIG. 26 may be a control rule template indicated by the entry 1311 of FIG. 13 or the

entries

2111, 2112 of FIG. 21A of the second embodiment.

FIG. 26 shows an example of the conditions of a control rule template that compares the rate of increase of the CPU usage rate of the migration virtual machine with the rate of increase of the CPU usage rate of the virtual machine that already exists on the migration destination physical server. . In the value 1307 of the control rule template table 1300 shown in the figure, a query is stored so that a value can be acquired from the table, not a fixed value. When generating the control rule information 1400 from the control rule template table 1300, the value 1408 of the control rule information 1400 and the query variable “@TaskId” stored in the value 1307 are acquired in step S1501 of the control rule generation program 224. A query in which the task ID of the entered entry is substituted is stored. When the control rule information 1400 is applied, a query of a value 1408 is executed, a specific value is specified, and a condition is determined based on the value. When a plurality of values are specified by the query stored in the value 1408, each value is compared with a value determined by the table 1404, the field 1405, and the ID 1406 according to the operator 1407 to determine whether the value is true or false. . The condition shown in FIG. 26 may be true when at least one of the values specified by the query of the value 1408 is determined to be true, or when a value of a certain ratio or more is determined to be true.

The calculation of the rate of increase of each metric of each component may be performed periodically and stored in the performance information table 2500, or performed every time the condition of the control rule template table 1300 is determined. Also good.

101 Computer system to be managed 201 Management computer 221 System information management program 222 Impact analysis program 225 Change process impact management program 400 Configuration information table 500 Change process DB
600 Influence rule table 700 Influence event management table 800 Change process status table

Claims

A management computer that manages a computer system to be managed,
The management computer has a central processing unit and a storage device,
The storage device
Configuration information relating to the configuration of the components constituting the managed computer system;
Change process information relating to a change process for changing the configuration of a component of the managed computer system, the change process information including tasks and parameters constituting the change process;
An impact rule for identifying the impact event caused by executing the task for each task type; and
Execution status of tasks constituting the change process, and
The central processing unit is
Based on the task type of the task that constitutes the change process information and the influence rule, a process of identifying an influence event for each task when the change process is executed,
A management computer that performs a process of identifying a task being executed based on an execution status of the task and identifying an influence event of the task being executed.
The central processing unit is
The management computer according to claim 1, further performing a process of outputting an influence event of the identified task being executed.
The impact event is the impacting component and the impacting metric,
The storage device
Further storing information indicating the state of the component including observations of multiple metrics;
The central processing unit is
The management computer according to claim 2, wherein processing for outputting a state of a component relating to the influence event of the task being executed is performed according to an observed value of the metrics relating to the influence event of the task being executed.
The impact event is the impacting component and the impacting metric,
The storage device
Information indicating the state of the component, including observations of multiple metrics,
A control process for the change process defined for each task type, and a control rule template including a criterion for determining whether the control process can be executed based on an influence event for each task type;
The central processing unit is
Based on the task type of the task constituting the change process and the control rule template, a process for generating a control rule including a control process for the change process and a criterion for determining whether the control process can be executed;
A process for determining whether or not to execute a control process for a change process defined in the control rule based on an observed value of a metric related to an influence event of the task being executed and a generated control rule;
The management computer according to claim 1, further comprising: processing for displaying a determination result of whether or not the control processing is necessary.
5. The management computer according to claim 4, wherein the criterion of the control rule template includes a change process or a task execution status.
The management computer according to claim 5, wherein the criterion of the control rule template includes a progress status of tasks constituting a change process.
The central processing unit is
The management computer according to claim 4, further performing a process of executing a control process defined in the control rule when a determination result of whether or not the control process is necessary is an execution result.
The management computer according to claim 4, wherein the control rule template is defined for each type of the change process.
The management computer according to claim 4, wherein the control rule template is defined for each set of task type and influence metric type.
The criterion of the control rule template is a comparison between the rate of increase in the observed value of the specific metric of the component that is changed by the execution of the task and the rate of increase in the observed value of the specific metric of the component that is affected by the execution of the task. The management computer according to claim 4, comprising:
The impact rule includes a period in which the impact event occurs for each task type,
The central processing unit is
Based on the task type of the task constituting the change process information and the influence rule, an influence event for each task when the change process is executed, and a process for specifying a period in which the influence event occurs;
The management computer according to claim 2, further comprising: outputting the influence event according to the change process and an execution status of a task constituting the change process.
The impact rule includes a period in which the impact event occurs for each task type,
The control rule includes a period in the criteria for determining whether or not to execute,
The central processing unit is
Execution of the control process for the change process defined in the control rule based on the observed value of the metric related to the influence event of the task being executed, the control rule, and the execution status of the task constituting the change process The management computer according to claim 4 which judges necessity.
The central processing unit is
The management computer according to claim 3, wherein when the state of a component that is affected by the task is “abnormal”, the change process related to the task is displayed as a cause of a problem.
A method for managing a computer system to be managed by a management computer,
The management computer has a central processing unit and a storage device,
The storage device
Configuration information relating to the configuration of the components constituting the managed computer system;
Information relating to a change process for changing a configuration of a component of the managed computer system, including change process information including tasks and parameters constituting the change process;
An impact rule for identifying the impact event caused by executing the task for each task type; and
Execution status of tasks constituting the change process, and
The central processing unit is
Based on the task type of the task that constitutes the change process information and the influence rule, a process of identifying an influence event for each task when the change process is executed,
A management method for performing a process of identifying a task being executed based on an execution status of the task and identifying an influence event of the task being executed.
A computer program for a management computer that manages a computer system to be managed,
The management computer has a central processing unit and a storage device,
The storage device
Configuration information relating to the configuration of the components constituting the managed computer system;
Information relating to a change process for changing a configuration of a component of the managed computer system, including change process information including tasks and parameters constituting the change process;
An impact rule for identifying the impact event caused by executing the task for each task type; and
Execution status of tasks constituting the change process, and
When the computer program is executed by the central processing unit,
Based on the task type of the task that constitutes the change process information and the influence rule, a process of identifying an influence event for each task when the change process is executed,
A computer program for performing a process of specifying a task being executed based on an execution status of the task and specifying an influence event of the task being executed.