JPWO2018047325A1 - Manager, method and computer program for managing a computer system to be managed - Google Patents

Abstract

When a problem occurs in the computer system while executing a configuration change or setting change on the computer system, it is determined whether the problem that has occurred is due to the influence of the configuration change or the setting change. Define the rule that defines the influence event of configuration change or setting change for each type of configuration change or setting change, and the configuration information of computer system, parameter of configuration change or setting change, execution status of configuration change or setting change When a problem occurs in the computer system, an influence event due to a configuration change or setting change being executed is identified.

Description

  The technology disclosed herein relates to a management computer that manages a computer system.

  In the management of a computer system, it is required that devices constituting the computer system, parts thereof, and services provided by the computer system continue to operate normally. Therefore, recovery processing or preventive processing may be executed to solve the problem when a problem occurs in the computer system or to prevent the occurrence of the problem. For example, if there is a problem that the performance of a device that constitutes a computer system is abnormally reduced, by changing the configuration or setting of the device or software based on the past performance value of the software operating on that device. The problem may go away. Also, configuration changes are frequently implemented 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 to be provided is detected during the change execution, it may be necessary to take action such as interrupting or reviewing 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 determined by the computer system administrator based on whether the problem that has occurred is due to the effect of the change process.

  The effect of the change process is, for example, a decrease in the performance of the device or software caused by the load on the device and the consumption of resources that occur in executing the change process. However, the configuration of computer systems in recent years is large and complex, and the effects caused by the contents and progress of configuration changes and setting changes are also different. Therefore, it is difficult to identify the impact event of the change process and to judge whether the change process should be interrupted or reviewed. Therefore, the computer system administrator may make an erroneous judgment such as interrupting the change process that does not need to be interrupted.

Patent document 1: JP 2009-217587 WO2015 / 040688

  According to the technology disclosed in Patent Document 1, in the field of batch job management of batch processing, there is a technology of interrupting a specific processing according to the state of computer resources used by a batch job. However, while the technology disclosed in Patent Document 1 has fixed computer resources consumed by batch processing and batch jobs that configure it, in the case of a computer system change process, the contents and processing of processing to be executed The range and events that affect the target and the execution status of the process differ.

  According to one embodiment of the present invention, a management computer which manages a computer system to be managed includes a central processing unit and a storage device. The storage device is configuration information related to the configuration of components constituting the computer system to be managed, and change process information on a change process to change the configuration of the components of the computer system to be managed, comprising the change process Storing the change process information including the tasks and parameters to be performed, the influence rule for specifying the influence event caused by the execution of the task for each task type, and the execution status of the tasks constituting the change process. The central processing unit identifies, based on a task type of a task constituting the change process information and the influence rule, an influence event for each task when the change process is executed, and an execution state of the task And identifying a task being executed based on and identifying an influence event of the task being executed.

  According to the present invention, when a problem occurs in a 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 overview 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 may be applied. 3 illustrates an exemplary data structure of a performance information table of the first embodiment. 5 illustrates an exemplary data structure of a configuration information table of the first embodiment. 5 illustrates an exemplary data structure of a change process DB of the first embodiment. 5 illustrates an exemplary data structure of a change process DB of the first embodiment. 3 shows an exemplary data structure of an influence rule table of the first embodiment. 5 illustrates an exemplary data structure of an influence event management table of the first embodiment. 5 illustrates an exemplary data structure of a change process status table of the first embodiment. The processing 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. The display program of 1st Embodiment shows an example of the change process management screen displayed on a display. 5 illustrates an exemplary data structure of a change process status table of the first embodiment. 7 illustrates an exemplary data structure of a control rule template table of the second embodiment. 6 illustrates an exemplary data structure of control rules of the second embodiment. The processing example of the control rule generation program of 2nd 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. The display program of 2nd Embodiment shows an example of the change process management screen displayed on a display. 14 shows an exemplary data structure of an influence rule table of the third embodiment. The example data structure of the influence event management table of 3rd Embodiment is shown. 14 illustrates an exemplary data structure of a control rule template table of the third embodiment. 14 illustrates 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. 14 illustrates an exemplary data structure of control rules of the third embodiment. The display program of 3rd Embodiment shows an example of the change process management screen displayed on a display. 6 shows an exemplary data structure of a performance increase rate table. The example of the conditions in the case of adding "magnitude of influence by a task" to the condition part of a control rule template is shown.

  DETAILED DESCRIPTION In the following detailed description of the present invention, reference is made to the accompanying drawings which form a part of the disclosure, which illustrate exemplary embodiments in which the present invention may be practiced and is not intended to limit the present invention. In these drawings, the same reference numerals indicate the same components throughout the drawings. Moreover, while the detailed description provides various exemplary embodiments, the present invention is not limited to the embodiments described and illustrated herein, as described and illustrated below, and those of ordinary skill in the art may Note that it can be extended to other known or later known embodiments.

  When reference is made herein to "this embodiment", the particular features, structures or characteristics described in the context of that embodiment are meant to be included in at least one embodiment of the present invention. The appearances of these phrases throughout the specification are not necessarily all referring 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 may be required to practice the present invention. In other situations, well-known structures, materials, circuits, processes and interfaces may not be described in detail and / or may be shown in block diagram form in order not to obscure the present invention unnecessarily.

  Moreover, portions of the detailed description that follow are presented as algorithmic and symbolic representations of operations within the computer. These algorithmic descriptions and symbolic representations are the means used by those skilled in the data processing arts to effectively convey the substance of their invention to others skilled in the art. An algorithm is a series of defined steps leading to a desired final state or result. In the present invention, the steps performed require physical manipulation of tangible quantities to achieve tangible results.

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

  Unless clearly stated otherwise, it is clear from the following description that the terms “process”, “calculate”, “calculate”, “determine”, “display” etc. are used throughout the description of this specification. The description used manipulates the computer system or data represented as physical (electronic) quantities in the registers and memory of the computer system to store, transmit or otherwise store the memory or registers or other information of the computer system. Other operations of the information processing apparatus and processing may be included to convert into other data similarly expressed as physical quantities in the display device.

  The invention also relates to an apparatus for performing the operations herein. The apparatus may be specially constructed for the required purpose, or may include one or more general purpose computers selectively activated or reconfigured by one or more computer programs. Such computer programs may be stored on computer readable storage media such as, for example, optical disks, magnetic disks, 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 various general purpose systems may be used with the programs and modules according to the teachings herein, it may prove convenient to construct a more specialized apparatus for performing the desired method steps. The structure of these various systems will become apparent in the description disclosed below. The invention also does not describe any particular programming language as a premise. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described below. The programming language instructions may 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 is described by expressions such as "aaa table", "aaa list", "aaaDB", etc., but such information is expressed by other than data structure such as table, list, relational database etc. It may be Therefore, "aaa table", "aaa list", "aaaDB", etc. may be called "aaa information" to indicate that they do not depend on the data structure.

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

  In the following description, the term "program" may be used as the subject, but since the program performs processing defined by being executed by the processor using the memory and the communication port (communication control device), the processor is the subject The explanation may be Further, the processing disclosed with the program as the subject may be processing performed by a computer such as a management server or an information processing apparatus. Also, part or all of the program may be realized by dedicated hardware.

  Also, various programs may be installed on each computer by a program distribution server or a storage medium readable by a computer.

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

  Hereinafter, a set of one or more computers that manage computer systems and display 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 combination of a management computer and a display computer may be a management system. In addition, in order to speed up the management processing and to improve reliability, processing equivalent to the management computer may be realized by a plurality of computers. In this case, the plurality of computers (for display when display computer performs display) The computer may also be a management system). The "display information for display" by the management computer may be to display the display information on a display device of the management computer, or the management computer (for example, a server) may be a remote display computer (for example, a client) May be to transmit display information). Also, in the following description, when different elements of the same type are described separately, the reference symbols of the elements are used, and when the elements of the same type are described without distinction, the common parent of the reference symbols of the elements May use a sign. For example, the server 202 may be described as the server 202 if the servers are described without particular distinction, and may be described as the servers 202 a and 202 b when the individual servers are described separately.

