JP2017102818A - Virtual computer management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a virtual computer management system with which it is possible to quickly specify a physical computer from a virtual computer name in the operation management server of the virtual computer management system.SOLUTION: The virtual computer management server 300 of a virtual computer management system 100 comprises: a virtual computer configuration change unit for changing the configuration of virtual computers; a virtual computer master table in which a current configuration including the physical position information of virtual computers is preserved; and a virtual computer configuration change notification unit for notifying an operation management server 400 of a content that includes a change when the change is made to the virtual computer master table. The operation management server 400 is provided with a physical computer identifier table having a physical computer identifier for identifying the arrangement position of a physical computer and a virtual computer name field, and a configuration change reflection unit for receiving the notification from the virtual computer configuration change notification unit, and changing the physical computer identifier table.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a virtual machine management system, and is suitably applied to, for example, a virtual server system that is connected to a network and provides a service.

  With the spread of computer networks such as the Internet, it is common to access a server device and receive various services. Providing services via such a network requires specialized knowledge for the maintenance and operation of server devices, so a company acting on behalf of system operation provides server hosting and a virtual server system in the form of a cloud. At the same time, maintenance and operation are often performed. Virtual server system operations generally handle virtual machine management servers for mainly creating (constructing) virtual servers, changing virtual server specifications, deleting virtual servers, etc. There is an operation management server for this purpose, and these perform operations with different management systems, thereby providing efficient services.

  When a load imbalance occurs between a plurality of groups of virtual computers, Patent Literature 1 removes an appropriate physical computer from a low load group and reassigns the physical computer to a high load group. It discloses reducing the load imbalance between groups.

JP 2012-220977 A

  However, in such operations with different management systems, for example, even if a failure caused by hardware occurs in the virtual computer and the operation management server is notified of the failure, the physical computer is identified from the virtual computer name. Or customers could not be identified quickly.

  The present invention has been made in consideration of the above points, and is intended to provide a virtual machine management system in which an operation management server can quickly identify a physical machine from a virtual machine name.

  In order to solve such a problem, a virtual machine management system of the present invention includes a virtual machine management server that manages a virtual machine, and an operation management server that manages an operation of a physical machine that operates the virtual machine, The virtual machine management server includes: a virtual machine configuration changing unit that changes a configuration of the virtual machine; a virtual machine master table that stores a current configuration including physical location information of the virtual machine; and the virtual machine master table A virtual machine configuration change notification unit that notifies the operation management server of contents including the change when there is a change, and the operation management server includes a physical computer identifier that identifies an arrangement position of the physical computer, and A physical computer identifier table having a virtual computer name field, and a notification from the virtual computer configuration change unit, A configuration change reflecting unit to change the serial physical computer identifier table, a virtual machine management system, characterized in that it comprises a.

  According to the present invention, a physical computer can be quickly identified from a virtual computer name in the operation management server of the virtual computer management system.

1 is a diagram schematically showing a virtual machine management system according to an embodiment of the present invention. FIG. It is a figure shown about an example of the hardware constitutions of a virtual machine management server. It is a figure shown about the functional block of a virtual machine management server. It is a figure shown about the functional block of an operation management server. It is a figure which shows the example of the screen of virtual machine management in a client terminal. It is a flowchart shown about a virtual machine structure change process. It is a figure which shows the example of a structure of a virtual machine master table. It is a flowchart shown about a virtual machine change notification process. It is a flowchart shown about a structure change reflection process. It is a figure shown about the example of a structure of a physical computer identifier table. It is a figure shown about the example of a structure of a virtual machine name table. It is a figure shown about the example of a structure of a virtual machine identifier table. It is a figure shown about the example of a structure of an operation schedule table. It is a flowchart shown about a schedule notification process. It is a flowchart shown about a failure information notification process. It is a flowchart shown about a virtual machine message preservation | save process. It is a figure shown about the example of a structure of a virtual machine message table. It is a figure which shows the example of the screen of a virtual machine search in an operation management server.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the following description, similar elements are denoted by the same reference numerals, and redundant description is omitted.

