JP6152050B2 - Virtual machine management apparatus, server virtualization system, virtual machine management method and program - Google Patents

Description

  The present invention relates to a virtual machine management device, a server virtualization system, a virtual machine management method, and a program.

  In a virtualized infrastructure system that allows a plurality of physical machines to behave as a single infrastructure, it is required to optimize resources by minimizing the surplus resources of each physical machine. In order to optimize the resources of the virtualization infrastructure, a technique for dynamically transferring virtual machines has been established (see, for example, Patent Document 1). At this time, it is necessary to confirm whether or not the service operating on the virtual machine is operating normally when the virtual machine is dynamically moved, and the normality is manually confirmed by the maintenance manager.

  Patent Document 2 discloses a technique for notifying an operator at a timing when a predetermined operation work occurs. Patent Document 3 discloses a technique for executing a failure countermeasure job when a failure occurs in the system. Patent Document 4 discloses a technique for executing a procedure for grasping a situation for each event that occurs by detecting a change in the situation in a network.

JP 2012-003651 A JP2013-029985A JP 2012-093894 A JP 2011-155364 A

However, when the maintenance manager manually checks the normality of the transferred virtual machine, there is a problem that a time lag occurs between the transfer and the normality confirmation, and the maintenance manager costs human costs.
An object of the present invention is to provide a virtual machine management apparatus, a server virtualization system, a virtual machine management method, and a program that solve the above-described problems.

The first aspect is a notification receiving unit that receives a notification indicating that the virtual machine has been transferred from a physical machine that emulates the virtual machine, and the notification is transferred when the notification receiving unit receives the notification. A normality confirmation unit that confirms the normality of the virtual machine, and the normality confirmation unit, when the normality of the transferred virtual machine is determined to be bad, the physical machine and the transfer before the transfer It is a virtual machine management apparatus that includes a virtual machine starting unit that starts a physical machine other than the physical machine later that starts the same virtual machine having a redundant configuration of the virtual machine .

In addition, a third aspect is the first aspect, in which the virtual machine activation unit has a CPU usage rate or a memory usage rate out of the physical machine before the transfer and the physical machine other than the physical machine after the transfer. It is a virtual machine management device that determines a physical machine for starting the same virtual machine based on at least one.

According to a fourth aspect, in the first or second aspect, a program for emulating the same virtual machine is stored in a plurality of the physical machines, and the virtual machine activation unit is A virtual machine management apparatus that determines the physical machine that stores a program for emulating the same virtual machine , which is a redundant configuration of the machine , as a physical machine that starts the same virtual machine .

The fifth aspect includes a plurality of physical machines that emulate a virtual machine and a virtual machine management device that manages the plurality of physical machines, and the physical machine transfers the virtual machine when the virtual machine is transferred. A transfer notification unit that issues a notification indicating that the machine has been transferred, wherein the virtual machine management device receives a notification indicating that the virtual machine has been transferred from the physical machine; and the notification When the receiving unit receives the notification, the normality confirmation unit that confirms the normality of the transferred virtual machine, and the normality confirmation unit is defective in the normality of the transferred virtual machine If it is determined that the virtual machine is activated, the physical machine other than the physical machine before the transfer and the physical machine other than the physical machine after the transfer are started with the same virtual machine having a redundant configuration of the virtual machine. A server virtualization system comprising a part.

According to a sixth aspect, the notification receiving unit of the virtual machine management apparatus receives a notification indicating that the virtual machine has been transferred from a physical machine that emulates the virtual machine, and the notification receiving unit When the notification is received, the normality confirmation unit of the virtual machine management device confirms the normality of the transferred virtual machine; and When it is determined that the normality is bad, the virtual machine activation unit of the virtual machine management device has a redundant configuration of the virtual machine in the physical machine before the transfer and the physical machine other than the physical machine after the transfer. A virtual machine management method including a step of starting the same virtual machine .

In the seventh aspect, the computer receives a notification indicating that the virtual machine has been transferred from a physical machine that emulates the virtual machine, and the notification receiving unit receives the notification. A normality confirmation unit for confirming the normality of the transferred virtual machine, and when the normality confirmation unit determines that the normality of the transferred virtual machine is bad, This is a program for causing a physical machine other than the machine and the transferred physical machine to function as a virtual machine activation unit that activates the same virtual machine having a redundant configuration of the virtual machine .

  According to at least one of the above aspects, the virtual machine management apparatus can automatically check the normality of the virtual machine after the virtual machine has moved, without depending on the maintenance manager.