In the following description, one or more operations for configuration change applied to a computer system for one purpose, one or more operations for configuration change, etc. It is called. Furthermore, individual change operations constituting the change process are called "tasks", and setting values to be set for the tasks to execute the tasks are called "parameters".
First Embodiment

  According to the present embodiment, in the management of the devices configuring the computer system, when the change process is started for the device and the software, a device that displays an 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 impact event of the change process is determined by the progress of the change process, the rules for determining the impact event caused by the change process, and the content of the execution of the change process.

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

  According to the present embodiment, the management computer 201 is a computer that manages at least one device that configures the management target computer system 101. The devices configuring the management target computer system 101 include, for example, a computer represented by a server, and a network device represented by an IP (Internet Protocol) switch. Moreover, in the IoT (Internet of Things) field, it may be a device (IoT device) attached with a sensor or a computer connected to the Internet. Also, logical or physical elements included in one managed device include, for example, ports, processors, storage resources, physical storage devices, programs, and virtual machines.

  In the present embodiment, data is stored in the storage area of the management computer 201, for example, in the following table format.

  The configuration information table 400 is a table for storing configuration information of the management target computer system collected by the system information management program 221. The change process DB 500 is a table that stores tasks constituting the change process to be executed and its parameters. The tasks and their parameters may be, for example, an API that operates an apparatus and software that configure a computer system and its arguments. Also, the change process may be a script that executes the API. The influence rule table 600 stores tasks and task influence events in a format that does not depend on the execution targets of the tasks. The change process status table 800 stores the progress of change processes and tasks being executed.

  The outline of the process in the present embodiment will be described below.

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

  In the present embodiment, when a problem in the computer system (for example, an abnormal decrease in the performance of a device provided by the computer system or a service provided by the computer system) is detected, the change process is triggered by the change process. Impact events are identified. The identified impact event may be displayed in response to the request of the computer system administrator. This allows the administrator to compare the content of the detected problem with the impact event of the change process, and confirm whether the problem occurred is due to the impact event of the change process. That is, the administrator can appropriately control the change process in a short time.

The first embodiment will be described in detail below.
<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 servers 230 are 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 is a general-purpose computer to which these devices are connected via a system bus 216. It is good. The disk 213 is, for example, a hard disk drive (HDD), but instead, another nonvolatile storage device such as a solid state drive (SSD) may be adopted. As a logical module of the management computer 201, for example, a system information management program 221, an influence analysis program 222, a change process status management program 223, a control rule generation program 224, a change process influence management program 225, a display program 226, a change process control program 227 And. Also, 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 for storing the performance information and configuration information of the management target device collected from the management target device by the system information management program 221 and the physical and logical elements constituting it. is there. The performance information table 300 and the configuration information table 400 may not be held by the management computer 201 but may be held by the respective management target devices. In this case, when referring to configuration information or performance information, the management computer 201 may access each management target device via the network 220 to acquire information.

  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, and the change process control program 227 are stored in the memory 212. Is executed by The performance information table 300, the configuration information table 400, the change process DB 500, the influence rule table 600, the influence event management table 700, the change process status table 800, the control rule template table 900 and the like are stored in the disk 213. At least one of these programs or at least one data may be stored in another appropriate storage area to which the CPU 211 can refer.

  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 detail in the second embodiment.

  The network I / F 215 acquires information on a device and its components such as configuration information and performance information from a management target device such as the physical server 230 connected via the network 220. The output device 217 is a device that outputs (typically displays) information from the display program 226. The input device 214 is a device that 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 other devices may be used.

  The physical server 230 may be a management target device that executes a program such as an application. The server 230 may be a general-purpose computer including a memory 232, a network I / F 233, and a CPU 231 connected thereto. The physical server 230 may have, in addition to the memory 232, a non-volatile storage device such as an HDD. The physical server 230 may have a hypervisor 235 capable of logically generating and executing virtual machines 234. The hypervisor 235 can control multiple virtual machines 234 at one time. Each virtual machine 234 can execute application programs as if it were a stand-alone physical computer by allocating and allocating computer resources such as the CPU 231 and memory 232 of the physical server 230 by the hypervisor 235.

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

  As means for collecting configuration information and performance information of the management target computer system including the physical server 230, the physical server 230 has a monitoring agent (program) instead of collecting the information possessed by the hypervisor 235, and monitoring The agent may transmit at any time.

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

  The performance information table 300 stores performance information of a management target device or components thereof (hereinafter, the management target device and components may be collectively referred to as a management target component). This performance information may be collected by the system information management program 221 from the hypervisor 235 or the like, or from the monitoring agent. The system information management program 221 may periodically start processing to 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 update the information in the performance information table 300.

  FIG. 3 is a view for explaining an example of the data structure of the performance information table 300. As shown in FIG.

  The performance information table 300 comprises five fields: component ID 301, metric type 302, time 303, performance value 304, and status 305.

  The component ID 301 stores a value that uniquely identifies a managed component. The metric type 302 stores a value identifying an observation item of performance of the managed component. The time 303 indicates the time at which the performance of the managed component was 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 as to whether the observed value is abnormal. An example in which the determination result “abnormal” is stored in the status 305 may be a case where the value stored in the performance value 304 exceeds a static threshold preset for each metric type. In addition, when a threshold value of performance value is set in advance for each set of metric type and managed component, it may be determined as “abnormal” when the observed performance value exceeds the threshold value. The threshold may be calculated dynamically. For example, for a particular metric type of a particular managed component, a dynamic threshold may be set based on performance values over a past fixed period. Furthermore, in the present embodiment, only “normal” and “abnormal” are defined as identification information indicating 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, the system information management program 221 detects the set of the management target component and the metric type in which the status 305 is stored as “abnormal” and the metric type as a problem that occurs in the management target computer system 101. The mail function or the output device 217 may be used to notify that.

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

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

  FIG. 4 is a view for explaining an example of the data structure of the configuration information table 400 for storing configuration information of the physical server 230.

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

  Further, in the configuration information table 400, the information of the table may be updated along with the configuration change of the management target component. When the information of the configuration information table 400 is updated, the information before the update may be recorded, and may be saved as history information so that past configuration information can be referred to.

  The configuration information table 400 comprises two fields: 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 a 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. 3.

  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”. It indicates that the virtual machine identified by the identifier (here, the virtual machines 234a and 234b in FIG. 2) is operating.

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

  The change process DB 500 stores information on a change process scheduled to be executed, being executed, or completed for the management target computer system 101. The change process consists of tasks and parameters.

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

  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 workflow information from the orchestration software and store it. Alternatively, it may be input according to the procedure manual of the operation executed by the administrator. Alternatively, the management computer 201 may acquire and store information on a plan derived by the configuration change plan generation function represented by Patent Document 2.

  The determination of whether the process is to be performed or a change process being performed may be input by the administrator. Alternatively, when using an execution scheduler function of batch job management software or orchestration software, information may be acquired from the scheduler function to determine the execution state of the change process.

  In the present embodiment, information on the change process is stored in the change process DB 500 of the storage area of the management computer 201. However, a method may be adopted in which information is acquired from script files, orchestration software, etc. at the timing of using the information. .

  5A and 5B are diagrams for explaining 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 a change process. Therefore, in the present embodiment, the change process DB 500 is configured of a change process list table 591 for storing a change process list, and a VM live migration parameter table 592 for storing parameters of VM live migration tasks constituting 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 uniquely identifying the change process. The task ID 502 stores a value that uniquely identifies a task. In the present embodiment, even if the contents of the change process and the contents of the task are the same, another ID is assigned to the change process or task executed at different timings. For example, if the change process is a script and the task included in the change process is an API, even if the contents of the script file to be executed, that is, the API written in the script and the arguments passed to the script are all the same If the script is executed at different times, 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 of FIG. 5A indicates that the change process identified by the identifier “Proc1” includes two tasks identified by the identifiers “Task1” and “Task2”. Furthermore, the two tasks belong to the type (in this case, VM live migration) identified by the identifier “VM_LiveMigration”, and the parameters identified by “Param1” and “Param2” are respectively passed to the two tasks. It is shown.

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

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

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

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

  In the influence rule table 600, rules for deriving an influence event are stored for each task constituting the change process registered in the change process DB 500. In the present embodiment, one example of the influence event is the performance of the managed component whose value fluctuates under influence when one task is executed. This is an example, and the impact event is not limited to the performance of the managed component. The influence event may be an event that can be observed by the manager of the management computer 201 or the computer system 101. For example, the information may be status information represented by “success” or “failure” of another task.

  In the present embodiment, the influential event is a set of managed components and performance metric types affected by one task, but may be expressed using other information.

  FIG. 6 is a view for explaining an example of the data structure of the influence rule table 600. As shown in FIG.

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

  The rule ID 601 stores a value for uniquely identifying an influence rule. 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, for example, the value stored in the task type 503 of FIG. 5A. The influential component information acquisition query 603 stores a query for acquiring information on managed components affected by a certain task. In the present embodiment, an example of the information stored in the influenced component information acquisition query 603 is a SQL statement acquired from the configuration information table 400 or the change process DB 500 for acquiring the ID of the component affected by the task. ing. “@ Param” of 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 statement is taken as an example of a means for acquiring information of components affected by a task, but other acquisition means may be used. The information acquisition destination 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 even the orchestration software that manages the change process. Good. The influence metric type 604 stores a value that uniquely identifies the metric type that a certain task affects. The value stored in the influence metric type 604 may be, for example, a value equal to the metric type 302 in FIG. 3.