(1) Configuration of Virtual Machine Management System According to this Embodiment FIG. 1 is a diagram schematically showing a virtual machine management system 100 according to an embodiment of the present invention. As shown in this figure, the virtual machine management system 100 includes a cloud 200 that is a storage on a network having a virtual machine group A, a virtual machine group B,. For example, a client terminal 110 that is a user terminal that is connected and uses a virtual machine in the virtual machine group A, and a virtual machine management server 300 that performs management including creation of a virtual machine in the virtual machine group A, For example, an operation management server 400 that performs operation management of physical computers that operate virtual computers in the virtual computer group A is included. Here, although the client terminal 110 using the virtual machine group A is included in the present embodiment, the virtual machine management system 100 may not include the client terminal 110, and the cloud 200 The virtual machine group A, the virtual machine group B, etc., which are a plurality of virtual machine groups, are included, but only one virtual machine group may be provided.

  FIG. 2 shows an example of the hardware configuration of the virtual machine management server 300. The virtual machine management server 300 includes a volatile storage unit 302 including a cache memory and a RAM (Random Access Memory), a non-volatile storage unit 303 including a hard disk and a flash memory, and a volatile storage unit 302 and a non-volatile storage unit 303. A CPU (Central Processing Unit) 301 that executes a stored program, an input device 304 such as a mouse and a keyboard, and a display device 305 such as a liquid crystal display device that displays images are included. The operation management server 400 and the client terminal 110 can use the same hardware configuration.

  FIG. 3 is a functional block diagram of the virtual machine management server 300. Each functional block shown in this figure is realized by the cooperation of the hardware shown in FIG. As shown in FIG. 3, the virtual machine management server 300 includes a control unit 310 that realizes functions mainly by processing by the CPU 301 and a storage unit 330 that is mainly realized by a storage area of a nonvolatile storage unit 303. doing. The control unit 310 includes, for example, a virtual machine configuration change unit 312 that changes the configuration of the virtual machines in the virtual machine group A, and a virtual machine in which the current configuration including, for example, the physical position information of the virtual machines in the virtual machine group A is stored. When there is a change in the master table 332 and the virtual machine master table 332, there is a virtual machine configuration change notification unit 314 that notifies the operation management server 400 of the contents including the change.

  FIG. 4 is a functional block diagram of the operation management server 400. It should be noted that each functional block shown in this figure is realized by the same hardware as in FIG. 2 operating in cooperation with the virtual machine management server 300. As shown in FIG. 4, the operation management server 400 includes a control unit 410 that realizes functions mainly by processing by a CPU, and a storage unit 440 that is mainly realized by a storage area of a nonvolatile storage unit. Yes.

  The operation management server 400 also receives a physical computer identifier table 443 having at least a physical computer identifier and a virtual computer name field for identifying the location of the physical computer, and a notification from the virtual computer configuration change unit 312, Configuration change reflection unit 411 for changing the identifier table 443, a virtual machine name table 441 including customer information related to the virtual machine, a virtual machine identifier table 442 including network information including the network address of the virtual machine, and at least a physical computer A schedule for identifying a virtual machine to be stopped in the operation schedule table 444 based on the operation schedule table 444 for storing the stop schedule and the physical computer identifier table 443 and notifying the virtual machine management server 300 When the failure information of the physical computer is input, the knowledge unit 412, the failure information notification unit 413 that identifies the virtual computer related to the failure information and notifies the virtual computer management server, and the failure-related message transmitted from the virtual computer Is stored in the virtual machine message table 446. If the message is not a duplicate message after receiving the message and determining whether or not the message is a duplicate message, the virtual machine message received and saved is stored in the virtual machine message table. Part 414.

