JP6748724B2 - Management computer, method and computer program for managing a computer system to be managed - Google Patents

Description

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

In the management of a computer system, it is required that the devices and their components that make up the computer system and the services provided by the computer system continue to operate normally. Therefore, when a problem occurs in the computer system, a recovery process or a preventive process may be executed to solve the problem or prevent the problem from occurring. For example, when a problem occurs that the performance of a device that makes up a computer system abnormally decreases, it is possible to change the configuration or settings of the device or software based on the past performance value of the software running on that device. Sometimes the problem goes away. In addition, configuration changes are frequently carried out to provide new services. In recent years, these changes may be implemented without stopping the service provided by the computer system.

Therefore, if a problem with the computer system or the service provided is detected during execution of the change, it may be necessary to suspend or review the operation for changing the series of configurations (hereinafter referred to as the change process). is there. Whether or not to interrupt the change process must be decided by the administrator of the computer system based on whether or not the problem that occurred is due to the influence of the change process.

The influence of the change process is, for example, a decrease in the performance of the device or software, which is caused by the load on the device or the consumption of resources that occurs in executing the change process. However, the configuration of a computer system in recent years is large in scale and complicated, and the influence caused by the contents and progress of the configuration change and setting change is also different. Therefore, it is difficult to identify the impact event by the change process and to judge whether to suspend or review the change process. Therefore, the computer system administrator may make an erroneous decision such as interrupting a change process that does not need to be interrupted.

JP, 2009-217587, A 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 of 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 process and the batch jobs that configure the batch process are fixed, whereas in the case of a computer system change process, the content of the process to be executed and execution The range and phenomenon that have an influence differ depending on the target and the processing execution state.

According to an embodiment of the present invention, a management computer that manages a computer system to be managed includes the central processing unit and a storage device. The storage device is configuration information regarding a configuration of components that configure the managed computer system and change process information regarding a change process that changes the configuration of components of the managed computer system, and configures the change process. Change process information including a task and a parameter to be executed, an influence rule for specifying an influence event caused by executing the task for each task type, and an execution status of the task configuring the change process are stored. 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 the influence event for each task when the change process is executed, and the execution status of the task A task being executed based on the above, and a process of specifying an influential event of the task being executed.

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 shows an outline of 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. 5 shows an exemplary data structure of a performance information table of the first embodiment. 3 shows an exemplary data structure of a configuration information table of the first embodiment. The example data structure of change process DB of 1st Embodiment is shown. The example data structure of change process DB of 1st Embodiment is shown. 5 shows an exemplary data structure of an impact rule table of the first embodiment. 5 shows an exemplary data structure of an influential event management table according to the first embodiment. 5 shows an exemplary data structure of a change process status table of the first embodiment. The process example 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 the display program of 1st Embodiment displays on a display is shown. 5 shows an exemplary data structure of a change process status table of the first embodiment. 8 shows an exemplary data structure of a control rule template table of the second embodiment. 8 shows an exemplary data structure of a control rule of the second embodiment. The processing example of the control rule generation program of the second embodiment is shown. The processing example of the system information management program of 2nd Embodiment is shown. The processing example of the change process control program of 2nd Embodiment is shown. An example of the change process management screen which the display program of 2nd Embodiment displays on a display is shown. The example data structure of the influence rule table of 3rd Embodiment is shown. The example data structure of the influence event management table of 3rd Embodiment is shown. 8 shows an exemplary data structure of a control rule template table of the third embodiment. 8 shows an exemplary data structure of a control rule template table of the third embodiment. The processing example of the change process influence management program of 3rd Embodiment is shown. 9 shows an exemplary data structure of a control rule of the third embodiment. An example of the change process management screen which the display program of 3rd Embodiment displays on a display is shown. 3 illustrates an exemplary data structure for a performance gain table. An example of conditions for adding the “magnitude of the effect of the task” to the condition part of the control rule template is shown.

DETAILED DESCRIPTION In the following detailed description of the invention, reference is made to the accompanying drawings, which form a part of the disclosure, which show, by way of illustration, exemplary embodiments in which the invention can be practiced and are not limiting of the invention. In these drawings, the same reference numerals denote the same components throughout the drawings. Furthermore, although 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 one of ordinary skill in the art. Note that this can be extended to other embodiments that are known or will become known in the future.

When referring to “this embodiment” herein, a particular feature, structure or characteristic described in connection with that embodiment is meant to be included in at least one embodiment of the invention. However, the appearances of these terms in various places in the present specification do not necessarily all refer to the same embodiment.

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

Further, some portions of the detailed description that follow are presented as algorithms and symbolic representations of operations within a 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 set of defined steps that reaches a desired final state or result. In the present invention, the steps performed require physically manipulating 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 often proved convenient to refer to these signals as bits, values, elements, symbols, characters, items, numbers, instructions, etc., because they can be commonly used in principle. However, it should be noted that all of these and similar items should be associated with appropriate physical quantities and are merely convenient labels attached to these physical quantities.

As will be apparent from the following description, unless otherwise specified, terms such as “process”, “calculate”, “calculate”, “determine”, and “display” are used throughout the description of the present specification. The description used is to manipulate data represented as physical (electronic) quantities in a computer system or registers and memory of the computer system to manipulate memory or registers of the computer system or other information storage, transmission or It may include the operation and processing of another information processing device that converts it into other data that is similarly expressed as a physical quantity in the display device.

The present invention also relates to apparatus for performing the operations herein. The apparatus may be specially constructed for the required purposes, or it may comprise one or more general purpose computers selectively activated or reconfigured by one or more computer programs. Such computer programs may be stored on a computer readable storage medium such as, for example, optical discs, magnetic discs, read-only memory, random access memory, solid state devices and drives, or any other medium suitable for storing electronic information. However, it is not limited to these.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Although a variety of general purpose systems may be used with the programs and modules according to the teachings herein, it may be convenient to construct more specialized apparatus to perform the desired method steps. The structure of these various systems will be apparent from the description disclosed below. The present invention is also not predicated on any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention, as described below. The instructions in the programming language can be executed by one or more processing units, such as a central processing unit (CPU), processor, or controller.

In the following description, the information of the present invention will be described in terms of expressions such as "aaa table", "aaa list", "aaaDB", etc. However, these information are expressed in other than the data structure such as table, list, relational database, etc. May be. Therefore, the "aaa table", the "aaa list", the "aaaDB", etc. may be referred to as "aaa information" to indicate that they do not depend on the data structure.

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

In the following description, the term “program” may be used as the subject, but since the program uses the memory and the communication port (communication control device) to perform the processing specified by the processor, the processor is the subject. It may be explained as. Further, the process disclosed with the program as the subject may be performed by a computer such as a management server or an information processing device. Further, part or all of the program may be realized by dedicated hardware.

Further, various programs may be installed in each computer by a program distribution server or a computer-readable storage medium.

The management computer has an input/output device. A display, a keyboard, and a pointer device can be considered as examples of the input/output device, but other devices may be used. Further, as an input/output device substitute, a serial interface or an Ethernet interface is used as an input/output device, and a display computer having a display, a keyboard, or a pointer device is connected to the interface, and display information is transmitted to the display computer. The display computer may perform display by receiving the input information from the display computer, or the input and display at the input/output device may be replaced by receiving the input.