For example, the entry 611 in FIG. 6 indicates that, in the influence rule of the identifier “Impact Rule 1”, 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 that the task affects 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. Furthermore, the entry 611 indicates that the metric type that the task influences is the metric type identified by the identifier “PS / CPU / utilization”.
<Influence event management table>

  The influential event management table 700 stores information on the influential events of each task derived based on the influential rules stored in the influential rule table 600 of FIG. In the present embodiment, the influential event is represented by a combination of the ID of the managed component affected by one task and the metric type, which is an observation item of performance, but may be represented by other information. . Also, the impact event may be other than the performance of the managed component.

  FIG. 7 is a view for explaining an example of the data structure of the influence event management table 700. As shown in FIG.

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

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

  For example, entry 711 in FIG. 7 indicates that the influence event identified by “Impact 1” has the following content. That is, the change process “Proc1” has an event affected by “Task1” whose task type is “VM_LiveMigration” is “VM / VM” of the virtual machine (here, the virtual machine 234c in FIG. 2) identified by “vm3”. Indicates that the metric is identified by "CPU / contention" (here, the CPU contention rate of VM). Furthermore, the entry 711 indicates that the current performance value of “VM / CPU / contention” is “abnormal”.

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

  The change process status table 800 stores information on the progress of change processes and tasks monitored by the change process status management program 223. The progress of the task may be obtained from the hypervisor 235 if the task to be performed is VM live migration. Moreover, when it is a task of other types, you may acquire from the program which manages each task.

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

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

  FIG. 8 is a view for explaining an example of the data structure of the change process status table 800. As shown in FIG.

  The change process status table 800 includes five fields: an ID 801, a change process ID 802, a change process status 803, a task ID 804, and a task status 805. The ID 801 stores a value that uniquely identifies an entry of the change process status table 800. The change process ID 802 stores a value uniquely identifying the change process. The value stored in the change process ID 802 may be, for example, a value equal to the value stored in the change process ID 501 of the change process list table 591 of FIG. 5A. The change process status 803 stores a value 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 “not performed”, and identification information indicating these may be stored in the change process status 803. The task ID 804 stores a value uniquely identifying a 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 tasks that make up the change process. In the present embodiment, the task execution status may be divided into three states of “completed”, “in progress”, and “not executed”, and identification information indicating these may be stored in the task status 805.

For example, the entry 812 indicates that the execution status of the change process identified by the identifier “Proc 1” is “in progress”, and among the tasks constituting the change process “Proc 1”, the task identified by “Task 2” is Indicates "in progress".
<Process of impact analysis program>

  The influence analysis program 222 identifies an influence event by the change process and the task based on the information of the configuration information table 400, the change process DB 500, and the influence rule table 600, and registers the information in the influence event management table 700.

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

  The impact analysis program 222 may start this process when information on a new change process is registered in the change process DB 500. This process may also be started at the timing when the information on the change process is updated in the change process DB 500. The control rule generation program 224, the change process influence management program 225, or the second embodiment describes the process after the new change process information is registered in the change process DB 500 or the information on the registered change process is updated. This process may be started at an arbitrary timing until the change process control program 227 is started. Also, if the task being executed is to execute the configuration change of the managed computer system 101, the impact event of another task may also change depending on the completion of the task, so every time one task is completed This process may be started.

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

  Note that when acquiring the updated entry and all the entries and proceeding with the subsequent processing, the change process DB acquired among the entries of the influence event management table 700 in order to update the information of the influence event. The entry associated with the entry may be deleted.

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

  In step S 903, the influence analysis program 222 acquires, from the influence rule table 600, an influence rule having in the task type 602 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 processing of steps S905 to S909 for all the influence rules acquired in step S903.

  In step S 905, the influence analysis program 222 substitutes the value stored in the parameter ID 504 of the change process DB entry for the variable of the influence component information acquisition query 603 of the influence rule, executes the query, and affects the task. Get all the identification information of affected managed components (affected component ID).

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

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

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

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

  The 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. When executing processing for the entry 611 in the iterative processing of step S904, in step S905, substitute the parameter ID "Param 1" for the variable of the influenced component information acquisition query 603, and generate and execute the query shown below. As “influential component ID,” “PS2” is acquired from the migration destination physical server ID 523 of the VM live migration parameter table 592 in FIG. 5B.