(2) Virtual Machine Configuration Change Processing Next, virtual computer configuration change processing will be described. The processing for changing the configuration of the virtual machine includes new creation, change, deletion and migration (migration) of the virtual machine. Such a change process is performed when the virtual machine management server 300 receives an instruction from the client terminal 110, and when the virtual machine manager directly operates the virtual machine management server 300. There is.

  FIG. 5 shows a screen 510 as an example of a virtual machine management screen in the client terminal 110. This screen 510 shows an example of an input screen for creating a new virtual machine. In the input field 513, the customer name and virtual machine name, and the CPU, memory, OS (Operating System), HDD required for the virtual machine are displayed. There is a field for entering each specification of (Hard Disk Drive). The screen 510 is provided with a creation button 515 for newly creating a virtual machine in accordance with the specifications of these input fields 513 and a reset button 514 for resetting all inputs of the input fields 513. On the virtual machine management screen, there are functions of “virtual machine change”, “virtual machine deletion” and “migration” in addition to the function of “virtual machine new creation”, and a function selection area 511 for selecting these functions. Is provided. As a function other than the virtual machine management, for example, it may have a function of “user setting” such as “virtual machine search” for searching one of the virtual machine name and physical computer identifier, and a change in display method. .

  FIG. 6 is a flowchart showing the virtual machine configuration change process S10. For example, when a new virtual machine creation operation is performed from the screen 510 in FIG. 5, an instruction to create a new virtual machine is transmitted from the client terminal 110 to the virtual machine management server 300 together with the contents input in the input field of the screen 510. Then, in accordance with the instruction, the virtual machine configuration change unit 312 of the virtual machine management server 300 performs the virtual machine configuration change process S10. The instruction here is an instruction to create a new virtual machine, but may be any instruction other than new creation, such as change, deletion, and migration. In addition, although an instruction from the client terminal 110 is received, any one of new creation, change, deletion, and migration may be performed by directly operating the virtual machine management server 300. In this case, the virtual machine management server 300 may display a screen similar to the screen 510 of the client terminal 110 in FIG. 5 on the display device and allow the virtual machine manager to operate.

  As shown in FIG. 6, the virtual machine configuration change processing S10 first determines whether the instruction is any one of new creation, change, deletion and migration of a virtual machine (S11). If none of the instructions are given, the virtual machine configuration change process S10 is terminated. If the instruction is any of the instructions, the virtual machine is newly created, changed, deleted, or migrated based on the received or input specification (S12). When the process of step S12 is completed, the result of the process is reflected and updated in the virtual machine master table 332 (see FIG. 7) (S13), and the virtual machine configuration change process S10 is terminated.

  FIG. 7 shows an example of the configuration of the virtual machine master table 332. As shown in this figure, the virtual machine master table 332 includes a customer information field that is a customer name, a virtual machine name field that is input by the customer, and an LPAR that is a unit obtained by logically dividing the physical computer. A field, an IP field that is an IP address, a VLAN field that is a virtual network segment of a virtual machine, and a field of physical related information that is related information related to the location of a physical computer assigned by a virtual machine management server; ,have. The virtual machine configuration change unit 312 adds or deletes a record to the virtual machine master table 332 or changes a value when a virtual machine is newly created, changed, deleted, or migrated.

  FIG. 8 is a flowchart showing the virtual machine change notification process S20 performed by the virtual machine configuration change notification unit 314. As shown in this figure, in the virtual machine change notification process S20, it is first determined whether or not the virtual machine master table 332 has been changed (S21). If there is no change, the virtual machine configuration change notification process S20 is terminated. If there is a change, information including the changed part is transmitted to the operation management server 400 (S22). Here, the information including the changed part may be only the changed part, may be information in record units including the changed part, or may include other information such as the entire virtual machine master table 332. .

  FIG. 9 is a flowchart illustrating the configuration change reflection process S30 performed by the configuration change reflection unit 411 of the operation management server 400. As shown in this figure, in the configuration change reflection process S30, it is first determined whether or not a notification that the virtual machine master table 332 has been changed has been received from the virtual machine management server 300 (S31). Here, when the notification is not received, the configuration change reflection process S30 is terminated. When the notification is received, the table that needs to be changed among the physical computer identifier table 443, the virtual computer name table 441, and the virtual computer identifier table 442 stored in the operation management server 400 is appropriately changed. (S32).

  10 to 12 are diagrams illustrating examples of configurations of the physical computer identifier table 443, the virtual computer name table 441, and the virtual computer identifier table 442, respectively. As shown in FIG. 10, in addition to the virtual computer name field, the physical computer identifier table 443 includes a “center” indicating a data center where a physical computer is installed as a plurality of identifiers indicating positions where the physical computer is installed. ”Field,“ Floor ”field indicating the floor where the physical computer is installed,“ Rack ”field indicating the rack where the physical computer is installed,“ Chassis ”field indicating the chassis where the physical computer is installed, and It has a “Slot” field which is a position in the chassis. As shown in FIG. 11, the virtual machine name table 441 has fields of “virtual machine name” and “customer information”. As shown in FIG. 12, the virtual machine identifier table 442 includes a virtual machine name field, a “LPAR” field that is a unit obtained by logically dividing a physical machine, and an IP address of the virtual machine “ IP ”field and“ VLAN ”field, which is a virtual network segment of the virtual machine. In the configuration change reflection process S30, the configuration change reflection unit 411 causes the physical computer identifier table 443, the virtual computer name table 441, and the virtual computer identifier table 442 to be newly created or deleted. Records in each table are added or deleted, and when there is a change or migration, the corresponding record is appropriately corrected. The configuration of each table illustrated in FIGS. 10 to 12 is not limited to this, and may be combined into one table, or may not include the fields illustrated in each table in FIGS. Other fields may be included.