Hereinafter, a set of one or more computers that manage the computer system and display the display information may be referred to as a management system. When the management computer displays the display information, the management computer may be the management system. The management system may be a combination of the management computer and the display computer. Also, in order to speed up the management process and increase reliability, it is possible to implement processing equivalent to that of the management computer on multiple computers. In this case, those computers (for display when the display computer performs display) A management system may be a computer). “Displaying display information” by the management computer may be displaying the display information on a display device included in the management computer, or the management computer (for example, a server) may display a remote display computer (for example, a client). ) May be transmitted to the display information. Further, in the following description, when the elements of the same type are described separately, the reference numerals of the elements are used, and when the elements of the same type are described without distinction, the common parent among the reference numerals of the elements is used. A sign may be used. For example, when the description is made without particularly distinguishing the servers, it may be described as the server 202, and when the individual servers are described separately, they may be described as the servers 202a and 202b.

In the following description, one or more operations for changing the configuration applied to the computer system for one purpose and one or more operations for changing the settings are referred to as a “change process”. To call. Furthermore, each change operation that constitutes the change process is called a "task", and the set 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 for the device and the software, a device for displaying the influence event by the change process according to the progress status of the change process, Methods and computer programs are provided.

In the present 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 content of the change process.

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

According to this embodiment, the management computer 201 is a computer that manages at least one device that constitutes the management target computer system 101. The devices constituting the managed computer system 101 include, for example, a computer represented by a server and a network device represented by an IP (Internet Protocol) switch. Further, in the field of IoT (Internet of Things), a device connected to the Internet or a device (IoT device) attached with a computer may be used. The 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 managed computer system collected by the system information management program 221. The change process DB 500 is a table that stores the tasks and parameters of the change process to be executed. The task and its parameter may be, for example, an API that operates devices and software that make up the computer system and its arguments. Also, the modification process may be a script that executes an API. The influence rule table 600 is stored in a format in which a task and an influential event given by the task do not depend on an execution target of the task. The change process status table 800 stores the progress statuses of change processes and tasks being executed.

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

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

According to the present embodiment, when a problem in the computer system (for example, an abnormal deterioration in the performance of a device that constitutes the computer system or the service provided by the computer system) is detected, the change process causes the change process. The impact events that will be identified are identified. The identified influential event may be displayed in response to a request from the computer system administrator. Thereby, the administrator can check the content of the detected problem and the influential event of the change process, and confirm whether or not the occurred problem is due to the influential event of the change process. In other words, 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 of the first embodiment. The computer system has 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. Good. The disk 213 is, for example, an HDD (Hard Disk Drive), but instead, another non-volatile storage device such as an SSD (Solid State Drive) may be adopted. As the logical module of the management computer 201, for example, the system information management program 221, the impact 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, the change process control program 227. With. Further, the management computer 201 has, 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 the managed devices collected from the managed devices by the system information management program 221 and the physical and logical elements that configure the managed devices. is there. The performance information table 300 and the configuration information table 400 may not be included in the management computer 201 but may be held in each management target device. In this case, when referring to the configuration information or the performance information, the management computer 201 may access each management target device via the network 220 and acquire the information.

The system information management program 221, the impact analysis program 222, the changed process status management program 223, the control rule generation program 224, the changed process influence management program 225, the display program 226, and the changed process control program 227 are stored in the memory 212, and the CPU 211. 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 suitable storage area that the CPU 211 can refer to.

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 about the device and its components, such as configuration information and performance information, from a managed device such as the physical server 230 connected via the network 220. The output device 217 is a device that outputs (typically displays) the information from the display program 226. The input device 214 is a device that receives a user's 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 devices other than these may be used.

The physical server 230 may be a managed device that executes programs such as applications. The server 230 may be a general-purpose computer including a memory 232, a network I/F 233, and a CPU 231 connected to them. 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 have a hypervisor 235 capable of logically creating and executing a virtual machine 234. The hypervisor 235 can control multiple virtual machines 234 at one time. The computer resources such as the CPU 231 and the memory 232 of the physical server 230 are divided and assigned to the respective virtual machines 234 by the hypervisor 235, so that the application programs can be executed as if they were stand-alone physical computers.

The hypervisor 235 monitors the configurations and performances 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 any timing.

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

The performance information table 300 stores performance information of a managed device or its constituents (hereinafter, the managed device and constituents may be collectively referred to as a managed component). This performance information may be collected by the system information management program 221 from the hypervisor 235 or the like, or the 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 illustrating 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 that identifies an observation item of performance 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 the determination result of whether or not 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 static threshold value set in advance for each metric type. Further, when a threshold value of the performance value is set in advance for each metric type and managed component set, it may be determined as “abnormal” when the observed performance value exceeds the threshold value. The threshold may be dynamically calculated. For example, for a specific metric type of a specific managed component, a dynamic threshold may be set based on performance values for a certain past period. Further, in the present embodiment, only “normal” and “abnormal” are defined as the identification information indicating the status, but three or more statuses are defined by defining a plurality of threshold values for one metric type. You may. In the present embodiment, a set of a managed component and a metric type stored as “abnormal” in the status 305 is detected as a problem that has occurred in the managed computer system 101, and the system information management program 221 notifies the administrator. It 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, with respect to 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". , 2016/01/01/0:00, the performance of "90%" was observed. Then, the performance value is "abnormal" based on a certain determination condition, and is detected as a problem that has occurred in the managed computer system 101.
<Configuration information table>

The configuration information table 400 stores the configuration information of the managed device acquired by the system information management program 221 from the hypervisor 235 or the like. The configuration information includes related information indicating a connection relationship, a dependency relationship, etc. between the managed device and its constituent elements. The system information management program 221 may start processing periodically to 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 update the information in the configuration information table 400.

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.

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

Further, in the configuration information table 400, the information in the table may be updated when the configuration of the managed component is changed. When the information in the configuration information table 400 is updated, the information before the update may be recorded and stored as history information so that the 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 of FIG.