SELECT destination physical server ID FROM VM_LiveMigration_Parameter
WHERE Parameter ID = “Param1” ... (1)

Then, the information from the ID 701 of the entry 711 in FIG. 7 to the influence metric type 706 is stored in step S 907, the entry 314 is acquired from the performance information table 300 in FIG. 3 in step S 908. The information “abnormal” stored in the status 305 of the entry 314 is stored in the status 707.
<Processing of Change Process Impact Management Program>

  Based on the influence event management table 700 and the change process status table 800, the change process influence management program 225 displays the change process influence events according to the progress of the change process.

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

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

  In step S1001, the change process 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 with respect to the change process status entry acquired in step S1001.

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

  In step S1004, 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 “during 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 influence event management table 700 in step S1003 in the memory as the "ongoing" group.

  In step S1006, the change process impact management program 225 starts the display program 226, and changes processes, tasks, and the like based on the acquired entry of the change process status table 800 and the information stored in the memory in step S1005. Displays on the output device 217 the information of the event affecting at the start of the change process impact 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. When the entry 812 is targeted in the repetitive process of step S1002, the change process influence management program 225 acquires the entry 713 and the entry 714 of FIG. 7 in step S1003. Then, in the determination process in step S1004, since "executing" is stored in the task status 805 of the entry 812, the process proceeds to step S1005, and in step S1005, the change process influence management program 225 includes the entry 812 and the entry The sets of 713 and 714 are recorded in the memory as an "ongoing" group, and in step S1006, the display program is activated and information is displayed on the output device 217.

  In the first embodiment, an example of a screen displayed by the display program 226 in step S1006 is shown in FIG. 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 influence event based on the information acquired and stored by the change process influence management program 225.

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

  In the change process name 1111, identification information of the change process may be displayed in a format understood by the administrator based on the information of the change process ID 802 of the entry of the change process status table 800 acquired in step S1001 of FIG. . The change process status 1112 may display the progress of the change process 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.

  The task and influence event display area 1113 may display information on tasks constituting the change process and their influence events. The display area 1113 may be composed of five fields: 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 configured and displayed as one entry for each task constituting the change process.

  In the task name 1121, 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. 10, the identification information of the task may be displayed in a form known to the administrator. The execution content 1122 displays the information acquired from the change process DB 500 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 be done. The status 1123 may display task status information 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. When 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 or , May be highlighted. The performance status 1125 may display the status of the performance information indicated by the influential event based on the information of the status 707 of the entry in the influential event management table 700 acquired in step S1003 of FIG. The performance status 1125 may display that effect only when the value of the status 707 of the entry in the influenced event management table 700 is "abnormal".

  The administrator determines that the problem occurred is due to the impact of the change process if the performance status 1125 displays "abnormal" and the impact event displayed in the impact event 1124 belongs to the "ongoing" group. Control processes such as interrupting the change process. 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 process of the change process should be continued.

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

  In the present embodiment, the change process influence management program 225 is executed in response to an input of a display instruction by a manager or the like, but processing is periodically started and information acquired or derived in the memory is recorded. 11 may be displayed on the output device 217 based on the information recorded in the memory when the input of the display instruction by the administrator or the like is received.

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

As described above, according to the first embodiment, execution is performed based on the influence rule in which the influence event of the computer system exerted by the task configuring the change process is defined for each task type and the progress status of the change process Impact events of the change process during can be identified according to the progress of the change process. Thus, when a problem occurs in the managed computer system, the administrator can determine whether the problem that has occurred is due to the influence of the change process being executed or not. Only the decision to interrupt the change process, review, etc. can be implemented. That is, even if a problem occurs in the managed computer system, if it is not the influence of the change process, it is possible to prevent the administrator from making a wrong decision such as interrupting the change process that does not need to be interrupted.
Second Embodiment

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

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

  However, whether or not the change process should be interrupted depends not only on whether the problem is due to the influence of the change process, but also on the contents of the tasks constituting the change process and the progress of the tasks. For example, some tasks may be interrupted depending on the task type. In addition, if the progress rate of the change process or task is equal to or more than a certain value, the change process may have a short impact on the computer system, so the decision to continue the execution of the change process or task may be appropriate. These decisions require knowledge of the type of task (eg, VM live migration). Therefore, a manager who does not have detailed knowledge about a task may misjudge the necessity of the control process of the change process with the method exemplified in the first embodiment or the time for the judgment. It may take a while. The control process of the change process is, for example, interrupting process of the change process. Further, in the method shown in the first embodiment, the determination of the necessity of the control process of the change process requires the judgment of the administrator without fail. Therefore, the control process of the change process is automatically determined by software and executed. Can not do it.

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

  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 are the same as those in the first embodiment. The configuration of each table is the same as in the first embodiment.

In the second embodiment, the control rule template table 1300 of FIG. 2 is added as new data, and the change process status table 800 is changed, in order to explain the process of determining the control process of the change process. Also, a control rule generation program 224 and a change process control program 227 are added as new programs, and a process to be 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 of Second Embodiment>

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

  The configuration of the change process status table 800 in the second embodiment is substantially the same as the configuration of the change process status table 800 in the first embodiment. The change process status table 800 has five fields, that is, an ID 801, a change process ID 802, a change process status 803, a task ID 804, and a task status 805, to store information on the change process or task execution status. On the other hand, the change process status table 800 in the second embodiment stores information on the progress rate of the task being executed, in order to determine whether or not the control process of the change process is necessary based on the progress rate of the task. 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 “Proc 1”, the task identified by “Task 2” is “in progress”, and the progress rate of the task is It shows that it is "80%".
<Control rule template table>

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

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

  FIG. 13 is a view for explaining an example of the data structure of the control rule template table 1300. As shown in FIG.

  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 unit 1331 includes five fields of a table 1303, a field 1304, an ID acquisition query 1305, an operator 1306, and a value 1307. The condition unit 1331 defines information on conditions for executing control processing on a change process or task. The conclusion unit 1332 has two fields of a control target 1308 and a control process 1309. In the conclusion unit 1332, information on control processing executed when all the conditions defined in the condition unit 1331 are satisfied is defined.

  The rule template ID 1301 stores information for uniquely identifying a control rule template. The task type 1302 stores information identifying the type of task to which the control rule template is applied. The value stored in the task type 1302 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 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 which the information used for the condition determination of the control rule is stored in the table designated by the table 1303. 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 this embodiment, as an example of the information stored in the ID acquisition query 1305, a SQL statement for acquiring the ID of the entry in which the information to be the condition is stored is listed from the influence event management table 700 and the change process status table 800. . “@TaskId” of 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, an SQL statement is taken as an example of means for acquiring information used for condition determination of a control rule, but other acquisition means may be used. The acquisition destination is not the information recorded in the storage area of the management computer, but may be the management target computer system 101, the hypervisor 235 that manages the execution of VM live migration, or orchestration software that manages the change process.

  The operator 1306 stores an operator used to determine the condition of the control rule. The values stored in the operator 1306 may be, for example, comparison operators “>”, “=”, “≦”, “≠”, and the like. A value 1307 stores a value for determining whether the information specified by the table 1303, the field 1304, and the ID acquisition query 1305 satisfies the condition. The control target 1308 stores information for identifying the type of a target to be subjected to control processing when the condition unit 1331 satisfies the conditions. In the present embodiment, the type “change process” is stored, but may be another value such as “task”. The control processing 1309 stores information for identifying the control processing to be executed when the condition unit 1331 satisfies the conditions. In the present embodiment, information for identifying a control process of “suspend” is stored, but as the other control processes, “continue”, “standby”, “rollback”, “correction”, “shrink”, etc. It may be. Moreover, those combinations may be sufficient. “Correction” is, for example, the process of interrupting the change process and changing and executing the contents of the remaining tasks so that the change process achieves the purpose and does not affect the detected problem. May be there. The “reduction” may be, for example, processing of reducing the number of parallel executions when a plurality of tasks are being 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 to 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 the identifier “CntlRuleTemplate1”. In this control rule template, when the application target task is “VM_LiveMigration” and all the conditions of the condition unit 1331 are satisfied, the “change process” to which the application target task belongs is called “suspended”. Indicates that control processing is to be performed. The control rule generated by the control rule template indicated by the entry 1311 has three conditions. The entry 1321 indicating one of the three conditions is "Impact_management", the field is "status", the entry is determined by the task ID, and its value is the table in which the information used for the condition determination is stored. Indicates that it is determined that the condition is satisfied if "abnormal" and "equal".