(3) Stop Schedule Response Processing Next, stop schedule response processing will be described. In order to carry out regular maintenance and preventive maintenance of IT (Information Technology) equipment, it is necessary to suspend the physical computer. By moving a virtual machine running on a physical computer scheduled to be stopped within a predetermined period to another physical computer, the service can be provided without stopping.

  FIG. 13 shows an operation schedule table 444 for inputting a schedule to be stopped. As shown in this figure, the operation schedule table 444 has fields of “center”, “Floor”, “Rack”, “Chassis”, and “Slot” which are physical identifiers. ”Or“ operation status ”indicating“ OFF ”being stopped, and a“ schedule ”field for inputting a date or date and time. In the “Schedule” field, when the date or the date and time described is reached, the operating status of the physical computer indicated by the physical identifier changes from “ON” to “OFF” or from “OFF” to “ON”. It is shown that. The operation manager adds a record to the operation schedule table 444 and inputs a physical identifier, a schedule, and the like when the scheduled stop of the physical computer is determined.

  FIG. 14 is a flowchart of the schedule notification process S40 performed by the schedule notification unit 412. As shown in this figure, in the schedule notification process S40, first, it is determined from the operation schedule table 444 whether there is a schedule for stopping the physical computer within a predetermined period (S41). Here, when the stop schedule within the predetermined period is not detected, the schedule notification process S40 is terminated. When a schedule that is within a predetermined period until the stop is detected, the physical computer identifier table 443 is referred to, the virtual computer name is specified from the physical identifier of the operation schedule table 444 (S42), and the specified stop schedule is determined. The virtual machine name is notified to the virtual machine management server 300 (S43). In this case, it is good also as notifying with the date or date etc. which are stopped. When the specified virtual machine name scheduled to be stopped is notified to the virtual machine management server 300, the schedule notification unit 412 ends the schedule notification process S40. Receiving this notification, the virtual machine management server 300 performs the virtual machine configuration change process S10 in FIG. 6 for the virtual machine with the corresponding virtual machine name, in the virtual machine configuration change unit 312 as having received the migration instruction. That is, the virtual machine configuration change unit 312 of the virtual machine management server 300 performs migration of the identified virtual machine based on the notification from the schedule notification unit 412, and changes the configuration of the virtual machine due to the migration to the virtual machine master table Save to 332. Subsequently, as described above, the virtual machine configuration change notification process S20 and the configuration change reflection process S30 are performed. Therefore, since the operation management server 400 can identify the virtual computer, even if the physical computer is scheduled to be stopped for regular maintenance or the like, it is easy to input the physical computer information without stopping the service. Continuous service can be provided. The determination of whether or not there is a stop schedule is based on the case where the stop is within a predetermined period, but it may be whether or not there is a stop schedule regardless of the predetermined period. In addition, the operation schedule table 444 may also store a schedule for restarting from a stopped state, and perform a process for setting a migration destination or a new virtual computer creation destination for the restarted physical computer.

(4) Failure Response Processing FIG. 15 is a diagram illustrating a flowchart of failure information notification processing S50 performed by the failure information notification unit 413. For example, when there is a failure in the physical computer, the operation manager inputs failure information to the operation management server 400, and the operation management server 400 performs processing based on the input content. As shown in FIG. 15, in the failure information notification process S50, first, the failure information notification unit 413 of the operation management server 400 determines whether or not failure information has been input (S51). If no failure information input is detected, the failure information notification process S50 ends. If an input of failure information is detected, the virtual computer name is identified from the physical identifier of the operation schedule table 444 with reference to the physical computer identifier table 443 (S52), and the identified virtual computer in which the failure has occurred The name is notified to the virtual machine management server 300 (S53). When the name of the identified virtual machine in which the failure has occurred is notified to the virtual machine management server 300, the failure information notification unit 413 ends the failure information notification process S50.

  Receiving this notification, the virtual machine management server 300 performs the virtual machine configuration change process S10 in FIG. 6 for the virtual machine with the corresponding virtual machine name, in the virtual machine configuration change unit 312 as having received the migration instruction. That is, the virtual machine configuration change unit 312 of the virtual machine management server 300 performs migration of the identified virtual machine based on the notification from the failure information notification unit 413, and changes the configuration of the virtual machine due to the migration to the virtual machine master. Save in table 332. Subsequently, as described above, the virtual machine configuration change notification process S20 and the configuration change reflection process S30 are performed. Therefore, even if a failure occurs in the physical computer, the operation management server 400 can identify the virtual computer, and therefore, only by inputting the information of the physical computer, the period during which service provision is affected is minimized. be able to.

