JP2018049546A - Vm environment command execution management program, vm environment command execution management method, vm environment command execution device, and vm environment command execution management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To achieve a trouble prevention, product quality stabilization, improvement in work efficiency and the like in a VM environment.SOLUTION: A program running in an environment where one or more virtual machines work is configured to: receive a command to be input from a terminal of an operator in charge; refer to a storage unit associating the command with an execution procedure of the command and an execution condition thereof; acquire the execution procedure and the execution condition corresponding to the received command; determine whether the execution condition is sequentially satisfied according to the execution procedure; when the execution procedure and the execution condition require authorization or check of a prescribed third party, notify the third party of a request for the authorization or check to receive the authorization or check; and make a computer execute processing of executing the command when all of the execution procedure and execution condition is satisfied.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a VM environment command execution management program, a VM environment command execution management method, a VM environment command execution management apparatus, and a VM environment command execution management system.

  In an information processing facility such as a data center, a plurality of VMs (Virtual Machines) are operated from the viewpoint of improving the use efficiency of real machines (physical servers) and maintaining data security. Service is often provided.

  In such a data center, if the scale is large, multiple management companies and departments in different specialized fields are involved in the operation of multiple servers, including VMs, and lack of horizontal coordination without knowing each other's existence. It independently manages information about the equipment and equipment in charge. The general administrator can check the status of the actual machine and the load of each VM on the monitoring device, but it is restricted by the operation policy that the person in charge of each VM directly refers to the information. Yes.

  Therefore, when the person in charge of each VM moves or copies a file on the VM for maintenance, there are cases where it takes extremely long time due to contention of processing resources of another VM running on the same actual machine. It was. In other words, in the transfer between VMs on the same real machine, the disk and the data transfer path are the same, so they cannot be used at the same time, and it takes time to wait until they can be used. It was. In some cases, the use of disks in a plurality of VMs on the same real machine overlaps, resulting in insufficient disk capacity on the real machine and the inability to continue processing.

  In addition, even if it is necessary to check other VM related parties by telephone when executing maintenance commands, the confirmation procedure may be overlooked, omitted, or attempted to be confirmed. Confirmation may not be possible due to a change or the like, which may affect other VMs.

  As described above, it is difficult for a skilled operation person to perform a series of operations in an increasingly sophisticated and complicated VM environment quickly and without errors, and stable information processing facilities such as a data center can be stably provided. It was difficult to operate.

  On the other hand, information related to each component of a large-scale information system and linkage information between each component are centrally managed to quickly grasp which business service will be disrupted when a specific facility fails. Have been disclosed (see, for example, Patent Document 1). However, this technology focuses on the response when a failure occurs, and does not prevent the failure.

Japanese Patent Laid-Open No. 2015-200936

  As described above, the burden on the operator in the VM environment is heavy, and trouble prevention, quality stabilization, work efficiency improvement, and the like have been desired.

  The present invention has been proposed in view of the above-described conventional problems, and an object thereof is to prevent troubles in a VM environment, stabilize quality, improve work efficiency, and the like.

  In order to solve the above-described problems, the present invention is a program that operates in an environment in which one or more virtual machines operate, accepts a command input from a terminal of an operator, Referring to the storage unit in which the execution procedure and the execution condition are associated with each other, the execution procedure and the execution condition corresponding to the received command are acquired, and it is determined whether the execution condition is sequentially satisfied according to the execution procedure. If the execution condition requires the approval or confirmation of a specified third party, the request for approval or confirmation is notified to the third party and the approval or confirmation is accepted, and all execution procedures and conditions are satisfied. The computer executes the process that executes the command if

  In the present invention, trouble prevention, quality stabilization, work efficiency improvement, and the like in the VM environment can be achieved.