<Control rule>

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

  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 control processing execution conditions and control contents in order to determine whether or not to execute a specific control process for the change process when a problem occurs in the managed computer system 101. . While control rule templates are defined in a format independent of task execution targets (that is, parameters) for each type of task, control rule information is defined for each task based on the information of the change process DB 500, It includes the status of specific impact events determined based on the target of task execution and the progress of specific tasks as conditions.

  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. It is a figure to do.

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

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

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

  The control rule ID 1401 stores information for uniquely identifying control rule information. The change process ID 1402 stores information identifying the change process to which the control rule is applied. The value stored in the change process ID 1402 may be, for example, a value equal to the value stored in the change process ID 501 of the change process list table 591 of FIG. 5A. The task ID 1403 stores information for uniquely identifying a 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 values stored in the table 1404 may be, for example, values equal to the table 1403 of the control rule template table 1300 of FIG. The field 1405 stores the field name of the field in which the information used for the condition determination of the control rule is stored in the table designated in the table 1403. The value stored in the field 1405 may be, for example, a value equal to the table 1404 of the control rule template table 1300 of FIG. The ID 1406 stores, in the table designated by the table 1403, the ID of the entry in which the information used for the condition determination of the control rule is stored. The operator 1407 stores an operator used to determine the condition of the control rule. The value stored in the operator 1407 may be, for example, a value equal to the operator 1306 in the control rule template table 1300 of FIG. The value 1408 stores a value for determining whether the information specified by the table 1404, the field 1405, and the ID 1406 satisfies the condition. The value stored in the value 1408 may be, for example, a value equal to the value 1307 of the control rule template table 1300 of FIG.

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

  For example, the entry 1411 in FIG. 14 indicates the control rule identified by the identifier “CntlRule1-1”. This control rule is applied to the control process "stop" for the change process "Proc 1" when the application target is the task "Task 1" of the change process "Proc 1" and all the conditions of the condition unit 1431 are satisfied. The process is to be performed. Also, 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 entry ID is "Impact 1", and the condition is "equal" to "abnormal". Indicates that it is determined that

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

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

  When a problem occurs in the management target computer system 101, the control rule generation program 224 determines information on the control rule template table 1300 and the change process DB 500 to determine whether 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 according to the first embodiment.

  The control rule generation program 224 may start this process when the information on the new change process is registered in the change process DB 500. Further, this process may be started also at the timing when the information on the influence event is updated in the influence event management table 700. Also, this process may be started when the change process is started. In addition, when the problem of the management target computer system 101 is detected by the system information management program 221, this process may be started. This process may be started at an arbitrary timing from when the new change process information is registered in the change process DB 500 or the information of the influential event management table 700 is updated and 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 entry to be acquired may be all entries, or may be a newly registered entry, an updated entry, or an entry having a change process ID equal to the updated entry.

  When acquiring the updated entry or all the entries and proceeding with the subsequent processing, the control rule information 1400 related to the acquired change process DB entry is deleted in order to update the control rule information. You may

  In step S1502, the control rule generation program 224 repeats the processing of steps S1503 to S1507 on the entries of all 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 processing of steps S1505 to S1507 on all the control rule templates acquired in step S1503.

  In step S 1505, the control rule generation program 224 substitutes the value of the task ID 502 of the change process DB entry into all the variables stored in the ID acquisition query 1305 of the control rule template, and executes the process. Get the set of table IDs. Here, in the present embodiment, the task ID is substituted for the variable of the query, but when defining the control rule template for each type of change process, it may be a change process ID.

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

  In step S1507, the control rule generation program 224 generates control rule information 1400 based on the information of the change process DB entry, the IDs acquired in steps S1505 and S1506, and the control rule template. Specifically, identification information for uniquely identifying a control rule is stored in the control rule ID 1401 of the control rule information 1400, and values of the change process ID 501 and task ID 502 of the change process DB entry are stored in the change process ID 1402 and task ID 1403. Are stored, and the values of the control rule template table 1303, field 1304, operator 1306, value 1307 and control process 1309 are stored in the table 1404, field 1405, operator 1407, value 1408 and control process 1410, respectively. 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, the control rule template indicated by the entry 1311 of FIG. 13 is further acquired in step S1503. In step S 1505, the control rule generation program 224 substitutes the task ID “Task 1” of the entry 511 for the variable of the ID acquisition query 1305 and 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 “Task 1” is substituted for the query variable of the entry 1321 of the condition unit 1331 and executed, the ID “Impact 1” of the entry 711 of the influence event management table 700 of FIG. , Entry 715 "Impact 2" is obtained. When “Task 1” is substituted for the query variable 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 S 1506, “Proc 1” stored in the change process ID 501 of the entry 511 is acquired based on the identification information “change process” stored in the control target 1308 of the entry 1311, and in step S 1507, the acquired information is Based on the entry 1411 and the entry 1412 in FIG. 14, control rule information is generated.