For example, the entry 411 in FIG. 4 is 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 identifiers (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 constituent elements of the physical server, such as the CPU 231, the memory 232, the identification information of the network I/F 233, and the like. The specifications, model, etc. of may be stored. In addition, information on an application program running on a physical server or a virtual machine may be stored.
<Change process DB>

The change process DB 500 stores information about change processes that are scheduled to be executed, are being executed, or have been completed for the managed computer system 101. The change process consists of tasks and parameters.

In the present embodiment, a task is the minimum unit of a configuration change operation or a setting change operation executed for a managed device or a program that operates on the managed device. That is, a task is the minimum unit of a configuration or setting change operation that can execute a control process such as an interruption process when controlling the change process. For example, the task may be an API or command for changing the configuration/setting, a program for executing the configuration/setting change, a minimum unit of the configuration/setting change operation executed by the administrator, or the like. The parameter may be an API, an argument of a command or a program, or a setting value input in an operation executed by an administrator. A modification process is a process consisting of one or more tasks that are performed on a computer system for a purpose. The change process may be defined by a script that executes an API, a command, or a program, a workflow of an orchestration software typified by vRealize Orchestrator (registered trademark), or a procedure or plan of an operation performed by an administrator. ..

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

The administrator may input whether to execute the change process or determine whether the change process is being executed. Alternatively, when using the execution scheduler function of the batch job management software or the orchestration software, the execution status of the change process may be determined by acquiring information from the scheduler function.

In the present embodiment, the information about the change process is stored in the change process DB 500 in the storage area of the management computer 201, but a method of acquiring the information from the script file or the orchestration software at the timing of using the information may be adopted. ..

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

In this embodiment, VM live migration is taken as an example of a task that constitutes the change process. Therefore, in the present 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 make up 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, when 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 situations, different IDs are assigned to each other. The task type 503 stores a value for identifying the type of task. The task type is, for example, information for determining which API or command is used. The parameter ID 504 stores a value that uniquely identifies a combination of one or more parameters used in the task.

For example, entry 511 in FIG. 5A indicates that the modification process identified by the identifier “Proc1” includes two tasks identified by the identifiers “Task1” and “Task2”. Further, the two tasks belong to a type (here, VM live migration) identified by an identifier “VM_LiveMigration”, and parameters identified by “Param1” and “Param2” are 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 moving virtual machine ID 522, a movement destination physical server ID 523, and a movement source physical server ID 524.

The parameter ID 521 stores information that uniquely identifies 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 moving virtual machine ID 522 stores a value that uniquely identifies a moving virtual machine in one VM live migration task. The value stored in the moving virtual machine ID 522 may be equal to the value stored in the virtual machine ID 402 in FIG. 4, for example. 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 destination physical server ID 523 may be equal to the value stored in the physical server ID 401 of 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 specified by the migration virtual machine 522. The value stored in the source physical server ID 524 may be equal to the value stored in the physical server ID 401 of FIG. 4, for example.

The parameters of the tasks other than the task type “VM_LiveMigration” may be stored in another table. In that case, each parameter set 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”. Further, in the entry 531 of FIG. 5B, in the VM live migration executed in “Task1”, the moving virtual machine is “vm1” (here, the virtual machine 234a of FIG. 2), and the physical server of the moving destination is “vm1”. PS2” (here, the physical server 230b in FIG. 2) is present, and the source physical server is “PS1” (here, the physical server 230a in FIG. 2).
<Impact rule table>

The influence rule table 600 stores rules for deriving an influence event for each task constituting the change process registered in the change process DB 500. In the present embodiment, as an example of the influential event, the performance of the managed component that is affected by the execution of one task and whose value fluctuates is cited. This is an example and the impact event is not limited to the performance of the managed component. The influential 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 information on the status of another task expressed as “success” or “failure”.

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

FIG. 6 is a diagram illustrating 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.

A value for uniquely identifying the influence rule is stored in the rule ID 601. The task type 602 stores a value that identifies 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 of FIG. 5A, for example. The affected component information acquisition query 603 stores a query for acquiring information on a managed component that a certain task affects. In the present embodiment, an example of the information stored in the affected component information acquisition query 603 is an SQL statement that is acquired from the configuration information table 400 or the change process DB 500 and that acquires the ID of the component that the task affects. ing. “@Param” in the SQL statement is a variable and indicates that the value stored in the parameter ID 504 of the change process list table 591 of FIG. 5A is substituted. In the present embodiment, the SQL sentence is taken as an example of the means for acquiring the information of the component affected by the 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 the execution of VM live migration, or the orchestration software that manages the change process. Good. The influence metric type 604 stores a value that uniquely identifies a metric type that a certain task influences. The value stored in the influence metric type 604 may be the same value as the metric type 302 in FIG. 3, for example.

For example, the entry 611 in FIG. 6 indicates that in the influence rule having the identifier “ImpactRule1”, the application target of the influence rule is a task belonging to the type identified by the identifier “VM_LiveMigration”. The information of the managed 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 about the influence event of each task derived based on the influence rule stored in the influence rule table 600 of FIG. In the present embodiment, the influential event is represented by a set of the ID of the managed component that one task affects and the metric type that is an observation item of performance, but may be represented by other information. .. The affecting event may be other than the performance of the managed component.

FIG. 7 is a diagram illustrating an example of the data structure of the influential event management table 700.

The influence 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 influence component ID 705, an influence metric type 706, and a status 707.

The ID 701 stores a value that uniquely identifies a set of a task and an influential event. The change process ID 702 stores a value that uniquely identifies the change process. The value stored in the changed process ID 702 may be equal to the value stored in the changed process ID 501 of the changed process list table 591 of 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, for example, a value equal to the value stored in the task ID 502 of the change process list table 591 of FIG. 5A. A value for identifying the task type is stored in the task type 704. The value stored in the task type 704 may be, for example, a value equal to the value stored in the task type 503 of the change process list table 591 of FIG. 5A. The affected component ID 705 stores a value that uniquely identifies the managed component 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 a value equal to the value stored in the physical server ID 401 or the virtual machine ID 402 of the configuration information table 400 of FIG. 4, for example. The influence metric type 706 stores a value that uniquely identifies the metric type affected by the task indicated by the identifier stored in the task ID 703. The value stored in the influence metric type 706 may be the same value as the metric type 302 in FIG. 3, for example. The status 707 stores the influence component ID 705 and the determination result of whether the performance value uniquely identified by the influence metric type 706 is abnormal. The value stored in the status 707 may be equal to the value stored in the status 305 of the performance information table 303 of FIG. 3, for example. In addition, the system information management program 221 may collect the performance information of the managed component and update the value of the status 707 each time the performance information table 300 is updated.

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

In the present embodiment, the influential events are stored in the table and managed, but the information corresponding to the information in the influential event management table is generated each time by 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 about the progress statuses of change processes 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. If the task is of another type, it may be acquired from a program that manages each task.

Also, progress may be obtained from the orchestration software if the change process is being performed by the orchestration software. Further, the progress status may be derived based on the information regarding the execution content of the change process stored in the change process DB 500 and the change in the configuration information of the managed computer system 101.

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

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

The change process status table 800 includes five fields, namely ID 801, change process ID 802, change process status 803, task ID 804, and task status 805. A value that uniquely identifies an entry in the change process status table 800 is stored in the ID 801. The change process ID 802 stores a value that uniquely identifies the change process. The value stored in the changed process ID 802 may be equal to the value stored in the changed process ID 501 of the changed process list table 591 of FIG. 5A, for example. 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”, “in execution”, and “unexecuted”, 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, for example, a value equal to the value stored in the task ID 502 of the change process list table 591 of FIG. 5A. The task status 805 stores a value that identifies the execution status of the task that constitutes the change process. In this embodiment, the task execution status may be divided into three states of “completed”, “in execution”, and “unexecuted”, 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 “under execution”, and the task identified by “Task2” among the tasks configuring the change process “Proc1” is Indicates that it is "in progress".
<Processing of impact analysis program>

The impact analysis program 222 identifies the impact event due to the change process and 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 according to the first embodiment.

The impact analysis program 222 may start this processing when information of a new change process is registered in the change process DB 500. Further, this processing may be started at the timing when the information of the change process is updated in the change process DB 500. New change process information is registered in the change process DB 500, or the registered change process information is updated, and then the control rule generation program 224, the change process influence management program 225, or the second embodiment will be described. This process may be started at an arbitrary timing until the change process control program 227 to be activated is started. Further, when the task being executed is to change the configuration of the managed computer system 101, the influencing event of another task may change due to the completion of the task. Then, 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, newly registered entries, updated entries, or entries having a change process ID equal to the updated entry.

In addition, when the updated entry or all the entries are acquired and the subsequent processing is advanced, the acquired change process DB among the entries of the affected event management table 700 is set in order to update the information of the affected event to the latest state. Entries related to the entry may be deleted.

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

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

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

In step S905, the impact analysis program 222 substitutes the value stored in the parameter ID 504 of the change process DB entry for the variable of the impact component information acquisition query 603 of the impact rule, executes the query, and affects the task. Acquires all the identification information (affected component ID) of the managed component to be received.

In step S906, the influence analysis program 222 repeats the processing of steps S907 to S909.

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

In step S908, the impact analysis program 222 identifies, from the performance information table 300, an entry having the component ID 301 and the metric type 302 that have 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 that 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 process of FIG. 9 is as follows.

For example, when the entry 511 of FIG. 5A is acquired in step S901, the entries 611 and 612 of FIG. 6 are acquired from the influence rule table 600. In the iterative process of step S904, when executing the process for the entry 611, in step S905, the parameter ID “Param1” is assigned to the variable of the affected component information acquisition query 603, 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)