It is the schematic which shows the structure of the server virtualization system by one Embodiment. It is a schematic block diagram which shows the software structure of a server virtualization system. It is a figure which shows the example of the information which a table memory | storage part memorize | stores. It is a sequence diagram which shows the outline | summary of operation | movement of a server virtualization system. It is a flowchart which shows operation | movement of the normality confirmation server by one Embodiment. It is a schematic block diagram which shows the structure of the computer which concerns on at least 1 embodiment.

Hereinafter, embodiments will be described in detail with reference to the drawings.
FIG. 1 is a schematic diagram illustrating a configuration of a server virtualization system 1 according to an embodiment.
The server virtualization system 1 includes a plurality of physical machines 100 and a normality confirmation server 200. In the present embodiment, the normality confirmation server 200 is an example of a virtual machine management apparatus.

  Each physical machine 100 emulates one or more virtual machines 110 by executing a virtual machine program. Further, each physical machine 100 configures one virtualization platform by executing the same virtualization platform program. Thereby, the server virtualization system 1 can transfer the virtual machine 110 between the plurality of physical machines 100. The plurality of physical machines 100 are stored in the data center 300, respectively. 1 illustrates an example in which the server virtualization system 1 includes two data centers 300, and each data center 300 includes one physical machine 100. However, the present invention is not limited to this. For example, the server virtualization system 1 may include three or more data centers 300 or one data center 300. Each data center 300 may include two or more physical machines 100.

  The normality confirmation server 200 confirms the normality of the operation of the virtual machine 110 after the transfer when the virtual machine 110 is transferred between the physical machines 100. If the normality confirmation server 200 determines that the operation of the virtual machine 110 after the transfer is not normal, the normality confirmation server 200 causes the other physical machine 100 to activate the virtual machine 110 that is the same as the virtual machine 110.

FIG. 2 is a schematic block diagram showing a software configuration of the server virtualization system 1.
Each physical machine 100 includes a virtual machine storage unit 101, a virtual machine control unit 102, a transfer control unit 103, a transfer notification unit 104, and a command receiving unit 105 by executing a virtualization platform program.
The virtual machine storage unit 101 stores a virtual machine program for emulating the virtual machine 110.
The virtual machine control unit 102 starts (emulates) the virtual machine 110 by executing a virtual machine program stored in the virtual machine storage unit 101.
The transfer control unit 103 transfers the virtual machine 110 emulated by the virtual machine control unit 102 to another physical machine 100.
The transfer notification unit 104 issues a transfer notification to the normality confirmation server 200 when the transfer control unit 103 transfers the virtual machine 110.
The command receiving unit 105 receives a startup command for the virtual machine 110 from the normality confirmation server 200.

  Each physical machine 100 stores a plurality of virtual machine programs in the virtual machine storage unit 101, but not all virtual machine programs are executed. A plurality of physical machines 100 each store a virtual machine program that emulates the same virtual machine 110. This is a redundant configuration for emulating the same virtual machine 110 by another physical machine 100 when a certain physical machine 100 cannot normally emulate the virtual machine 110. Therefore, when a certain physical machine 100 can normally emulate the virtual machine 110, another physical machine 100 that can emulate the same virtual machine 110 does not need to emulate the virtual machine 110.

The normality confirmation server 200 includes a table storage unit 201, a notification reception unit 202, a normality confirmation unit 203, a resource status confirmation unit 204, and a virtual machine activation unit 205.
The table storage unit 201 stores a virtual machine normality confirmation table and a physical machine resource state table. The virtual machine normality confirmation table stores the name of the virtual machine whose normality is to be confirmed and the normality confirmation procedure of the virtual machine 110 in association with each other. The physical machine resource state table includes, for each physical machine 100, the name of the virtual machine 110 that can be emulated by the physical machine 100, the name of the virtual machine 110 that is the same as the virtual machine 110, and the resource of the physical machine 100. Such information is stored.
The notification receiving unit 202 receives a notification of the transfer of the virtual machine 110 from the physical machine 100.
The normality confirmation unit 203 confirms the normality of the transferred virtual machine 110 based on the virtual machine normality confirmation table stored in the table storage unit 201. Specifically, the normality confirmation unit 203 confirms the normality of the virtual machine 110 by accessing the virtual machine 110 emulated by the virtual machine control unit 102 of the physical server after the transfer.
The resource status confirmation unit 204 confirms the physical machine resource status table and identifies the physical machine 100 that is the target of starting the virtual machine 110.
The virtual machine activation unit 205 activates the virtual machine 110 on the physical machine 100 identified by the resource status confirmation unit 204.