In this embodiment, when at least one influence event of a task is detected, control rule information 1400 for executing control processing is generated. Therefore, as in the above-mentioned example, a plurality of IDs are obtained from one query in step S1505. If acquired, the condition unit 1431 may be generated based on the acquired combination of IDs, and control rule information may be generated as many as the number of acquired IDs. In the case of the above-described example, when “Task 1” is substituted for the query variable of the entry 1321, two IDs “Impact 1” and “Impact 2” are acquired. Furthermore, when the query of the entry 1322 and the entry 1323 is executed, the ID “ProcSt1” is obtained. As a result, two control rules 1411 and 1412 shown in FIG. 14 are generated. If it is desired to generate control rule information for executing control processing including influence events of all tasks, control rule information 1400 having all the IDs acquired in step S1505 in the condition unit 1431 may be generated. . Further, control rule information may be generated to execute control processing when X% satisfies the condition among the conditions generated by the entry 1321 on the condition of the detection of an influence event. Further, an identifier for switching the method of generating the 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 the performance information or configuration information of the managed component from the hypervisor 235 or the monitoring agent, etc., and the performance information table 300, the configuration information table 400, or the influence information. The information of the status 707 of the event management table is updated. In addition to this, in the second embodiment, the system information management program 221 executes the process of the change process control program 227 of the second embodiment when the status of the performance information changes to "abnormal".

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

  The system information management program 221 may periodically start the process, or the system information management program 221 may start the process 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 management target component from the hypervisor 235 or the like.

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

  In step S 1603, the system information management program 221 updates the value of the status 707 of the influenced event management table 700 in accordance with the value stored in the performance information table 300.

  In step S 1604, when the system information management program 221 updates the values in the performance information table 300 in step S 1602, the status from the previous update on the metric uniquely identified by the set of component ID 301 and metric type 302. It is determined whether there is at least one metric in which the value 305 changes 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 process of the change process control program 227 (the process will be described later) of the second embodiment.

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

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

  In the first embodiment, the change process influence management program 225 displays the change process influence events according to the progress status of the change process based on the influence 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 process to be executed for the change process based on the control rule information 1400.

  FIG. 17 is a flowchart of an example of the process 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. In addition, the change process control program 227 may start processing upon receiving an input of a display instruction from a manager or the like. A trigger for the administrator to input a display instruction may be that the system information management program 221 detects that a problem has occurred in the managed computer system 101 and notifies the administrator.

  In step S1701, the change process control program 227 acquires the value of the change process ID 802 from the change process status table 800. In 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 “in execution” or “non-execution”.

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

  In step S1703, the change process control program 227 acquires all control rule information in which a value equal to the change process ID is stored in the change process ID 1402 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 processes of steps S1705 to S1708 on all the control rule information acquired in step S1703.

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

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

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

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

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

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

  For example, in step S1701, the change process ID "Proc1" stored in the entry 1212 of FIG. 12 is acquired from the table of the change process status table 800, and in step S1703 the entries 1411 and 1412 out of the control rule information 1400 of FIG. , 1413 and 1414 are acquired. In the iterative process of step S1704, "normal" stored in the status 707 of the entry 713 of FIG. 7 and the task status 805 of the entry 1212 of FIG. “Running” and “80%” stored in the progress rate 806 are acquired. In step S1706, for example, when attention is paid to the condition indicated by the entry 1441, the value acquired in step S1705 is "normal", whereas the operator 1407 of the entry 1441 is "=", and the value 1408 is " 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 repetitive processing of step S1704 is subsequently executed. Temporarily, if it is determined to be true in step S1707, a combination of the information “Proc 1” identifying the change process stored in the control target 1409 of the entry 1413 and the information “discontinue” identifying the control process to be executed. Are stored in the memory. Then, in step S1709, the display program 226 is activated and information is displayed on the output device 217.

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

  In the second embodiment, an example of a screen displayed by the display program 226 in step S1709 is shown in FIG. The change process management screen 1100 is an example of a screen for displaying a recommended control process 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. A change process name 1111, a change process status 1112, and a task and influence event display area 1113 are provided to display influence events in accordance with the progress status of the change process. On the other hand, the change process management screen 1110 in the second embodiment may further include a recommended control process display area 1814 to display the control process to be executed for the change process. The control processing recommended to be executed may be displayed in the display area 1814 based on the information of the control target 1409 and the control processing 1410 stored in the memory in step S1708 of FIG. Also, a program for executing the control process defined in 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 and managed. When the user selects the button, the program may be executed by inputting parameters for executing the recommended control process into the program. In the change process management screen 1100 of FIG. 18, the value of the status 707 of the entry 713 of the influenced event management table 700 of FIG. 7 is “abnormal”, and the value of the status 707 of the entries 711, 712, and 714 is “normal”. Show an example of display when

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

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

  The change process impact management program 225 and the change process control program 227 may be sequentially executed or parallelly executed, 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.

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

  Moreover, in the present embodiment, it is aimed to interrupt the change process when the problem occurred in the managed computer system is caused by the influence of the change process, and the influence event of the task under execution of the change process and the problem generated We have described an example of interrupting the change process if is equal. However, even if the problem that occurred is not due to the effect of the task being executed, if the impact event of the unexecuted task and the problem that occurred are equal, the problem that occurred by executing the unexecuted task gets worse It may be appropriate to interrupt the change process or to cancel the start of the execution so that it does not happen. Therefore, as exemplified in entry 1312 of FIG. 13, a control rule template is defined that interrupts the change process when an influence event of an unexecuted task becomes abnormal in order not to aggravate the problem that has occurred. May be

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

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

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

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

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

  For example, live migration of a virtual machine, which is one of the task types described in the first embodiment and the second embodiment, moves the physical server while the virtual machine continues its operation. Therefore, during migration processing, the CPU load for migration processing is generated not only on the physical servers of the migration source and migration destination but also after migration processing is completed, the virtual machine migrated on the migration destination physical server CPU load is continuously generated by running.

  As described above, if the influence of the task continues to exist even after the completion of the task execution, it may be desirable to interrupt the execution of the change process regardless of the task progress rate. In addition, when the influence of the task continues to exist, even when a problem occurs after the completion of execution of the task or the change process, it may be desirable to execute control processing such as rollback on the change process.

  On the other hand, there are influence events that occur only while the task is being executed. For example, as described above, during live migration of a virtual machine, CPU load due to live migration processing occurs on the migration source physical server, but load due to live migration does not occur after execution completion. As described above, with regard to the temporary influence during task execution, it is not necessary to execute control processing such as rollback even when a problem occurs after completion of task execution.

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

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

  The performance information table 300, the configuration information table 400, and the change process DB 500 used in the description of the third embodiment may be the same as those in the first embodiment. Further, as for 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, the values stored in the control rule template table 1300 and the control rule information 1400 are changed for the sake of explanation.

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 which has completed execution continuously affects a specific managed component. In addition, the processing executed by the change process impact management program 225 is also changed.
<Influence Rule Table of Third Embodiment>

  FIG. 19 is a view for explaining an example of the data structure of the influence rule table 600 in the third embodiment.

  The configuration of the influence rule table 600 in the third embodiment is substantially the same as the configuration of the influence rule table 600 in the first embodiment. The influence rule table 600 has four fields, that is, a rule ID 601, a task type 602, an influence component information acquisition query 603, and an influence metric type 604, in order to store information of the influence rule. In addition to these, the influence rule table 600 in the third embodiment determines the influence period of the influence event of the task derived by the influence rule in order to determine whether the influence event continuously influences even after completion of task execution. And an influence period 605 which is a field for storing information of In the present embodiment, the influence period is “In (effects only during task execution)”, “After (effects after completion of task execution)”, “In & After (effects during task execution and after completion) In the three patterns “1”, 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, entry 1911 in FIG. 19 indicates the following. That is, in the influence rule identified by the identifier "ImpactRule1", the task type to which the influence rule is applied is "VM_LiveMigration", and the managed component affected by the task is a VM live migration parameter based on the parameter ID of the task. The metric type that is acquired from the move destination physical server ID 523 in Table 592 and that the task affects is “PS / CPU / utilization”, and the influence period of the influence event of the task derived by the influence rule is “running” of the task And indicates that it is "after completion of execution."