Then, in step S907, information from the ID 701 of the entry 711 to the influence metric type 706 of FIG. 7 is stored, in step S908, the entry 314 is acquired from the performance information table 300 of FIG. 3, and in step S909, of the entry 711 of The information “abnormal” stored in the status 305 of the entry 314 is stored in the status 707.
<Process 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 status 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 impact management program 225 according to the first embodiment.

The change process impact management program 225 may receive an input of a display instruction by an administrator or the like and start processing. The trigger for the administrator to input the 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 impact management program 225 acquires all entries from the change process status table 800.

In step S1002, the change process impact management program 225 repeats the processes of 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 from the influence event management table 700, an entry having the task ID 703 having the value stored in the task ID 804 of the change process status entry.

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

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

In step S1006, the change process impact 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 Displays on the output device 217 the information of the event that has an influence at the start of the change process influence management program 225.

A specific example of the process of FIG. 10 is as follows.

For example, in step S1001, the change process impact management program 225 acquires all the entries stored in the change process status table 800 of FIG. In the iterative process of step S1002, when the entry 812 is targeted, the change process impact management program 225 acquires the entry 713 and the entry 714 of FIG. 7 in step S1003. Then, in the determination processing in step S1004, since “running” is stored in the task status 805 of the entry 812, the processing proceeds to step S1005, and in step S1005, the change process impact management program 225 sets the entry 812 and the entry 812. The combination of 713 and 714 is recorded in the memory as an “ongoing” group, and in step S1006, the display program is activated and the 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 for displaying the contents of the change process, the progress status, and the influential event based on the information acquired and stored by the change process impact management program 225.

The change process management screen 1100 may have a display area 1101 that displays information for each change process. Further, the display area 1101 may be composed of three fields, that is, a changed process name 1111, a changed process status 1112, and a task and influence event display area 1113.

In the changed process name 1111, the identification information of the changed process may be displayed in a format understandable to the administrator based on the information of the changed process ID 802 of the entry of the changed process status table 800 acquired in step S1001 of FIG. .. In the change process status 1112, the progress status 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/influenced event display area 1113, information on tasks that make up the change process and the influential events may be displayed. The display area 1113 may be composed of 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 be displayed by forming one entry for each task that constitutes the change process.

In the task name 1121, the identification information of the task may be displayed in a format that the administrator can understand based on the information of the task ID 804 of the entry of the change process status table 800 acquired in step S1001 of FIG. As the execution content 1122, the information acquired from the change process DB 500 is displayed in a format in which the administrator can understand the execution content of the task based on the information of the task ID 804 of the entry of the change process status table 800 acquired in step S1001 of FIG. It may have been done. In the status 1123, task status information may be displayed based on the information of the task status 805 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 information of the entry of the influence event management table 700 acquired in step S1003 of FIG. If the entry of the influential event management table 700 acquired in step S1003 is stored in the memory as the “ongoing” group in step S1005, the “ongoing” identifier is displayed as shown in the display area 1144. , May be highlighted. In the performance status 1125, the status of the performance information indicated by the influential event may be displayed based on the information of the status 707 of the entry of the influential 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 of the affected event management table 700 is “abnormal”.

The administrator determines that the problem occurred is due to the influence of the change process when the performance status 1125 displays "abnormal" and the impact event displayed in the impact event 1124 belongs to the "ongoing" group. However, control processing 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. 11. For example, the influence process displayed together with the change process name 1111 and the identifier of “ongoing” in the influence event 1124 (that is, information of the entry of the influence event management table 700 stored in the memory as the “ongoing” group in step S1005). ) Group may be displayed.

In the present embodiment, the change process impact management program 225 is executed upon the input of the display instruction by the administrator or the like, but the processing is periodically started to record the acquired or derived information in the memory. 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 the present embodiment, when the value of the status 707 of the entry of the influential event management table 700 of the influential event belonging to the “ongoing” group is “abnormal”, the change process displayed in the change process name 1111 is It may be displayed as a candidate for the cause of the problem that has occurred.

As described above, according to the first embodiment, the execution is performed based on the influence rule in which the influence event of the computer system that the task that constitutes the change process exerts is defined for each task type and the progress status of the change process. The influencing events of the change process inside can be identified according to the progress status of the change process. This allows the administrator to determine, when a problem occurs in the managed computer system, whether the problem occurred is due to the effect of the change process being executed. Only, decisions can be made such as interrupting or reviewing the change process. That is, even if a problem occurs in the managed computer system, it is possible to prevent the administrator from making an erroneous decision 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 description 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 management target computer system, the influence event of the computer system caused by the change process is displayed on the screen according to the progress status of the change process, and the problem caused by the administrator is displayed. By comparing the displayed impact events, it was determined whether the problem was due to the influence of the change process, and further 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 due to the influence of the change process, but also on the contents of tasks constituting the change process and the progress status of the tasks. For example, some tasks can be interrupted depending on the task type, and some cannot. Further, if the progress rate of the change process or task is equal to or higher than a certain value, the influence of the change process on the computer system is short, so that it may be appropriate to make a decision to continue executing the change process or task. These judgments require knowledge about the type of task (for example, VM live migration). Therefore, an administrator who does not have detailed knowledge about the task may make a mistake in determining whether or not the control processing of the change process is necessary by using only the method exemplified in the first embodiment, or it may take time to make the determination. May take. The control process of the change process is, for example, an interruption process of the change process. Further, in the method shown in the first embodiment, the manager must make a judgment in determining whether or not the change process control process needs to be executed. Therefore, the change process control process is automatically judged and executed by software. Can not do it.

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

Regarding the performance information table 300, the configuration information table 400, the change process DB 500, the influence rule table 600, and the influence event management table 700 used in the description of the second embodiment, the same ones as in the first embodiment are used. The structure of each table is the same as that of 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 in order to explain the process of determining the control process of the change process. Further, the control rule generation program 224 and the change process control program 227 are added as new programs, and the processing executed by the system information management program 221 is added. Further, in the second embodiment, the control rule generation program 224 generates new information called control rule information 1400.
<Change process status table according to the second embodiment>

FIG. 12 is a diagram illustrating an example of the data structure of the change process status table 800 according to 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, namely, 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 about the change process or task execution status. On the other hand, the change process status table 800 according to the second embodiment stores the information on the progress rate of the task being executed in order to determine the necessity of control processing of the change process based on the task progress rate. It may further have a task progress rate 806 which 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 “in execution”, and the progress rate of the task is "80%" is shown.
<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 about control rule templates. The control rule template is information indicating a judgment standard of control processing execution and control contents in order to judge whether or not to execute a specific control processing for a change process when a problem occurs in the managed computer system 101. 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 illustrating 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, except for 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 about a change process or a condition for executing a control process on a task is defined. The conclusion unit 1332 has two fields of a controlled object 1308 and a control process 1309. The conclusion section 1332 defines information about the control process executed when all the conditions defined by the condition section 1331 are satisfied.

The rule template ID 1301 stores information that uniquely identifies 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 the same value as the value stored in the task type 503 of the change process list table 591 of FIG. 5A, for example. The table 1303 stores the table name of the table in which the information used for the condition determination of the control rule is stored. The field 1304 stores the field name of the field in the table specified in the table 1303 in which the information used for the condition determination of the control rule is stored. The ID acquisition query 1305 stores a query for acquiring the ID of the entry in which the information used for the condition determination of the control rule is stored.

In the present embodiment, as an example of the information stored in the ID acquisition query 1305, an SQL statement for acquiring the ID of the entry in which the conditional information is stored from the influence event management table 700 or the change process status table 800 is given. .. “@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 of FIG. 5A is substituted. In the present embodiment, the SQL sentence is taken as an example of the means for acquiring the information used for the condition determination of the control rule, but other acquisition means may be used. The acquisition destination may be the managed computer system 101, the hypervisor 235 that manages the execution of the VM live migration, or the orchestration software that manages the change process, instead of the information recorded in the storage area of the management computer.