It is a figure which shows the structural example of the system concerning one Embodiment. It is a figure which shows the function structural example of a command wrapper. It is a figure which shows the hardware structural example of a physical server. It is a sequence diagram (the 1) which shows the process example of embodiment. It is a figure (the 1) which shows the example of wrapper information DB. It is FIG. (1) which shows an example of a screen. It is FIG. (2) which shows an example of a screen. It is a sequence diagram (the 2) which shows the process example of embodiment. It is a figure (the 2) which shows the example of wrapper information DB. It is a figure which shows the example of the virtual machine on a virtualization infrastructure. It is a sequence diagram (the 3) which shows the process example of embodiment. FIG. 6 is a diagram (part 3) illustrating an example of a wrapper information DB; It is a sequence diagram (the 4) which shows the process example of embodiment. It is FIG. (4) which shows the example of wrapper information DB. It is a figure which shows the example of the virtual machine on a virtualization infrastructure.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram illustrating a configuration example of a system according to an embodiment. In FIG. 1, physical servers (real machines) 1A, 1B,... Are connected to a maintenance network 3, a monitoring device 4 is connected to the maintenance network 3, and a monitoring information DB (Database) 5 is connected to the monitoring device 4. Has been. The monitoring information DB 5 stores system configuration information and the like necessary for monitoring by the monitoring device 4 and various information collected as a result of monitoring.

  Each of the physical servers 1A, 1B,... Is operating with one or more virtual machines. In the illustrated example, the virtual machines 11A1, 11A2,... Operate on the physical server 1A, and on the physical server 1B. Virtual machines 11B1, 11B2,... Are operating. In addition, on one or a plurality of virtual machines, a command wrapper 2 for processing a command input from an operator is running. In the illustrated example, the command wrapper 2 is operating on the virtual machine 11A2 of the physical server 1A. However, the command wrapper 2 may be operated on another virtual machine.

  The virtual machines on the physical servers 1A, 1B, ... are connected to the business networks 8A, 8B, ... via virtual switches 12A, 12B, .... In addition to the wrapper information DB 7 used by the command wrapper 2, various databases such as the maintenance procedure manual DB 6 are connected to the business networks 8A, 8B,. The wrapper information DB 7 stores command execution condition / execution procedure information 71 and collection information 72. The command execution condition / execution procedure information 71 is information indicating a condition for executing for each command and a procedure of work to be performed before the execution. The collected information 72 is information necessary for the determination about conditions that can be automatically determined and information used for presenting to the person in charge of operation. In addition, client terminals 9A1, 9A2,..., 9B1, 9B2,... Operated by an operator or the like are connected to the business networks 8A, 8B,. Of the client terminals 9A1, 9A2,..., 9B1, 9B2,... That only perform approval / confirmation described later may not be connected to the business networks 8A, 8B,. For example, in the case where an approval / confirmation request is received by an automatic telephone and the result (OK, NG) is returned as a DTMF (Dual-Tone Multi-Frequency), it is not connected to the business networks 8A, 8B,. Also good.

  FIG. 2 is a diagram illustrating a functional configuration example of the command wrapper 2. In FIG. 2, the command wrapper 2 includes a wrapper agent unit 21, a wrapper manager unit 22, a notification agent unit 23, and a notification manager unit 24.

  The wrapper agent unit 21 includes a command reception function, a condition inquiry function, an execution control function, a log output function, an approval / confirmation request function, a notification function, a result registration function, and the like. The command reception function is executed by the client terminal 9 (9A1, 9A2,..., 9B1, 9B2,...) To the virtual machine 11 (11A1, 11A2,..., 11B1, 11B2,. This function accepts commands for maintenance of applications. When receiving a command, it is possible to request authentication using an authentication ID and a password. The condition inquiry function is a function for acquiring corresponding information from the command execution condition / execution procedure information 71 of the wrapper information DB 7 based on the received target system name and command.

  The execution control function is a function for controlling the execution of a command via a user interface with the person in charge of operation based on information acquired from the command execution condition / execution procedure information 71. The log output function is a function for outputting a log to the collection information 72 of the wrapper information DB 7 when executing a command. The approval / confirmation request function is a function for requesting approval / confirmation from a third party when the command execution condition includes approval or confirmation from the third party. The notification function is a function for notifying a third party of an approval / confirmation request or the like. In addition, in order to eliminate the need to worry about the presence (physical position) of the notification manager unit 24 for the approval / confirmation request function and the notification function of the wrapper agent unit 21, the notification manager unit via the wrapper manager unit 22 as a gateway. The request is made to 24. Multiple notification methods are possible, such as web notification, phone call, SMS, email response, etc. If there are multiple notification managers 24 including the use of other companies' services, set if managing them on the wrapper agent unit 21 side However, the intervention of the wrapper manager unit 22 makes management easier and saves the results. The result registration function is a function for registering a command execution result in the collection information 72 of the wrapper information DB 7.

  The wrapper manager unit 22 includes a condition registration function, an authentication function, a condition / state search function, a result answer function, a log storage function, an information reception function, an information collection function, and the like. The condition registration function is a function for registering a command execution condition and an execution procedure in the command execution condition / execution procedure information 71 of the wrapper information DB 7 in accordance with an operation from the client terminal 9 or the like. The authentication function is a function for authenticating a person who uses the wrapper information DB 7 with an authentication ID / password or the like. The condition / state search function is a function for searching the wrapper information DB 7 for an execution condition, an execution procedure, and the like registered corresponding to the command received by the wrapper agent unit 21. The result answering function is a function for answering a request result to a search result. The log accumulation function is a function for accumulating the log output from the wrapper agent unit 21 as a part of the collection information 72 of the wrapper information DB 7. The information receiving function is a function for receiving information from other parts. The information collection function is a function that collects information from the monitoring information DB 5, the maintenance procedure manual DB 6, and others and accumulates it as part of the collection information 72 of the wrapper information DB 7.

  The notification agent unit 23 is called from the notification manager unit 24 and has a function of notifying the target person, waiting for a response, and responding the result to the notification manager unit 24.

  The notification manager unit 24 has a function of being called from the wrapper manager unit 22, causing the notification agent unit 23 to wait for notification and response, and responding the result to the wrapper manager unit 22.

  FIG. 3 is a diagram illustrating a hardware configuration example of the physical server 1 (1A, 1B,...). Note that the monitoring device 4 and the client terminals 9 (9A1, 9A2,..., 9B1, 9B2,...), And the database server constituting the monitoring information DB5, the maintenance procedure manual DB6, and the wrapper information DB7 are also hardware. The hardware configuration is the same.

  In FIG. 3, a physical server 1 includes a CPU (Central Processing Unit) 1002, a ROM (Read Only Memory) 1003, a RAM (Random Access Memory) 1004, and an NVRAM (Non-Volatile Random Access Memory) 1005 connected to a system bus 1001. It has. The physical server 1 includes an I / F (Interface) 1006, an I / O (Input / Output Device) 1007, an HDD (Hard Disk Drive) / SSD (Solid State Drive) 1008, which are connected to the I / F 1006. A network interface card (NIC) 1009. The physical server 1 also includes a monitor 1010, a keyboard 1011, a mouse 1012, and the like connected to the I / O 1007. A CD / DVD (Compact Disk / Digital Versatile Disk) drive or the like can be connected to the I / O 1007.

  The function of the physical server 1 is realized by executing a predetermined program in the CPU 1002. The program may be acquired via a recording medium, may be acquired via a network, or may be embedded in a ROM.

<Operation>
[Example of redundant system single system maintenance]
FIG. 4 is a sequence diagram showing a processing example of the above embodiment, and shows a processing example of redundant system single system maintenance. In FIG. 4, in accordance with an instruction from any client terminal 9 (step S101) or automatically, the command wrapper 2 requests maintenance procedure manual information from the maintenance procedure manual DB 6 (step S102), and the maintenance procedure manual DB 6 The maintenance procedure manual information is returned (step S103). Based on the acquired maintenance procedure manual information, the command wrapper 2 generates execution conditions and work procedures in a predetermined format according to the instructions when there is an operator's instruction and according to a predetermined rule when automatically performed. And registered in the wrapper information DB 7 (step S104). In addition, although the case where execution conditions and work procedures are generated and registered prior to the input of a command to be described later, execution conditions and work procedures may be generated and registered in response to the input of commands. Also, the execution conditions and work procedures can be registered directly in the wrapper information DB 7 from any of the client terminals 9 without using the maintenance procedure manual DB 6.

  FIG. 5 is a diagram showing an example of the wrapper information DB 7, which is an example of a command “shutdown” for a system having a specific system name. As the command execution condition / execution procedure information 71 in the illustrated example, an authentication ID with a timed password is required for authentication, a time condition is within a schedule, and prior approval is necessary as a procedural condition. If it is not, approval is required, and the technical condition is that one system is in normal operation, the balancer is set, and the standby state is set. In addition, from the viewpoint of double check, it is described that a check by a work checker who is a colleague of an operator is necessary, and then a command is executed and a result is notified. The collection information 72 includes a schedule automatically collected by the wrapper information DB 7, presence / absence of prior approval, presence / absence of normal operation of one system, balancer setting state, work log as a log unit, execution results, and shared information And are included.

  Returning to FIG. 4, the command wrapper 2 makes a request for monitoring information to the monitoring information DB 5 at a predetermined timing (including after command input described later) (step S105), and the monitoring information DB 5 responds with the monitoring information (step S105). S106). The command wrapper 2 registers the acquired monitoring information as part of the collected information 72 in the wrapper information DB 7 (step S107). The command wrapper 2 collects information from other information sources in the same manner. In addition to requesting information from the command wrapper 2, the information may be automatically transmitted to the command wrapper 2 at the timing when the information is updated from the information source.

  After that, when the maintenance person in charge designates the target system name and inputs the shutdown command to the command wrapper 2 from the client terminal 9A1, for example, the command wrapper 2 starts log output (step S108). Step S109). Further, the command wrapper 2 makes a search request to the wrapper information DB 7 based on the target system name and the command (step S110), and the wrapper information DB 7 responds with registration information when the corresponding information is registered (step S110). S111).

  When the command wrapper 2 acquires the registration information, the command wrapper 2 collects the execution condition from the command execution condition / execution procedure information 71 and the collection information 72 included in the registration information according to the execution procedure of the command execution condition / execution procedure information 71. It is determined whether or not the above is satisfied (step S112). Then, the command wrapper 2 generates user interface screen information and transmits it to the client terminal 9A1 (step S113). Fig. 6 shows an example of the screen. Shared information and past results as reference information are displayed at the top. Below that, it is shown that the maintenance time of the time condition is within the schedule by automatic collection. The prior approval of the procedural conditions of the company was not confirmed by automatic collection. Since prior approval is not satisfied and it is necessary to approve the person in charge, there is no subsequent indication.

  Returning to FIG. 4, if the pre-approval is not satisfied and it is necessary to approve the responsible person, the command wrapper 2 sends the system name and the command to be executed to the responsible client terminal 9A3. An approval request with the above information added is made (step S114). Information such as the address of the person in charge may be included in the execution condition, or may be acquired from the current system information as part of the collected information. When the responsible person performs an approval operation (such as clicking a button on the screen), an approval response is sent from the client terminal 9A3 (step S115).

  Next, the command wrapper 2 determines whether the subsequent execution condition is satisfied by the collection information or the like (step S116). Then, the command wrapper 2 generates screen information of the user interface and transmits it to the client terminal 9A1 (step S117). FIG. 7 shows an example of the screen at this time, and it is shown that the pre-approval is “OK” by the approval by the person in charge, and that the one-sided normal operation and balancer settings of the technical conditions are also satisfied. ing.

  Next, from the viewpoint of double check, the command wrapper 2 makes a confirmation request with information about the system name and the command to be executed to the client terminal 9A2 of another work confirmer who is a colleague of the operator. (Step S118). When the work confirmer performs a confirmation operation (such as clicking a button on the screen), a confirmation response is sent from the client terminal 9A2 (step S119).

  Next, the command wrapper 2 finally issues an execution confirmation request to the client terminal 9A1 of the operation person (step S120), and the operation person performs an operation confirmation operation (such as clicking a button on the screen). Then, an execution confirmation response is sent from the client terminal 9A1 (step S121). In response to this, the command wrapper 2 executes the command input from the person in charge of operation (step S122). The command is executed by inputting the command to a system to which the command should be given. Although not shown, the command wrapper 2 appropriately acquires collected information (monitoring information) from the wrapper information DB 7 even after execution of the command. For example, when the command execution causes other adverse effects. Has a function of inquiring from the wrapper manager unit 22 to the wrapper agent unit 21 whether to continue, interrupt, or cancel execution of the command. The approval and confirmation request can be performed in the same manner.

  Thereafter, the command wrapper 2 notifies the related client terminals 9A2 and 9A3 of the result of command execution (steps S123 and S124) and registers them in the wrapper information DB 7 (step S125). The client terminal 9A1 of the person in charge of the operation is notified of the result from the system that has input the command by executing the command.