FIG. 3 is a diagram illustrating an example of information stored in the table storage unit 201.
As shown in FIG. 3A, the virtual machine normality confirmation table stores virtual machine names and normality confirmation procedures in association with each other. In FIG. 3A, a URI (Uniform Resource Identifier) is stored as a normality confirmation procedure. This indicates that normality is confirmed by whether or not a normal response can be obtained by accessing the URI.

  As shown in FIG. 3B, the physical machine resource state table includes a physical machine name, a virtual machine name, an NG flag, a selection flag, the same virtual machine name, a CPU usage rate of the physical machine 100, and a memory usage of the physical machine 100. The rate, resource threshold over flag, resource sum, and confirmation flag are stored in association with each other.

Here, the NG flag is a flag indicating whether or not it is determined that the operation of the virtual machine 110 is not normal when the physical machine 100 emulates the virtual machine 110. That is, when the NG flag indicates “1”, it indicates that the operation of the virtual machine 110 is not normal.
The selection flag is a flag indicating whether or not the virtual machine 110 is to be selected for activation. That is, when the selection flag indicates “1”, it indicates that the virtual machine 110 is a selection target for activation.
The resource threshold over flag is a flag indicating whether either the CPU usage rate or the memory usage rate sum exceeds a predetermined threshold value. That is, when the resource threshold value over flag indicates “1”, it indicates that either the CPU usage rate or the sum of the memory usage rates exceeds a predetermined threshold value.
The confirmation flag is a flag indicating whether or not the virtual machine 110 has been confirmed as an activation target. That is, when the confirmation flag indicates “1”, it can be seen that the physical machine 100 is confirmed to start the virtual machine 110.

Next, an outline of the operation of the server virtualization system 1 according to the present embodiment will be described.
FIG. 4 is a sequence diagram illustrating an outline of the operation of the server virtualization system 1.
When a resource shortage of a physical machine 100 (hereinafter referred to as a physical machine 100A) occurs, the transfer control unit 103 of the physical machine 100A executes a virtual machine program for emulating the virtual machine 110 being emulated by the own device. The data is transferred to another physical machine 100 (hereinafter referred to as physical machine 100B) (step S1). Next, the transfer control unit 103 of the physical machine 100B records the virtual machine program received from the physical machine 100A in the virtual machine storage unit 101 of the physical machine 100B. Next, the virtual machine control unit 102 of the physical machine 100B emulates the virtual machine 110 by executing the virtual machine program recorded in the virtual machine storage unit 101 of the physical machine 100B (step S2). When the virtual machine control unit 102 of the physical machine 100B starts emulating the virtual machine 110, the transfer notification unit 104 of the physical machine 100B issues a transfer notification to the normality confirmation server 200 (step S3). The notification of the transfer includes the name of the transferred virtual machine 110.

  When the notification receiving unit 202 of the normality confirmation server 200 receives the transfer notification from the physical machine 100B, the normality confirmation unit 203 refers to the virtual machine normality confirmation table stored in the table storage unit 201, and performs a normality confirmation procedure. Is specified (step S4). Next, the normality confirmation unit 203 accesses the virtual machine 110 transferred according to the identified normality confirmation procedure, and confirms the normality of the virtual machine 110 (step S5). Next, the normality confirmation unit 203 determines normality based on the access result to the virtual machine 110 (step S6). If the normality determination result is good, the normality confirmation unit 203 ends the process.

  On the other hand, when the normality determination result by the normality confirmation unit 203 is bad (OPT: normality failure), the resource status confirmation unit 204 refers to the physical machine resource state table stored in the storage unit, and the virtual machine A physical machine 100 (hereinafter referred to as a physical machine 100C) that activates the same virtual machine 110 as 110 is identified (step S7). Next, the virtual machine activation unit 205 transmits an activation command to activate the same virtual machine 110 as the transferred virtual machine 110 to the physical machine 100C (step S8).

  When the command receiving unit 105 of the physical machine 100C receives a startup command from the normality confirmation server 200, the virtual machine control unit 102 of the physical machine 100C loads a virtual machine 110 program for emulating the virtual machine 110 indicated by the startup command. By executing this, the virtual machine 110 is activated (step S9).

  By the above procedure, the server virtualization system 1 automatically checks the normality of the virtual machine 110 after the virtual machine 110 is moved. As a result, the time from the transfer of the virtual machine 110 to the confirmation of normality can be shortened. Further, according to the above procedure, the server virtualization system 1 can automatically start the virtual machine 110 and ensure the normality of the service when the normality confirmation fails. Thereby, since the downtime of the service is minimized, a highly available service can be provided to the user who uses the service.