<Influence event management table of the third embodiment>

  FIG. 20 is a view for explaining an example of the data structure of the influential event management table 700 in the third embodiment.

  The configuration of the influential event management table 700 in the third embodiment may be substantially the same as the configuration of the influential event management table 700 in the first embodiment. The influential event management table 700 has seven fields, i.e., ID 701, change process ID 702, task ID 703, task type 704, influential component ID 705, influential metric type 706, and status 707, to store information on influential events for each task. have. In addition to these, the influential event management table 700 in the third embodiment stores information on the influence period of the influential event of the task in order to determine whether the influential event continuously influences even after completion of the task execution. It may have an influence period 708 which is a field. In the present embodiment, the influence period is “In (effect only during task execution)”, “After (effect after completion of task execution)” and “In & After (effect during task execution and after completion of execution)”. In the three patterns “1”, 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, entry 2011 in FIG. 20 indicates the following. That is, the influence event identified by the identifier “Impact1” is that the change process is “Proc1”, the task is “Task1”, and the task type is “VM_LiveMigration”. Furthermore, the event that the task “Task1” affects is “VM / CPU / contention” (here, VM CPU contention rate of the virtual machine (here, virtual machine 234 c in FIG. 2) identified by “vm3”. Is the performance value identified in), and the current performance value is "normal". Then, it indicates that the influence period of the influence event of the task is “during execution and after completion of execution” of the task.

  Note that the values stored in the influential event management table 700 shown in FIG. 20 are based on the change process DB 500 of FIG. 5AB, the performance information table 300, and the influence rule table 600 of FIG. It is generated by executing the process 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 S 907 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.

Note that for the description of the third embodiment, the values stored in the status 707 of the influenced event management table 700 of FIG. 20 are the same as those of the performance information table 300 of FIG. 3 of the first embodiment or FIG. It differs from the values stored in the management table 700.
<Control Rule Template Table of Third Embodiment>

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

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

  In the control rule template in 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 process for the change process, including whether or not the influence event continuously affects even after completion of task execution.

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

  In addition, a task or change process that has completed execution continuously affects a specific managed component, thereby performing rollback control processing for the change process if a problem occurs. 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 rules are generated by the process of the control rule generation program 224 shown in FIG. 15 of the second embodiment. Information 1400 is generated.
Control Rule of Third Embodiment

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

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

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

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

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

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

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

  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 impact management program 225 repeats the processes in steps S2203 to S2211 for all the change process status table entries acquired in step S1201.

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

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

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

  In step S 2206, 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 “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 impact management program 225 determines whether the value of the impact period acquired in step S2204 is “In” or “In & After”. If the result of this determination is true (S2207: YES), the process proceeds to step S2210. If the result of this determination is false (S2207: NO), the process continues to repeat the process of step S2202.

  In step S2208, the change process 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 “completed”. If the result of this determination is true (S2208: YES), the process proceeds to step S2209. If the result of this determination is false (S2208: NO), the process continues to repeat the process of step S2202.

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

  In step S2210, the change process impact management program 225 records the entry of the impact event management table 700 in the memory as the "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 impact management program 225 activates the display program 226. The display program 226 determines the change processes, tasks, and their effects at the start of the change process impact management program 225 based on the acquired change process status table 800 entries and the information stored in the memory in steps S2210 and S2211. Is displayed on the output device 217.

  In step S2201, when the change process impact management program 225 acquires an entry from the change process status table 800, the change process influence management program 225 may select an entry to be acquired based on a designated 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 is also an entry whose change process status is "in execution" or "not executed". Alternatively, it may be limited to entries whose change process status is “completed” and whose completion time is within a certain 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 impact 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, in step S2203, the change process influence management program 225 acquires the entry 2013, the entry 2014, and the entry 2017 of FIG. Next, when executing processing in the entry 2013 in the repetitive processing 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 process proceeds to step S2210 by the determination processing of steps S2206 and S2207. Then, in step S 2210, 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.

  In the third embodiment, FIG. 24 shows an example of a screen displayed by the display program 226 in step S2212 in FIG. 22 and step S1709 in FIG. The change process management screen 1100 is based on information obtained or stored in the change process influence management program 225 of FIG. 22 and the information acquired or stored in the change process control program 227 of FIG. Control processing 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 events 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 in order to display the control process to be executed for the change process.

  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 a screen having only the recommended control processing display area 1814 may be displayed.

  In the influence event 1124 of the third embodiment, the influence event for each task may be displayed based on the information of the entry of the influence event management table 700 acquired in step S2203 of FIG. Also, in step S 2210 or in step S 2211, when stored in the memory as the “ongoing” group or the “completed / ongoing” group, as shown in the display area 1144 of FIG. Alternatively, the "completed / ongoing" identifier may be displayed or highlighted.

  The administrator changes the problem that occurred when the performance status 1125 is displayed as "abnormal" and the impact event displayed in the impact event 1124 belongs to the "ongoing" or "completed / ongoing" group. Control process such as interrupting or rolling back the change process.

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

  In the present embodiment, as shown in FIG. 24, 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". The change process displayed in the change process name 1111 may be displayed as a cause candidate of the problem that has occurred.

  As described above, according to the third embodiment, it is defined whether or not the influence by the task continues after completion of the task execution for the influence rule, and the influence event of the change process is based on the definition. Can be determined, or it can be determined whether a particular control process for the change process should be performed. In this way, it is necessary to execute the control process of the change process in consideration of whether the tasks that constitute the change process affect a specific managed component only during execution or continuously after completion of execution. You can judge no.

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

  For example, the task may be volume migration in which logical volumes (logical storage devices) of the storage device move between redundant arrays of independent disks (RAID) 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 part of a physical area of the RAID group, which is an LU (logically accessible as one storage resource from a computer) Logical Unit). The impact event caused by the volume migration is, for example, an increase in the operation rate of the migration destination RAID group and a decrease in response time of the logical volume on the migration destination RAID group. In addition, when the copy function such as taking snapshots regularly is applied to the logical volume on the storage device that performs volume migration, the copy speed of the logical volume to which the copy function is applied is reduced. An influence 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. Volume response time reduction is a continual impact event. On the other hand, the reduction in the copy speed of the logical volume is an influence event that occurs only during the volume migration. The above-described volume migration is one of the tasks, and the above-mentioned influence events are displayed in the change process or the recommendation for the change process using the method shown in the first to third embodiments. A display of control processing may be implemented.

  Also, the task may be server scale-out processing in which servers running the same application are added and load-balanced in order to improve the performance of services provided by the computer system.

  The task may be setting change processing of an application operating on the server or update processing of an application program.

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

  Also, the task may be control processing 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 influence event of a specific task occurs, all the same regardless of the contents of the influence event Although control processing was performed, a control rule template may be defined for each set of task type and influence metric type. For example, by defining the query stored in the ID acquisition query 1305 of the entry 1321 of FIG. 13 as follows, the CPU utilization of the migration destination physical server (PS / CPU / utilization) is executed when performing live migration of a virtual machine. Control processing can be divided and defined when an "abnormality" occurs and when another abnormality occurs.
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, whether or not the control processing needs to be executed is determined depending on whether or not the influence event caused by the task is in the “abnormal” state. The condition unit 1331 may define a condition in consideration of “the magnitude of the influence of the task”.

  For example, in the example of live migration of virtual machines mentioned in the second embodiment, the virtual machine (vm1) moves from the physical server (PS1) to the physical server (PS2). This live migration has the effect of increasing the CPU utilization (PS / CPU / utilization) of the physical server (PS2). However, the CPU utilization of the physical server (PS2) also increases due to the load of the virtual machine (vm3) operating on the physical server (PS2). At this time, when the CPU utilization and memory usage of the virtual machine (vm1) to be moved are small, while the CPU utilization of the virtual machine (vm3) is large, the contribution to the CPU utilization increase of the physical server (PS2) is It can be determined that the load of the virtual machine (vm3) is larger than that of live migration. Therefore, in this case, there is a high possibility that the CPU utilization rate abnormality of the physical server (PS2) can not be resolved even if the movement of the virtual machine (vm1) is interrupted, so it may be judged that the change process is not interrupted. is there.

  Such a determination may be incorporated into the condition part 1331 of the control rule template. For example, if the CPU utilization (VM / CPU / utilization) of the mobile 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 and. In addition, the CPU utilization rate increase rate of the mobile virtual machine may be calculated, and a condition to be determined as true may be added if the rate is equal to or more than a predetermined value.

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

  Also, the condition part 1331 of the control rule template in FIG. 13 compares the following conditions, that is, the increase rate of the CPU utilization of the mobile virtual machine with the increase rate of the CPU utilization of the virtual machine on the destination physical server: A condition that is determined to be true when the rate of increase in the CPU utilization of the mobile virtual machine is high may be added.

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

  FIG. 26 shows a modified example of the condition part 1331 of the control rule template table 1300. The condition part 1331 of the modified example shown in FIG. 26 may be a control rule template indicated by the entry 1311 of FIG. 13 of the second embodiment or the entries 2111, 2112 of FIG. 21A.

  FIG. 26 shows an example of the condition of the control rule template for comparing the increase rate of the CPU utilization of the mobile virtual machine with the increase rate of the CPU utilization of the virtual machine existing on the destination physical server earlier. . In the value 1307 of the control rule template table 1300 shown in the figure, a query is stored so that a value can be obtained from the table, not a fixed value. When the control rule information 1400 is generated from the control rule template table 1300, it is acquired in step S1501 of the control rule generation program 224 in the variable “@TaskId” of the query stored in the value 1307 as the value 1408 of the control rule information 1400. A query in which the task ID of the entered entry is substituted is stored. Then, when the control rule information 1400 is applied, a query of a value 1408 is executed, a specific value is specified, and condition determination is made 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, and determination of true or false is performed . Then, when at least one of the values specified in the query of the value 1408 is determined to be true, or when it is determined that a value of a certain percentage or more is true, the condition shown in FIG. 26 may be set to be true.

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