(5) Virtual Machine Message Saving Process FIG. 16 is a flowchart showing the virtual machine message saving process S60 by the virtual machine message reception saving unit 414. As shown in this figure, in the virtual machine message storage process S60, for example, it is determined whether a message related to a failure is received from the virtual machine group A (S61). If no message has been received, the virtual machine message storage process S60 is terminated. If a message has been received, it is determined whether a message that overlaps the received message is already stored in the virtual machine message table 446 (see FIG. 17) (S62). If the message is a duplicate message already stored in the virtual machine message table 446, the virtual machine message storage process S60 is terminated. If it is not a duplicate message, a message regarding the failure is stored in the virtual machine message table 446 (S63), and the virtual machine message storage process S60 is terminated.

  FIG. 17 is a diagram illustrating an example of the configuration of the virtual machine message table 446. As shown in this figure, the virtual machine message table 446 is composed of a virtual machine name field and a message field for storing a message received from the virtual machine group A, for example. The operation manager confirms the message stored in the virtual machine message table 446, and identifies customer information and physical information of the virtual machine related to the failure from the screen 520 of the operation management server 400 as shown in FIG. 18, for example. Therefore, the operation manager can deal with the failure. Further, the operation manager may input the failure information to the operation management server 400 and perform the failure information notification process S50.

  FIG. 18 is a diagram illustrating an example of a display screen 520 displayed on the display device of the operation management server 400. As shown in this figure, on the screen 520, the search keyword is entered in one or more of “customer name”, “virtual computer name”, “center”, “floor” and “rack” in the search keyword input area 521. When the search button 523 is pressed, a list of virtual machines corresponding to the input search keyword is displayed in the virtual machine list display area 522. Such a search function is realized by searching the “physical computer identifier table”, “virtual computer identifier table”, and “virtual computer name table”. In this way, by providing a user interface that can be updated in real time and can quickly identify the physical computer from the virtual computer name, the operation manager can use the displayed virtual computer list to make necessary operations and failures. Can respond quickly. As a function other than the virtual machine search, for example, a “fault management” for displaying a fault and a response status for the fault, and a “user setting” function such as a change in display method may be provided.

(6) Effects of this Embodiment A virtual machine management system 100 according to this embodiment includes a virtual machine management server 300 that manages virtual machines, and an operation management server that manages the operation of physical machines that run virtual machines. 400, the virtual machine management server 300 includes a virtual machine configuration change unit 312 that changes the configuration of the virtual machine, and a virtual machine master table 332 that stores the current configuration including the physical location information of the virtual machine. And a virtual machine configuration change notification unit 314 that notifies the operation management server 400 of the contents including the change when the virtual machine master table 332 is changed. A physical computer identifier table 443 having physical computer identifier and virtual computer name fields for identifying A configuration change reflection unit 411 that receives a notification from the computer configuration change unit 312 and changes the physical computer identifier table 443; Therefore, the operation management server 400 can quickly identify the physical computer from the virtual computer name.

  In addition, the operation management server 400 according to the present embodiment specifies a virtual machine to be stopped in the operation schedule table 444 based on the operation schedule table 444 that stores a physical computer stop schedule and the physical computer identifier table 443. And a virtual machine configuration change unit 312 of the virtual machine management server 300 that is identified based on the notification from the schedule notification part 412. It is also possible to store the change in the configuration of the virtual machine resulting from the migration in the virtual machine master table 332. In this case, for example, even if the physical computer is scheduled to be stopped due to maintenance or the like, the operation management server 400 can simply and continuously input information on the physical computer without stopping the service. Services can be provided. Furthermore, the schedule notification unit 412 of the operation management server 400 may notify the virtual machine management server 300 when it is detected that the time is within a predetermined period until the stop. In this case, the migration time can be secured in advance before the stop, so that the migration can be completed before the virtual machine is stopped.

  Further, the operation management server 400 according to the present embodiment determines that a failure information has been input, identifies a virtual machine related to the failure information, and notifies a failure information notification unit 413 that notifies the virtual machine management server 300 The virtual machine configuration changing unit 312 of the virtual machine management server 300 performs migration of the identified virtual machine based on the notification from the failure information notification unit 413, and changes the configuration of the virtual machine by migration. It may be stored in the virtual machine master table 332. In this case, even when a failure occurs in the physical computer, the operation management server 400 can only minimize the period during which the service provision is affected by only inputting the physical computer information. .

  In addition, the operation management server 400 according to the present embodiment may further include a virtual machine identifier table including network information including the network address of the virtual machine. In this case, it is possible to quickly cope with operation management that requires network information. In addition, the operation management server 400 according to the present embodiment may further include a virtual computer name table including customer information related to the virtual computer. In this case, it is possible to quickly cope with operation management that requires customer information.

  In addition, the operation management server 400 according to the present embodiment receives the message from the virtual machine message table 446 in which a message related to a failure transmitted from the virtual machine is stored, and determines whether the message is a duplicate message. If it is not a duplicate message, a virtual machine message reception storage unit 414 that stores the message in the virtual machine message table may be included. In this case, it is possible to search for a physical computer corresponding to the virtual computer associated with the message, and thus it is possible to quickly cope with a failure.

  The present invention can be applied to a virtual server system that is connected to a network and provides a service.