Next, the operation of the normality confirmation server 200 according to this embodiment will be described in detail.
FIG. 5 is a flowchart illustrating the operation of the normality confirmation server 200 according to an embodiment.
When the notification reception unit 202 of the normality confirmation server 200 receives the notification of the transfer of the virtual machine 110 from the physical machine 100, the normality check unit 203 stores the physical machine resource stored in the table storage unit 201 based on the transfer notification. A record indicating the virtual machine 110 before the transfer is specified from the state table. Next, the normality confirmation unit 203 adds a mark indicating that the virtual machine 110 has been transferred to the virtual machine name of the identified record (step S101). For example, the normality confirmation unit 203 records in the physical machine resource state table that the virtual machine 110 has been transferred by adding an asterisk to the end of the virtual machine name.

  Next, the normality confirmation unit 203 adds a record indicating the virtual machine 110 after the transfer to the physical machine resource state table stored in the table storage unit 201 based on the transfer notification (step S102). For example, the normality confirmation unit 203 records, in the physical machine resource state table, a record in which the physical machine 100 that is the source of the transfer notification is associated with the virtual machine name included in the transfer notification. At this time, the normality confirmation unit 203 can use the same record as the record indicating the virtual machine 110 before the transfer as the same virtual machine name of the record.

  Next, the normality confirmation unit 203 reads the normality confirmation procedure associated with the virtual machine name included in the transfer notification from the virtual machine normality confirmation table stored in the table storage unit 201 (step S103). Next, the normality confirmation unit 203 accesses the virtual machine 110 based on the identified normality confirmation procedure, and performs normality confirmation (step S104).

  Next, when receiving the access result from the virtual machine 110, the normality confirmation unit 203 determines whether or not the normality confirmation result is good based on the access result (step S105). For example, when an HTTP access is performed as the normality confirmation procedure, the normality confirmation unit 203 performs the normality confirmation result when the HTTP (HyperText Transfer Protocol) status included in the access result indicates the 200th generation (success). Is determined to be good, and when the status indicates 400th generation (client error) or 500th generation (server error), it is determined that the result of the normality confirmation is bad.

  When the normality confirmation unit 203 determines that the result of the normality confirmation is good (step S105: YES), the normality confirmation unit 203 ends the process. On the other hand, when the normality confirmation unit 203 determines that the result of the normality confirmation is bad (step S105: NO), the normality confirmation unit 203 sets the NG flag of the record indicating the virtual machine 110 after the transfer of the physical machine resource state table to “1”. To “” (step S106).

  Next, the resource state confirmation unit collects the CPU usage rate and the memory usage rate from all the physical machines 100 (step S107). Next, the resource status confirmation unit records the collected CPU usage rate and memory usage rate in the physical machine resource status table (step S108). Next, the resource state confirmation unit rewrites the resource threshold value over flag of a record in which at least one of “CPU usage rate” and “memory usage rate” is equal to or greater than a predetermined threshold (for example, both 50%) to “1” ( Step S109) Next, the resource state confirmation unit includes a record stored in the physical machine resource state table that is not the transfer source, the NG flag is not “1”, and the resource threshold overflag is not “1”. Is determined (step S110).

  When it is determined that there is no record that is not the transfer source, the NG flag is not “1”, and the resource threshold over flag is not “1” (step S110: NO), the resource state confirmation unit is the same as the other physical machine 100 The process is terminated without starting the virtual machine 110. This is to prevent the performance of the entire system from deteriorating by further emulating the virtual machine 110 in the physical machine 100 having insufficient resources.

  On the other hand, when the resource state confirmation unit determines that there is a record whose CPU usage rate and memory usage rate are lower than the predetermined threshold among records that are not the transfer source and the NG flag is not “1” (step S110: YES). Then, the selection flag of the record is rewritten to “1” (step S111).

  Next, the resource state confirmation unit reads the same virtual machine name stored in the record indicating the virtual machine 110 after the transfer from the physical machine resource state table. Next, the resource state confirmation unit rewrites the selection flag other than the record included in the same virtual machine name of the virtual machine 110 after the virtual machine name is transferred to “0” among the records whose selection flag indicates “1”. (Step S112).

  Next, the resource status confirmation unit calculates a value obtained by adding the CPU usage rate and the memory usage rate for each record in which the selection flag indicates “1”, and rewrites the resource sum of the record. Next, the resource state confirmation unit identifies the record having the smallest resource sum among the records whose selection flag indicates “1”, and rewrites the confirmation flag of the record to “1” (step S113).

  Next, the virtual machine activation unit 205 activates the physical machine 100 indicated by the record indicating the confirmation flag “1” among the records stored in the physical machine resource state table to activate the virtual machine 110 indicated by the record. Is transmitted (step S114). When the virtual machine activation unit 205 transmits an activation instruction to the physical machine 100, the selection flag, the resource threshold over flag, the resource sum, and the confirmation flag are cleared from all records stored in the physical machine resource state table. Further, the virtual machine activation unit 205 deletes the record indicating the virtual machine 110 before the transfer (Step S115).

  According to the above procedure, the normality confirmation server 200 can automatically confirm the normality of the transferred virtual machine 110. Further, according to the above procedure, the normality confirmation server 200 can start the virtual machine 110 in an appropriate physical machine 100 when the normality confirmation fails.