101 Managed 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 a computer system to be managed,
The management computer has a central processing unit and a storage unit.
The storage device is
Configuration information related to the configuration of components constituting the computer system to be managed;
Change process information related to a change process for changing the configuration of components of the computer system to be managed, the change process information including tasks and parameters constituting the change process;
Impact rules for identifying impact events that occur due to task execution for each task type,
Storing the execution status of the tasks that constitute the change process,
The central processing unit
A process of specifying an influence event according to task when the change process is executed based on a task type of a task constituting the change process information and the influence rule;
A management computer that executes a process of identifying a task being executed based on the execution status of the task, and identifying an influence event of the task being executed. The central processing unit
The management computer according to claim 1, further performing processing of outputting an influence event of the identified task under execution. The influential event is an influential component and an influential metric,
The storage device is
Further stores information indicating the state of the component including multiple metrics observations,
The central processing unit
The management computer according to claim 2, wherein the processing of outputting the state of the component related to the influential event of the in-progress task is performed according to the observed value of the metrics of the influential event of the in-progress task. The influential event is an influential component and an influential metric,
The storage device is
Information indicating the state of the component that contains multiple metrics observations,
Further storing a control process for a change process defined for each task type, and a control rule template including a determination criterion of the executability of the control process based on an influence event for each task type;
The central processing unit
A process of generating a control rule including a control process for the change process and a determination criterion of executability of the control process based on a task type of a task constituting the change process and the control rule template;
A process of determining whether or not to execute control processing for a change process defined in the control rule based on observed values of metrics related to an influence event of the task being executed and the generated control rule;
The management computer according to claim 1, further performing a process of displaying a determination result of necessity of execution of the control process.   The management computer according to claim 4, wherein the control rule template determination criteria include an execution status of a change process or task.   The management computer according to claim 5, wherein the control rule template determination criteria include the progress of tasks constituting the change process. The central processing unit
The management computer according to claim 4, further performing a process of executing a control process defined in the control rule, when the determination result of the execution necessity of the control process is necessary.   The management computer according to claim 4, wherein the control rule template is defined for each type of the change process.   The management computer according to claim 4, wherein the control rule template is defined for each set of task type and influence metric type.   The criterion of the control rule template is a comparison between the rate of increase of the observed value of a particular metric of the component that is modified by the task execution and the rate of observed value of the particular metric of the component that is affected by the task execution. The management computer according to claim 4, comprising The influence rule includes a period during which the influence event occurs for each task type,
The central processing unit
A process of specifying an influence event according to task when the change process is executed and a period in which the influence event occurs, based on a task type of a task constituting the change process information and the influence rule;
The management computer according to claim 2, further performing a process of outputting the influential event according to the change process and the execution status of a task that configures the change process. The influence rule includes a period during which the influence event occurs for each task type,
The control rule includes a period in the determination criterion of the executability, and
The central processing unit
Execution of control processing on a change process defined in the control rule based on observed values of metrics related to an influence event of the task in execution, the control rule, and an execution status of tasks constituting the change process The management computer according to claim 4, wherein the management computer determines the necessity. The central processing unit
The management computer according to claim 3, wherein when the status of the component affected by the task is "abnormal", the change process relating 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, comprising:
The management computer has a central processing unit and a storage unit.
The storage device is
Configuration information related to the configuration of components constituting the computer system to be managed;
Information on a change process for changing the configuration of the components of the computer system to be managed, the change process information including tasks and parameters constituting the change process;
Impact rules for identifying impact events that occur due to task execution for each task type,
Storing the execution status of the tasks that constitute the change process,
The central processing unit
A process of specifying an influence event according to task when the change process is executed based on a task type of a task constituting the change process information and the influence rule;
A management method comprising: identifying a task being executed based on the execution status of the task; and identifying an influence event of the task being executed. A computer program for a management computer that manages a computer system to be managed,
The management computer has a central processing unit and a storage unit.
The storage device is
Configuration information related to the configuration of components constituting the computer system to be managed;
Information on a change process for changing the configuration of the components of the computer system to be managed, the change process information including tasks and parameters constituting the change process;
Impact rules for identifying impact events that occur due to task execution for each task type,
Storing the execution status of the tasks that constitute the change process,
When the computer program is executed by the central processing unit
A process of specifying an influence event according to task when the change process is executed based on a task type of a task constituting the change process information and the influence rule;
A computer program for identifying a task being executed based on the execution status of the task, and identifying an influence event of the task being executed.

Images