[Virtual infrastructure (physical server) stop processing example]
FIG. 8 shows an example of a virtual infrastructure stop process. Further, it is assumed that command execution condition / execution procedure information 71 and collection information 72 as shown in FIG. 9 are registered in the wrapper information DB 7 for the virtualization infrastructure stop command. The collection information 72 is updated to the latest information as appropriate.

  In FIG. 8, when the maintenance operator in charge designates the target system name (virtual infrastructure name) from the client terminal 9A1 to the command wrapper 2, for example, the virtual infrastructure stop command is input (step S201). The command wrapper 2 starts log output (step S202). Further, the command wrapper 2 makes a search request to the wrapper information DB 7 based on the target system name and command (step S203), and the wrapper information DB 7 responds with registration information when the corresponding information is registered (step S203). S204).

  When the command wrapper 2 acquires the registration information, the command wrapper 2 collects the execution condition from the command execution condition / execution procedure information 71 and the collection information 72 included in the registration information according to the execution procedure of the command execution condition / execution procedure information 71. It is determined whether or not the above is satisfied (step S205). Then, the command wrapper 2 generates user interface screen information and transmits it to the client terminal 9A1 (step S206). Here, as shown in FIG. 10, there are four virtual machines # 1 to # 4 under the virtualization infrastructure to be stopped, and all of them are in the service state by the collection information 72 (FIG. 9). If there is a stop condition, the technical condition is not satisfied and a message to that effect is displayed on the screen.

  Returning to FIG. 8, when the technical condition is not satisfied and it is necessary to approve the administrator of each virtual machine, the command wrapper 2 displays the client terminal 9A4 of the administrator of the virtual machines # 1 to # 4. To 9A7, an approval request with information on the system name and the command to be executed is added (step S207). Information such as the administrator's address may be included in the execution condition, or may be acquired from the current system information as part of the collected information. When the administrator performs an approval operation (such as clicking a button on the screen), an approval response is sent from the client terminals 9A4 to 9A7 (step S208).

  Next, the command wrapper 2 determines whether the subsequent execution condition is satisfied by the collection information or the like (step S209). Then, the command wrapper 2 generates screen information of the user interface and transmits it to the client terminal 9A1 (step S210).

  Next, from the viewpoint of double check, the command wrapper 2 makes a confirmation request with information about the system name and the command to be executed to the client terminal 9A2 of another work confirmer who is a colleague of the operator. (Step S211). When the work confirmer performs a confirmation operation (such as clicking a button on the screen), a confirmation response is sent from the client terminal 9A2 (step S212).

  Next, the command wrapper 2 finally issues an execution confirmation request to the client terminal 9A1 of the operation staff (step S213), and the operations staff performs an operation confirmation operation (such as clicking a button on the screen). Then, an execution confirmation response is sent from the client terminal 9A1 (step S214). In response to this, the command wrapper 2 executes the command input from the person in charge of operation (step S215). The command is executed by inputting the command to a system to which the command should be given.

  Thereafter, the command wrapper 2 notifies the client terminals 9A4 to 9A7 and 9A2 of the command execution results (step S216) and registers them in the wrapper information DB 7 (step S217). The client terminal 9A1 of the person in charge of the operation is notified of the result from the system that has input the command by executing the command.