The operator 1306 stores the operator used for the condition determination of the control rule. The value stored in the operator 1306 may be, for example, the comparison operators “>”, “=”, “≦”, “≠”, or 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 that identifies 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 it may be another value such as “task”. The control process 1309 stores information for identifying the control process executed when the condition part 1331 satisfies the condition. In the present embodiment, the information for identifying the control process of "interruption" is stored, but as other control processes, "continue", "standby", "rollback", "correction" and "reduction" etc. May be Also, a combination thereof may be used. “Fixing” is, for example, the process of interrupting the change process and then changing and executing the remaining tasks so that the change process achieves its purpose and does not affect the detected problem. You can The “reduction” may be, for example, a process of reducing the number of parallel executions when a plurality of tasks are executed in parallel.

In the present 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 in 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 is controlled and is called “suspend”. Indicates that control processing is executed. The control rule generated by the control rule template indicated by the entry 1311 has three conditions. An entry 1321 indicating one of these three conditions has a table in which information used for condition determination is stored as “Impact_management”, a field as “status”, and an entry determined by a task ID and its value. Indicates that the condition is satisfied when is “abnormal” and “equal”.
<Control rule>

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

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

FIG. 14 illustrates an example of the data structure of the 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. FIG.

In the present embodiment, the control rule information is represented by the data structure of the table of the relational database, but another data format may be used.

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 of a table 1404, a field 1405, an ID 1406, an operator 1407 and a value 1408. In the condition part 1431, information on a change process or a condition for executing a control process on a task is defined. The conclusion section 1432 has two fields of a control target 1409 and a control process 1410. The conclusion section 1432 defines information on the control process executed when all the conditions defined by the condition section 1431 are satisfied.

Information that uniquely identifies the control rule information is stored in the control rule ID 1401. The change process ID 1402 stores information that identifies the change process to which the control rule is applied. The value stored in the changed process ID 1402 may be equal to the value stored in the changed process ID 501 of the changed process list table 591 of FIG. 5A, for example. The task ID 1403 stores information that uniquely identifies 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 of FIG. 5A. The table 1404 stores the table name of the table in which the information used for the condition determination of the control rule is stored. The value stored in the table 1404 may be the same value as the table 1403 of the control rule template table 1300 of FIG. 13, for example. The field 1405 stores the field name of the field in the table specified in the table 1403 in which the information used for the condition determination of the control rule is stored. The value stored in the field 1405 may be the same value as the table 1404 of the control rule template table 1300 of FIG. 13, for example. The ID 1406 stores the ID of the entry in the table designated by the table 1403, which stores the information used for the condition determination of the control rule. The operator 1407 stores the operator used for the condition determination of the control rule. The value stored in the operator 1407 may be the same value as the operator 1306 of the control rule template table 1300 of FIG. 13, for example. 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 a value equal to the value 1307 of the control rule template table 1300 of FIG. 13, for example.

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

For example, the entry 1411 in FIG. 14 indicates a control rule identified by an identifier “CntlRule1-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 "interrupt" is applied to the change process "Proc1". The processing 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 in which the information used for condition determination is stored is “Impact_management”, the field is “status”, the ID of the entry is “Impact1”, and the condition is “abnormal” and “equal”. Indicates that it is determined that

In the present embodiment, the condition part of the control rule template stores the information for determining the location where the information for the condition determination is stored, and the control rule template is used to control the rule based on the information of the change process DB 500. Is generated, and the condition part of the control rule stores the information of the place where the information for the condition determination is stored. However, as another means, the control rule template stores information on means for acquiring information for condition determination, and based on the information in the change process DB 500 each time the change process control program 227 described later is executed. Then, 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, when a problem occurs in the managed computer system 101, information of 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. The control rule information 1400 is generated based on

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 processing when information of a new change process is registered in the change process DB 500. Further, this processing may be started at the timing when the information on the influence event is updated in the influence event management table 700. This process may be started when the change process is started. Further, when a problem of the managed computer system 101 is detected by the system information management program 221, this process may be started. This process may be started at any timing after the new change process information is registered in the change process DB 500 or the information of the affected event management table 700 is updated, and before 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, newly registered entries, updated entries, or entries having a change process ID equal to the updated entry.

When the updated entry or all the entries are acquired and the subsequent processing is advanced, 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 of steps S1503 to S1507 for all the entries of 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 a task type 1302 having a value equal to the value stored in the task type 503 of the change process DB entry.

In step S1504, the control rule generation program 224 repeats the processes of 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 substituting the value of the task ID 502 of the change process DB entry for all variables stored in the ID acquisition query 1305 of the control rule template, and is specified in the table 1303. A set of IDs of the table is acquired. Here, in this embodiment, the task ID is assigned to the variable of the query, but when the 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 an 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 the present embodiment, the “change process” is stored in the control target 1308, and therefore the change process ID 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 that uniquely identifies the control rule, and the change process ID 1402 and the task ID 1403 have values of the change process ID 501 and the task ID 502 of the change process DB entry. The table 1404, the field 1405, the operator 1407, the value 1408, and the control processing 1410 store the values of the control rule template table 1303, the field 1304, the operator 1306, the value 1307, and the control processing 1309, respectively. Then, the ID acquired in step S1505 is substituted for the ID 1406, and the ID acquired in step S1506 is stored in the control target 1409.

The specific example of the process of FIG. 15 is as follows.

For example, when the control rule generation program 224 acquires the entry 511 of FIG. 5A in step S1501, it further acquires the control rule template indicated by the entry 1311 of FIG. 13 in step S1503. In step S1505, the control rule generation program 224 substitutes the task ID “Task1” of the entry 511 into the variable of the ID acquisition query 1305, executes this query, and the ID of the entry in which the 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 assigned to 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. 7 is executed. , “Impact2” of the entry 715 is acquired. When “Task1” is assigned to 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 changed process ID 501 of the entry 511 is acquired based on the identification information “changed process” stored in the controlled object 1308 of the entry 1311, and in step S1507, the acquired information is added. Based on this, the control rule information indicated by the entries 1411 and 1412 in FIG. 14 is generated.

In the present embodiment, when at least one influential event of a task is detected, the control rule information 1400 that executes the control process is generated. Therefore, as in the above-described example, a plurality of IDs are output from one query in step S1505. When acquired, the condition part 1431 may be generated by the combination of the acquired IDs, and the control rule information may be generated by the number of acquired IDs. In the above example, when “Task1” is assigned to the query variable of the entry 1321, two IDs “Impact1” and “Impact2” are acquired. Further, when the queries of the entry 1322 and the entry 1323 are executed, the ID “ProcSt1” is acquired respectively. As a result, two control rules 1411 and 1412 shown in FIG. 14 are generated. When it is desired to generate the control rule information for executing the control process including the influential event of all the tasks, the control rule information 1400 having all the IDs acquired in step S1505 in the condition part 1431 may be generated. .. Further, the control rule information for executing the control process may be generated when X% satisfies the condition among the conditions generated by the entry 1321 which is the condition for detecting the influential event. Further, an identifier for switching the generation method of these control rule information for each task type may be defined in the control rule template and the control rule.
<Process 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, the monitoring agent, or the like, and collects the performance information table 300, the configuration information table 400, or the influence. The information of the status 707 in the event management table is updated. In addition to this, in the second embodiment, the system information management program 221 executes the processing 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 according to the second embodiment.

The system information management program 221 may start the processing periodically, or the system information management program 221 may start the processing at the timing when it is 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 managed 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 of the influence event management table 700 according to the value stored in the performance information table 300.