DESCRIPTION OF SYMBOLS 100 Virtual computer management system, 110 Client terminal, 200 Cloud, 300 Virtual computer management server, 302 Volatile memory | storage part, 303 Non-volatile memory | storage part, 304 Input device, 305 Display apparatus, 310 Control part, 312 Virtual computer structure change part, 314 Virtual computer configuration change notification unit, 330 storage unit, 332 virtual computer master table, 400 operation management server, 410 control unit, 411 configuration change reflection unit, 412 schedule notification unit, 413 failure information notification unit, 414 reception of virtual computer message , 440 storage unit, 441 virtual computer name table, 442 virtual computer identifier table, 443 physical computer identifier table, 444 operation schedule table, 446 virtual computer message table, 510 screen, 511 Function selection area, 513 input field, 514 reset button, 515 creation button, 520 screen, 521 search keyword input area, 522 virtual computer list display area, 523 search button

Claims (7)

A virtual machine management server for managing virtual machines;
An operation management server that performs operation management of a physical computer that operates the virtual computer,
The virtual machine management server is
A virtual machine configuration changing unit for changing the configuration of the virtual machine;
A virtual machine master table in which a current configuration including physical location information of the virtual machine is stored;
A virtual machine configuration change notification unit for notifying the operation management server of the contents including the change when there is a change in the virtual machine master table;
The operation management server
A physical computer identifier table having fields of a physical computer identifier and a virtual computer name for identifying an arrangement position of the physical computer;
A virtual machine management system comprising: a configuration change reflection unit that receives a notification from the virtual machine configuration change unit and changes the physical computer identifier table. In the virtual machine management system according to claim 1,
The operation management server
An operation schedule table for storing a schedule for stopping the physical computer;
Based on the physical computer identifier table, the virtual computer to be stopped in the operation schedule table is identified, and a schedule notification unit that notifies the virtual computer management server,
The virtual machine configuration change unit of the virtual machine management server performs the migration of the identified virtual machine based on the notification from the schedule notification unit, and changes the configuration of the virtual machine by the migration to the virtual machine A virtual machine management system characterized in that it is stored in a machine master table. In the virtual machine management system according to claim 2,
The virtual machine management system, wherein the schedule notification unit of the operation management server notifies the virtual machine management server when detecting that the time is within a predetermined period until the stop. In the virtual machine management system according to any one of claims 1 to 3,
The operation management server
A failure information notification unit that determines that there has been input of failure information, identifies the virtual machine related to the failure information, and notifies the virtual machine management server;
The virtual machine configuration change unit of the virtual machine management server performs migration of the identified virtual machine based on the notification from the failure information notification unit, and changes the configuration of the virtual machine by the migration to the virtual machine A virtual machine management system characterized in that it is stored in a machine master table. In the virtual machine management system according to any one of claims 1 to 4,
The operation management server further includes a virtual machine identifier table including network information including a network address of the virtual machine. In the virtual machine management system according to any one of claims 1 to 5,
The operation management server further includes a virtual computer name table including customer information related to the virtual computer. In the virtual machine management system according to any one of claims 1 to 6,
The operation management server
A virtual machine message table in which messages about failures sent from the virtual machine are stored;
A virtual machine message reception storage unit for storing the message in the virtual machine message table if the message is not a duplicate message after receiving the message and determining whether the message is a duplicate message or not. A virtual machine management system.

Images