[File copy processing example]
FIG. 11 shows an example of file copy processing. Further, it is assumed that command execution condition / execution procedure information 71 and collection information 72 as shown in FIG. 12 are registered in the wrapper information DB 7 for file copy commands. The collection information 72 is updated to the latest information as appropriate.

  In FIG. 11, when the maintenance person in charge designates the target system name and inputs a file copy command from the client terminal 9A1 to the command wrapper 2 (step S301), the command wrapper 2 outputs a log. Start (step S302). Further, the command wrapper 2 makes a search request to the wrapper information DB 7 based on the target system name and the command (step S303), and the wrapper information DB 7 responds with registration information when the corresponding information is registered (step S303). S304).

  When the command wrapper 2 acquires the registration information, the command wrapper 2 collects the execution condition from the command execution condition / execution procedure information 71 and the collection information 72 included in the registration information according to the execution procedure of the command execution condition / execution procedure information 71. It is determined whether or not the above is satisfied (step S305). Then, the command wrapper 2 generates user interface screen information and transmits it to the client terminal 9A1 (step S306). Here, there are four virtual machines # 1 to # 4 under the same virtualization infrastructure as the virtual machine handled by the person in charge of operation, and the I / O usage batch is determined from the work schedule of the collection information 72 (FIG. 12). If not, the technical condition is satisfied and the current I / O usage status confirmation result is displayed on the screen. The I / O usage status is included in the collection information 72 (FIG. 12).

  Next, from the viewpoint of double check, the command wrapper 2 makes a confirmation request with information about the system name and the command to be executed to the client terminal 9A2 of another work confirmer who is a colleague of the operator. (Step S307). When the work confirmer performs a confirmation operation (such as clicking a button on the screen), a confirmation response is sent from the client terminal 9A2 (step S308).

  Next, the command wrapper 2 finally issues an execution confirmation request to the client terminal 9A1 of the operation person (step S309), and the operation person performs an operation confirmation operation (such as clicking a button on the screen). Then, an execution confirmation response is sent from the client terminal 9A1 (step S310). In response to this, the command wrapper 2 executes the command input from the person in charge of operation (step S311). The command is executed by inputting the command to a system to which the command should be given.

  Thereafter, the command wrapper 2 notifies the client terminal 9A2 of the command execution result (step S312) and registers it in the wrapper information DB 7 (step S313). The client terminal 9A1 of the person in charge of the operation is notified of the result from the system that has input the command by executing the command.