In step S1604, the system information management program 221 updates the status of the metric uniquely identified by the combination of the component ID 301 and the metric type 302 when the value of the performance information table 300 is updated in step S1602 since the last update. It is determined whether or not there is even one metric in which the 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, and if the result of this determination is false (S1604: NO), the process ends.

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

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

In this embodiment, the processing of the change process control program 227 is executed when at least one of the values of the status 305 changes to “abnormal” in the present embodiment. 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 impact management program 225 displays the impact event of the change process according to the progress status of the change process based on the impact event management table 700 and the change process status table 800. In addition to this, in the second embodiment, the change process control program 227 displays the 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 according to the second embodiment.

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 the processing upon receiving the input of the display instruction by the administrator or the like. The trigger for the administrator to input the 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 changed process control program 227 acquires the value of the changed process ID 802 from the changed process status table 800. In the present embodiment, the change process ID to be acquired may be one in which the change process status 803 is stored in the entry of “in execution” or “not executed”.

In step S1702, the changed process control program 227 repeats the processing of steps S1703 to S1708 for all the changed 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 of 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 of the condition part 1431 of the control rule information, the field 1405, and the fields and entries of the table indicated by the set of the IDs 1406.

In step S1706, the change process control program 227 determines whether each piece of 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 part 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, and if the result of this determination is false (S1707: NO), the process continues to execute the iterative process of step S1704.

In step S1708, the change process control program 227 acquires the values stored in the control object 1409 and the control process 1410 of the conclusion unit 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 based on the information stored in the memory in step S1708, displays the information of the control process to be executed on the output device 217.

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

For example, in step S1701, the changed process ID “Proc1” stored in the entry 1212 of FIG. 12 is acquired from the table of the changed process status table 800, and in steps S1703, the entries 1411 and 1412 of the control rule information 1400 of FIG. 14 are acquired. , 1413, 1414 are acquired. In the iterative process of step S1704, as processing for the entry 1413, “normal” stored in the status 707 of the entry 713 of FIG. 7 and “normal” stored in the task status 805 of the entry 1212 of FIG. 12 are processed in step S1705. “Under execution” and “80%” stored in the progress rate 806 are acquired. In step S1706, for example, when paying attention to the condition indicated by the entry 1441, the value obtained in step S1705 is “normal”, whereas the operator 1407 of the entry 1441 has “=” and the value 1408 has “ Since "abnormal" is stored, it is determined that the condition is not satisfied. Therefore, 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" for identifying the change process stored in the control target 1409 of the entry 1413 and information "interruption" for identifying the control process to be executed. Is stored in memory. Then, in step S1709, the display program 226 is activated and information is displayed on the output device 217.

The processing of the change process influence management program 225 of the first embodiment shown in FIG. 10 may be executed before or after the processing shown in FIG. 17, or at the same time.

FIG. 18 shows an example of the screen displayed by the display program 226 in step S1709 in the second embodiment. The change process management screen 1100 is an example of a screen that displays recommended control processing based on the 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. It has a change process name 1111, a change process status 1112, and a task and influence event display area 1113 in order to display the influence event according to the progress status of the change process. On the other hand, the change process management screen 1110 according to the second embodiment may further include a recommended control process display area 1814 to display the control process to be executed for the change process. In the display area 1814, the control process 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 activating 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 parameter for executing the recommended control process may be input to the program to execute the program. Note that 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 values of the status 707 of the entries 711, 712, and 714 are “normal”. The example of the display in the case of

Note that when the sets of control targets and control processes stored in the memory in step S1708 overlap, the recommended control process to be displayed may be one. Further, in the set of control targets and control processes stored in the memory in step S1708, if 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. May be limited to one. As a method of limiting the control processing to be displayed, a priority is set for the control rule template or the control target 1308 of the control rule template table 1300 or the identification information stored in the control processing 1309, and the highest priority is displayed. A method may be adopted.

In addition, when the display content of the recommended control processing display area 1814 is updated, it has a function of notifying the administrator of the information of the recommended control processing display area 1814 by email before displaying the screen. 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 the present embodiment, the recommended control processing display area 1814 is added to the change process management screen 1100 in the first embodiment, but only the recommended control processing display area 1814 may be displayed.

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

In addition, in the present embodiment, the problem that occurs in the managed computer system is aimed at interrupting the change process when it is caused by the effect of the change process, and the effect event of the task under execution of the change process and the problem that has occurred. An example was given where the change process is interrupted if the two are equal. However, even if the problem that occurred is not due to the effect of the task being executed, if the effect event of the unexecuted task and the problem that occurred are the same, the problem caused by executing the unexecuted task becomes worse. In some cases, it may be appropriate to interrupt the change process or cancel its execution so that nothing happens. Therefore, as an example is given in the entry 1312 of FIG. 13, a control rule template for interrupting the change process is defined when the influence event of the unexecuted task becomes abnormal so as not to worsen the occurred problem. May be.

Further, in the present embodiment, the control rule generation program 224 has generated control rule information from the control rule template in advance for all change processes and influential events, but a problem in the managed computer system 101 is detected. When the control rule information is generated from the control rule information, only the control rule information having the influence event equivalent to the detected problem in the condition unit 1431 may be generated. As a result, it is possible to reduce the consumption of the storage area of the management computer 201 and to reduce the number of repetitive processes of step S1704 of FIG. 17 executed by the change process control program 227 to improve the processing speed.

As described above, according to the second embodiment, the influence event of the computer system exerted by the tasks constituting the change process is compared with the influence rule for each task type, the progress status of the change process, and the change process. Whether a specific control process (for example, 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 You can decide As a result, even an administrator who does not have detailed knowledge about tasks can appropriately determine whether or not control processing of the change process is necessary, or can make a determination in a short time. Alternatively, the control process of the changing 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 the same functions, tables having the same items, etc. will be described. , The description may be omitted or simplified.

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

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

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

In this way, if the effect of the task continues to exist even after the task execution is completed, it may be desirable to suspend the execution of the change process regardless of the task progress rate. Further, when the influence of the task continues to exist, it may be desirable to execute control processing such as rollback for 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, while the live migration of the virtual machine is being executed, the CPU load due to the live migration process is generated on the migration source physical server, but after the execution is completed, the load due to the live migration is not generated. As described above, with respect to the temporary influence during task execution, even when a problem occurs after completion of task execution, it is not necessary to execute control processing such as rollback.

Therefore, when a problem occurs in the managed computer system 101, whether not only the influencing event of the task being executed but also the task that has completed execution continuously affects a specific managed component. Is preferably presented to the administrator. Further, also in the control rule described in the second embodiment, it is preferable to define the condition including the influential event due to the task whose execution has been completed.

In the third embodiment, an example will be described in which control processing of a change process is determined, including whether or not a task that has completed execution 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 ones as in the first embodiment may be used. Further, as the change process status table 800, the control rule template table 1300, and the control rule information 1400 used in the description of the third embodiment, the same ones as in the second embodiment may be used. 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, for the sake of explanation, the values stored in the control rule template table 1300 and the control rule information 1400 are changed.

In the third embodiment, the influence rule table 600 and the influence event management table 700 are changed. This is to explain the process of determining the control process of the change process including whether or not the task whose execution has been completed continuously affects a specific managed component. Further, the processing executed by the change process impact management program 225 is also changed.
<Influence rule table of the third embodiment>

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

The structure of the influence rule table 600 in the third embodiment is substantially the same as the structure of the influence rule table 600 in the first embodiment. The influence rule table 600 has four fields, namely, a rule ID 601, a task type 602, an influence component information acquisition query 603, and an influence metric type 604 for storing influence rule information. In addition to these, the influence rule table 600 according to the third embodiment uses the influence period of the influence event of the task derived by the influence rule to determine whether the influence event continuously influences 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 (affects only during task execution)”, “After (affects after completion of task execution)”, “In & After (affects during task execution and after completion of execution)”. In these three patterns, any of these may be stored as identification information in the influence period 605, but identification information indicating another pattern may be stored.

For example, the entry 1911 in FIG. 19 indicates the following. That is, in the impact rule identified by the identifier “ImpactRule1”, the task type to which the impact rule is applied is “VM_LiveMigration”, and the managed component affected by the task is the VM live migration parameter based on the parameter ID of the task. The metric type that is acquired from the migration destination physical server ID 523 of the table 592 and that affects the task is "PS/CPU/utilization", and the impact period of the impact event of the task derived by the impact rule is "running". And “after execution is complete”.
<Influence event management table of the third embodiment>

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

The configuration of the influential event management table 700 in the third embodiment may be substantially the same as the influential event management table 700 in the first embodiment. The impact event management table 700 has seven fields, namely, 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 in order to store information on the impact event for each task. have. In addition to these, the influence event management table 700 according to 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 influences even after the task execution is completed. It may have a field of influence 708. In the present embodiment, the influence periods are “In (affects only during task execution)”, “After (affects after completion of task execution)” and “In & After (affects during task execution and after completion of execution)”. In these three patterns, any of these may be stored as identification information in the influence period 708, but identification information indicating another pattern may be stored.

For example, the entry 2011 in FIG. 20 indicates the following. That is, the influential 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” influences is the “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”. ), 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 influential 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 influential rule table 600 in FIG. It is generated by executing the processing of 222. In the process of the influence analysis program 222 of the third embodiment, when the entry is stored in the influence event management table 700 in step S907 of FIG. 9, the value of the influence period 605 of the influence rule table 600 of FIG. Processing to be stored in the influence period 708 of the influence event management table 700 of FIG. 20 is added.