As described above, the embodiment has been described in detail with reference to the drawings. However, the specific configuration is not limited to that described above, and various design changes and the like can be made.
For example, in the above-described embodiment, the case where the normality confirmation unit 203 determines whether or not the access has been successful as the normality confirmation method has been described, but the present invention is not limited thereto. For example, in another embodiment, the normality confirmation unit 203 may determine that the response is not normal when the response time exceeds a predetermined threshold even if the access is successful.

  Further, for example, in the above-described embodiment, the case where the resource state confirmation unit determines the physical machine 100 that starts the virtual machine 110 based on the CPU usage rate and the memory usage rate in step S113 has been described. Not limited to. For example, in another embodiment, a bandwidth with a physical server provided with another virtual machine 110 (for example, a database) with which the virtual machine 110 communicates, or the other machine is provided in the same data center 300. The physical machine 100 that activates the virtual machine 110 may be determined based on whether or not it has been set.

  In the above-described embodiment, the case where the virtual machine 110 is transferred in response to a shortage of resources of the physical machine 100 has been described. However, the present invention is not limited to this. For example, in another embodiment, the physical machine 100 may transfer the virtual machine 110 when the usage rate decreases. That is, when the usage rate of the physical machine 100 decreases, the virtual machine 110 is automatically transferred to the physical machine 100 that has free resources, and the physical machine 100 in which the virtual machine 110 is not operating is turned off and consumed. The server virtualization system 1 according to the present invention may be applied to a distributed power management system that suppresses power.

  In the above-described embodiment, the case where the physical machine to which the virtual machine is transferred issues a transfer notification has been described. However, the present invention is not limited to this. For example, in another embodiment, a physical machine that is a transfer source of a virtual machine may issue a transfer notification. In this case, the notification of the transfer includes the virtual machine name and the name of the transfer destination physical machine.