[VM automatic proper placement processing example]
FIG. 13 shows a processing example of VM automatic proper placement. Further, it is assumed that command execution condition / execution procedure information 71 and collection information 72 as shown in FIG. 14 are registered in the wrapper information DB 7 for the virtual machine setting command. The collection information 72 is updated to the latest information as appropriate.

  In FIG. 13, when the maintenance person in charge designates the target system name and inputs a virtual machine setting command from the client terminal 9A1 to the command wrapper 2 (step S401), the command wrapper 2 outputs a log. Is started (step S402). Further, the command wrapper 2 makes a search request to the wrapper information DB 7 based on the target system name and command (step S403), and the wrapper information DB 7 responds with registration information when the corresponding information is registered (step S403). S404).

  When the command wrapper 2 acquires the registration information, the command wrapper 2 collects the execution condition from the command execution condition / execution procedure information 71 and the collection information 72 included in the registration information according to the execution procedure of the command execution condition / execution procedure information 71. Is satisfied (step S405). Then, the command wrapper 2 generates user interface screen information and transmits it to the client terminal 9A1 (step S406). Here, as shown in FIG. 15, when two virtual machines # 1 and # 2 already exist in the virtualization infrastructure to newly set a virtual machine, an overcommit of the newly added virtual machine is performed. Assuming that the rate is calculated and does not exceed the preset overcommit rate, the technical conditions are met and the situation up to this point is displayed on the screen.

  Next, from the viewpoint of double check, the command wrapper 2 makes a confirmation request with information about the system name and the command to be executed to the client terminal 9A2 of another work confirmer who is a colleague of the operator. (Step S407). When the work confirmer performs a confirmation operation (such as clicking a button on the screen), a confirmation response is sent from the client terminal 9A2 (step S408).

  Next, the command wrapper 2 finally issues an execution confirmation request to the client terminal 9A1 of the operation person (step S409), and the operation person performs an operation confirmation operation (such as clicking a button on the screen). Then, an execution confirmation response is sent from the client terminal 9A1 (step S410). In response to this, the command wrapper 2 executes the command input from the person in charge of operation (step S411). The command is executed by inputting the command to a system to which the command should be given.

  Thereafter, the command wrapper 2 notifies the client terminal 9A2 of the command execution result (step S412) and registers it in the wrapper information DB 7 (step S413). The client terminal 9A1 of the person in charge of the operation is notified of the result from the system that has input the command by executing the command.