For the description of the third embodiment, the values stored in the status 707 of the influential event management table 700 of FIG. 20 are the performance information table 300 of FIG. 3 of the first embodiment and the influential event of 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 illustrating an example of the data structure of the control rule template table 1300 according to 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 conditional expression of the query stored in the ID acquisition query 1305. This is to determine whether or not to execute the control processing for the change process, including whether or not the influential 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 is abnormal due to the influence of the task being executed and the influence period is “In (only during execution)”, the progress rate is 90%. If less, it indicates that the modification process is to be aborted. That is, if the progress rate is 90% or more, the period for causing a problem is sufficiently short, and the change process continues 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 completion of execution)” 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 is continuously generated even after the task is completed.

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

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

FIG. 23 is a diagram illustrating an example of the data structure of the control rule information 1400 according to 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 differs from that of the second embodiment.

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

In the third embodiment, by the processing of the change process control program 227 shown in FIG. 17 of the second embodiment, the control processing to be executed for the change process is determined based on the control rule of the control rule information 1400. It In the third embodiment, the changed process ID may be acquired from all the entries stored in the changed process status table 800 in step S1701 of the process of the changed process control program 227 shown in FIG. Alternatively, the change process ID to be acquired may be selected based on the 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. The change process ID acquired in step S1701 may be the change process ID of an entry whose change process status is “in execution” or “not executed”. Alternatively, it may be the change process ID of an entry whose change process status is “completed” and whose completion time is within a fixed time from the current time.
<Processing of Change Process Impact Management Program of Third Embodiment>

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

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

The start timing of the change process impact 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 the process of the change process control program 227 shown in FIG. 17 or in parallel with the process.

In step S2201, the change process impact 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 processing of steps S2203 to S2211 for all the entries of the change process status table acquired in step S1201.

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

In step S2204, the change process impact management program 225 repeats the processes of steps S2205 to S2211 for all the entries of the obtained 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 affected event management table.

In step S2206, the change process influence management program 225 determines whether the value stored in the task status 805 of the entry of the change process status table 800 is “in execution”. If the result of this determination is true (S2206: YES), the process proceeds to step S2207, and 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, and if the result of this determination is false (S2207: NO), the process continues to execute the iterative process of step S2202.

In step S2208, the change process impact management program 225 determines whether the value stored in the task status 805 of the entry of the change process status table 800 is “complete”. When the result of this determination is true (S2208: YES), the process proceeds to step S2209, and when the result of this determination is false (S2208: NO), the process continues to execute the iterative process of step S2202.

In step S2209, the change process impact management program 225 determines whether the value of the impact period acquired in step S2204 is “After” or “In&After”. When the result of this determination is true (S2209: YES), the process proceeds to step S2211, and when the result of this determination is false (S2209: NO), the process continues to execute the iterative 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, based on the acquired entry of the change process status table 800 and the information stored in the memory in steps S2210 and S2211, changes the processes, tasks, and their influence at the start of the change process impact management program 225. Is displayed on the output device 217.

Note that, in step S2201, when the change process impact management program 225 acquires an entry from the change process status table 800, the entry to be acquired may be selected based on the 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 “in execution” or “not executed”. Alternatively, the change process status may be “completed” and the completion time may be limited to the entry within the fixed time from the current time.

The specific example of the process 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 iterative process of step S2202, the change process impact management program 225 acquires the entry 2013, the entry 2014, and the entry 2017 of FIG. 20 in step S2203. Next, when the process is performed on the entry 2013 in the iterative process of step S2204, the task status of the entry 1212 of the change process status table 800 is “in execution”, and the value of the influence period 708 of the influence event management table 700 is “In & After”. Therefore, the processing proceeds to step S2210 by the determination processing of steps S2206 and S2207. Then, in step S2210, the entry 2013 is recorded in the memory as an “ongoing” group. Then, in step S2212, the display program is activated and the information is displayed on the output device 217.

FIG. 24 shows an example of the screen displayed by the display program 226 in step S2212 of FIG. 22 and step S1709 of FIG. 17 in the third embodiment. The change process management screen 1100 is based on the information acquired or stored by the change process impact management program 225 of FIG. 22 and the change process control program 227 of FIG. 7 is an example of a screen on which a control process for displaying 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 the influence event according to the progress status of the change process. Further, the change process management screen 1100 may further include a recommended control process display area 1814 to display the control process to be executed for the change process.

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

In the influential event 1124 of the third embodiment, the influential event for each task may be displayed based on the entry information of the influential event management table 700 acquired in step S2203 of FIG. Further, in step S2210 or step S2211, when the group is stored in the memory as the “ongoing” group or the “completed/ongoing” group, as shown in the display area 1144 of 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 occurred occurs in the change process. It may be determined that the change process is caused by the above, and control processing such as interrupting or rolling back 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 the present 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 in the influence rule whether or not the influence by the task continues even after the completion of the task execution, and based on the definition, the influence event of the change process. , Or whether or not a particular control process for the modification process should be performed. This allows you to consider whether the tasks that make up the change process affect a particular managed component only while it is running, or continuously after the run is complete. You can judge whether or not.

In the above-described first to third embodiments, live migration in which a physical server is moved while a virtual machine is operating is given as an example of a task, but another change process may be used.