FIG. 6 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment.
The computer 900 includes a CPU 901, a main storage device 902, an auxiliary storage device 903, and an interface 904.
The normality confirmation server 200 and each physical machine 100 described above are mounted on a computer 900, respectively. The operation of each processing unit described above is stored in the auxiliary storage device 903 in the form of a program. The CPU 901 reads a program from the auxiliary storage device 903, develops it in the main storage device 902, and executes the above processing according to the program. Further, the CPU 901 secures a storage area corresponding to each of the above-described storage units in the main storage device 902 according to the program.

  In at least one embodiment, the auxiliary storage device 903 is an example of a tangible medium that is not temporary. Other examples of the tangible medium that is not temporary include a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, and a semiconductor memory connected via the interface 904. When this program is distributed to the computer 900 via a communication line, the computer 900 that has received the distribution may develop the program in the main storage device 902 and execute the above processing.

  The program may be for realizing a part of the functions described above. Further, the program may be a so-called difference file (difference program) that realizes the above-described function in combination with another program already stored in the auxiliary storage device 903.

  DESCRIPTION OF SYMBOLS 1 ... Server virtualization system 100 ... Physical machine 101 ... Virtual machine memory | storage part 102 ... Virtual machine control part 103 ... Transfer control part 104 ... Transfer notification part 105 ... Command receiving part 110 ... Virtual machine 200 ... Normality confirmation server 201 ... Table Storage unit 202 ... Notification receiving unit 203 ... Normality confirmation unit 204 ... Resource status confirmation unit 205 ... Virtual machine activation unit 300 ... Data center

Claims (6)

A notification receiving unit that receives a notification indicating that the virtual machine has been moved from a physical machine that emulates the virtual machine;
A normality confirmation unit for confirming the normality of the transferred virtual machine when the notification reception unit receives the notification ;
When the normality confirmation unit determines that the transferred virtual machine is normal, the redundant configuration of the virtual machine is added to the physical machine other than the physical machine before the transfer and the physical machine after the transfer. A virtual machine management device comprising: a virtual machine activation unit that activates the same virtual machine . The virtual machine activation unit is configured to activate the same virtual machine based on at least one of a CPU usage rate or a memory usage rate from among the physical machine before the transfer and the physical machine other than the physical machine after the transfer. Determine the machine
The virtual machine management apparatus according to claim 1 . A program for emulating the same virtual machine is stored in the plurality of physical machines,
The virtual machine activation unit determines the physical machine that stores a program for emulating the same virtual machine that is a redundant configuration of the transferred virtual machine as a physical machine that activates the same virtual machine. The virtual machine management apparatus according to claim 1 or 2 . A plurality of physical machines that emulate a virtual machine, and a virtual machine management device that manages the plurality of physical machines,
The physical machine is
A transfer notification unit for issuing a notification indicating that the virtual machine has been transferred when the virtual machine is transferred;
The virtual machine management device is:
A notification receiving unit for receiving a notification indicating that the virtual machine has been moved from the physical machine;
A normality confirmation unit for confirming the normality of the transferred virtual machine when the notification reception unit receives the notification;
When the normality confirmation unit determines that the transferred virtual machine is normal, the redundant configuration of the virtual machine is added to the physical machine other than the physical machine before the transfer and the physical machine after the transfer. A server virtualization system comprising: a virtual machine activation unit that activates the same virtual machine . A notification receiving unit of the virtual machine management device receiving a notification indicating that the virtual machine has been transferred from a physical machine emulating the virtual machine;
When the notification receiving unit receives the notification, the normality confirmation unit of the virtual machine management device confirms the normality of the transferred virtual machine ;
When the normality confirmation unit determines that the normality of the transferred virtual machine is bad, the virtual machine activation unit of the virtual machine management device uses the physical machine before transfer and the physical machine after transfer A virtual machine management method including: causing a physical machine other than the above to start the same virtual machine that is a redundant configuration of the virtual machine . Computer
A notification receiving unit that receives a notification indicating that the virtual machine has been moved from a physical machine that emulates the virtual machine;
A normality confirmation unit for confirming the normality of the transferred virtual machine when the notification reception unit receives the notification ;
When the normality confirmation unit determines that the transferred virtual machine is normal, the redundant configuration of the virtual machine is added to the physical machine other than the physical machine before the transfer and the physical machine after the transfer. The program for functioning as a virtual machine starting part which starts the same virtual machine .

Images