<Summary>
As described above, according to the present embodiment, the function of the command wrapper forces the work required for executing each command and the conditions that must be satisfied. Therefore, trouble prevention, quality stabilization and work in the VM environment are enforced. Efficiency can be improved.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

DESCRIPTION OF SYMBOLS 1, 1A, 1B Physical server 11, 11A1-11B2 Virtual machine 12, 12A, 12B Virtual switch 2 Command wrapper 21 Wrapper agent part 22 Wrapper manager part 23 Notification agent part 24 Notification manager part 3 Maintenance network 4 Monitoring apparatus 5 Monitoring information DB
6 Maintenance procedure DB
7 Wrapper information DB
71 Command execution condition / execution procedure information 72 Collected information 8, 8A, 8B Business network 9, 9A1-9B2 Client terminal

Claims (8)

A program that runs in an environment where one or more virtual machines run,
Accepts commands entered from the terminal of the operator,
With reference to the storage unit that associates the command with the execution procedure and execution condition of the command, the execution procedure and execution condition corresponding to the received command are acquired,
Determine whether the execution conditions are satisfied sequentially according to the execution procedure,
If the execution procedure and conditions require the approval or confirmation of a specified third party, the approval or confirmation request is notified to the third party, and the approval or confirmation is accepted.
Execute a command when all execution procedures and execution conditions are satisfied,
A VM environment command execution management program which causes a computer to execute processing. Collect system information corresponding to each command and store it in the storage unit;
Determining whether the execution condition is satisfied using the information;
The VM environment command execution management program according to claim 1. Displaying the status of the processing for the execution procedure and the execution condition to the person in charge of operation,
The VM environment command execution management program according to claim 1 or 2. Notifying the third party of the execution result of the command,
The VM environment command execution management program according to any one of claims 1 to 3. Request confirmation of the person in charge immediately before the execution of the command,
Execute the command when confirmation is obtained,
The VM environment command execution management program according to any one of claims 1 to 4, wherein A method executed in an environment in which one or more virtual machines are operating,
Accepts commands entered from the terminal of the operator,
With reference to the storage unit that associates the command with the execution procedure and execution condition of the command, the execution procedure and execution condition corresponding to the received command are acquired,
Determine whether the execution conditions are satisfied sequentially according to the execution procedure,
If the execution procedure and conditions require the approval or confirmation of a specified third party, the approval or confirmation request is notified to the third party, and the approval or confirmation is accepted.
Execute a command when all execution procedures and execution conditions are satisfied,
A VM environment command execution management method, characterized by causing a computer to execute processing. A device installed in an environment in which one or more virtual machines operate,
Means for accepting commands entered from the terminal of the operator,
Means for acquiring an execution procedure and an execution condition corresponding to the received command with reference to a storage unit that associates the command with the execution procedure and execution condition of the command;
Means for sequentially determining whether or not the execution condition is satisfied according to the execution procedure;
Means for accepting approval or confirmation by notifying the third party of a request for approval or confirmation when the execution procedure and execution conditions require approval or confirmation of a predetermined third party;
Means for executing a command when all execution procedures and execution conditions are satisfied;
A VM environment command execution management device comprising: A system that constitutes an environment in which one or more virtual machines operate,
Means for accepting commands entered from the terminal of the operator,
Means for acquiring an execution procedure and an execution condition corresponding to the received command with reference to a storage unit that associates the command with the execution procedure and execution condition of the command;
Means for sequentially determining whether or not the execution condition is satisfied according to the execution procedure;
Means for accepting approval or confirmation by notifying the third party of a request for approval or confirmation when the execution procedure and execution conditions require approval or confirmation of a predetermined third party;
Means for executing a command when all execution procedures and execution conditions are satisfied;
A VM environment command execution management system comprising:

Images