For example, the task may be volume migration in which a logical volume (logical storage device) of a storage device moves between RAID (Redundant Arrays of Independent Disks) groups. A RAID group is a group in which a plurality of physical storage devices are grouped by RAID technology, and a logical volume is a LU that cuts out a partial physical area of the RAID group and is logically accessible as one storage resource from a computer ( Logical Unit). The influential events caused by volume migration include, for example, an increase in the operating rate of the migration destination RAID group and a decrease in the response time of the logical volume on the migration destination RAID group. Further, when the copy function such as taking a snapshot regularly is applied to the logical volume on the storage device for which volume migration is performed, the copy speed of the logical volume to which the copy function is applied decreases. The influential event also occurs. As described in the third embodiment, there are some influential events that occur only during task execution and some that occur continuously even after task execution is completed. The decrease in the response time of the volume is an influential event that occurs continuously. On the other hand, the decrease in the copy speed of the logical volume is an influential event that occurs only during execution of volume migration. Using the above-described volume migration as one of the tasks and using the above-described influential event as a method according to the first to third embodiments, the influential event of the change process is displayed or recommended for the change process. You may implement the display of control processing.

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

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

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

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

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

Further, in the control rule template of the second embodiment or the third embodiment, it is determined whether or not the control process needs to be executed depending on whether or not the influential event caused by the task is in the "abnormal" state. The condition section 1331 may define a condition in consideration of the “magnitude of the effect 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, when the CPU usage rate and memory usage of the moving virtual machine (vm1) are small, while the CPU usage rate of the virtual machine (vm3) is large, there is no contribution to the increase in 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 even if the movement of the virtual machine (vm1) is interrupted, the abnormal CPU usage of the physical server (PS2) cannot be resolved, and therefore it may be determined that the change process is not interrupted. is there.

Such a determination may be incorporated in the condition part 1331 of the control rule template. For example, when the CPU usage rate (VM/CPU/utilization) of the moving virtual machine is acquired from the performance information table 300 in the condition part 1331 of the control rule template of FIG. You may add the condition which determines. Further, a condition may be added in which the rate of increase in the CPU usage rate of the mobile virtual machine is calculated and a true determination is made when the rate is higher than a certain value.

The rate of increase is a value that can be calculated by the following formula 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 condition part 1331 of the control rule template of FIG. 13 is compared with the following condition, that is, the CPU utilization rate of the moving virtual machine and the CPU utilization rate of the virtual machine on the destination physical server are compared. The condition for determining true when the increase rate of 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 is 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 the control rule template shown 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 the control rule template for comparing the increase rate of the CPU usage rate of the moving virtual machine with the increase rate of the CPU usage rate of the virtual machine existing first on the migration destination physical server. .. The value 1307 of the control rule template table 1300 shown in the figure is not a fixed value, but a query is stored so that the value can be acquired from the table. When the control rule information 1400 is generated from the control rule template table 1300, the value 1408 of the control rule information 1400 is acquired in the variable "@TaskId" of the query stored in the value 1307 in step S1501 of the control rule generation program 224. The query in which the task ID of the entered entry is substituted is stored. Then, when the control rule information 1400 is applied, the query of the value 1408 is executed, the specific value is specified, and the condition determination is performed based on the value. When a plurality of values are specified by the query stored in the value 1408, each value is compared with the value determined by the table 1404, the field 1405, and the ID 1406 according to the operator 1407 to determine whether it is true or false. .. Then, when at least one of the values specified by the query of the value 1408 is determined to be true, or when a value equal to or more than a certain ratio is determined to be true, the condition shown in FIG. 26 may be set to be true.

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

101 management target computer system 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 Impact Rule Table 700 Impact Event Management Table 800 Change Process Status Table

Claims (15)

A management computer that manages the computer system to be managed,
The management computer has a central processing unit and a storage device,
The storage device is
Configuration information about the configuration of the components that make up the managed computer system,
Change process information relating to a change process for changing the configuration of a component of the management target computer system, the value uniquely identifying the change process, the value uniquely identifying a task configuring the change process, and including a task type of task, and information about the parameters is a set value to be set for the task, and changing process information,
Impact rules to identify the impact event that occurs by executing the task for each task type,
The execution status of the tasks constituting the change process is stored,
The central processing unit is
Based on the task type of the task that constitutes the change process indicated by the change process information and the influence rule, a process of specifying an influence event for each task when the change process is executed,
When a display instruction is input or when the status of the performance information of the component becomes abnormal, the task being executed in the change process indicated by the change process information is based on the execution status of the task. And a processing computer for identifying the influential event of the task being executed. The central processing unit is
The management computer according to claim 1, further comprising a process of outputting an influencing event of the identified task under execution. The influencing event is an influencing component and an influencing metric,
The storage device is
Further stores information indicating the state of the component, including observations of multiple metrics,
The central processing unit is
The management computer according to claim 2, which performs a process of outputting the state of the component related to the affecting event of the task being executed according to the observed value of the metric related to the affecting event of the task being executed. The influencing event is an influencing component and an influencing metric,
The storage device is
Information that shows the state of the component, including observations of multiple metrics,
A control process for a change process defined for each task type, and a control rule template that includes a criterion for determining whether or not the control process can be executed, based on an influential event for each task type, and further stored.
The central processing unit is
A process of generating a control rule including a control process for the change process and a criterion for determining whether or not the control process can be executed, based on the task type of the task configuring the change process and the control rule template;
Observation value of metrics related to the influencing event of the task being executed, and based on the generated control rule, a process of determining whether or not to execute the control process for the change process defined in the control rule,
The management computer according to claim 1, further comprising: a process of displaying a determination result of whether or not to execute the control process. The management computer according to claim 4, wherein the criterion of the control rule template includes an execution status of a change process or a task. The management computer according to claim 5, wherein the criterion of the control rule template includes the progress status of the tasks constituting the change process. The central processing unit is
The management computer according to claim 4, further comprising a step of executing a control process defined in the control rule when the result of the determination as to whether or not the control process is necessary is execution. 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 the comparison between the rate of increase of the observed value of the specific metric of the component changed by the execution of the task and the rate of increase of the observed value of the specific metric of the component 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 that constitutes the change process information and the influence rule, the 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: a process of outputting the influencing event according to an execution status of the change process and a task configuring 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 judgment criterion of the execution possibility,
The central processing unit is
Execution of control processing for the change process defined in the control rule based on the observed value of the metric related to the influential event of the task being executed, the control rule, and the execution status of the task configuring the change process The management computer according to claim 4, which determines necessity. The central processing unit is
The management computer according to claim 3, wherein when the status of the component affected by the task is "abnormal", the change process related to the task is displayed as a cause candidate of the problem. A method of 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 is
Configuration information about the configuration of the components that make up the managed computer system,
Information about a change process for changing the configuration of a component of the management target computer system, the value uniquely identifying the change process, the value uniquely identifying a task configuring the change process, and the task including a task type, and a information about the parameters is a set value to be set for the task, and changing process information,
Impact rules to identify the impact event that occurs by executing the task for each task type,
The execution status of the tasks constituting the change process is stored,
The central processing unit is
Based on the task type of the task that constitutes the change process indicated by the change process information and the impact rule, a process of identifying an impact event for each task when the change process is executed,
When a display instruction is input, or when the status of the performance information of the component becomes abnormal, the task under execution in the change process indicated by the change process information is displayed based on the execution status of the task. And a process of identifying and identifying an influential 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 is
Configuration information about the configuration of the components that make up the managed computer system,
Information about a change process for changing the configuration of a component of the management target computer system, a value that uniquely identifies the change process, a value that uniquely identifies a task that constitutes the change process, and a value of the task. including a task type, and a information about the parameters is a set value to be set for the task, and changing process information,
Impact rules to identify the impact event that occurs by executing the task for each task type,
The execution status of the tasks constituting the change process is stored,
When the computer program is executed by the central processing unit,
Based on the task type of the task that constitutes the change process indicated by the change process information and the influence rule, a process of specifying an influence event for each task when the change process is executed,
When a display instruction is input or when the status of the performance information of the component becomes abnormal, the task under execution in the change process indicated by the change process information is displayed based on the execution status of the task. A computer program that performs a process of specifying and specifying an influencing event of the task being executed.

Images