Information processing device, management program, and management method

Abstract

To properly perform shutdown of a virtualized system.SOLUTION: A control unit of an information processing device includes a first management unit that manages shutdown of a plurality of guest OSs running on a virtual OS, and a controller unit that displays a stop priority setting screen that allows a user to set the stop priority indicating the order in which the guest OSs are shut down. The first management unit executes the shutdown of the plurality of guest OSs according to the stop priority. The controller unit acquires stop status of the plurality of guest OSs and generates screen data for displaying a progress chart of the shutdown of the plurality of guest OSs in the stop priority setting screen.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a management program, and a management method. [Background technology]

[0002] A virtualization system is known as a conventional technology. For example, Patent Document 1 discloses that a control device including one or more processors realizes a virtualization environment in which multiple operating systems can be executed independently of each other using common hardware resources. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-187992 [Patent Document 2] Patent No. 5664004 [Patent Document 3] Patent No. 6029165 [Patent Document 4] Patent No. 5206750 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when shutting down a virtualization system, the next process (such as shutting down other guest OSes) is performed according to the set time without checking whether the guest OSes are in a shutdown state (see, for example, Patent Documents 2 and 3).

[0005] This caused problems during verification when building a system, such as being unable to confirm that the guest OS had shut down and not being able to perform the next process until the set time had elapsed, resulting in wasted time during verification. Also, if the guest OS took longer to shut down than expected, the guest OS would not shut down normally.

[0006] In addition, when the set time had elapsed, the guest OS shutdown was considered complete, and the virtual OS (hypervisor), virtual storage, etc. were unbound.

[0007] Patent Document 4 discloses a configuration in which a power supply device supplies power to a virtual host computer via a tap.

[0008] One aspect of the present invention aims to properly shut down a virtualization system. [Means for solving the problem]

[0009] In order to solve the above problem, an information processing device according to one embodiment of the present invention is an information processing device having a control unit, the control unit having a first management unit that manages the shutdown of multiple guest OSs running on a virtual OS, and a second management unit that shuts down the information processing device when all of the multiple guest OSs have been shut down by the first management unit, and when the first management unit obtains information that the shutdown of a guest OS among the multiple guest OSs has been completed, it shuts down guest OSs other than the guest OS.

[0010] According to the above configuration, when the shutdown of one of the multiple guest OSes running on the virtual OS is completed, the shutdown of the other guest OSes is executed, and when all of the multiple guest OSes have been shut down, the information processing device is shut down, so that the virtualization system can be shut down appropriately.

[0011] In an information processing device according to one embodiment of the present invention, the control unit may include a third management unit that monitors the status of the multiple guest OSs and controls the multiple guest OSs, and the first management unit may obtain status information of each of the multiple guest OSs via the third management unit and perform shutdown of the multiple guest OSs via the third management unit.

[0012] According to the above configuration, the status information of each of the multiple guest OSs is acquired and the multiple guest OSs are shut down, so that the multiple guest OSs can be shut down appropriately.

[0013] In an information processing device according to one embodiment of the present invention, when all of the plurality of guest OSes are shut down by the first management unit, the second management unit may shut down the information processing device via a control device that controls the information processing device and an uninterruptible power supply connected to the information processing device.

[0014] According to the above configuration, the information processing device can be shut down appropriately via the control device that controls the information processing device and the uninterruptible power supply device connected to the information processing device.

[0015] The information processing apparatus according to an aspect of the present invention may have a test mode in which the plurality of guest OSs are shut down in a predetermined order.

[0016] According to the above configuration, since the test mode is provided in which a plurality of guest OSs are shut down in a predetermined order, it is possible to test shutting down the guest OSs in various orders.

[0017] The information processing device according to an aspect of the present invention may further include a display control unit that generates screen data for displaying the shutdown time of each guest OS in the test mode.

[0018] According to the above configuration, the shutdown time of each guest OS in test mode is displayed, so that the appropriate order for shutting down the guest OSs can be considered.

[0019] In the information processing device according to an aspect of the present invention, the screen data may further include a cumulative total of shutdown times of each guest OS, a success or failure of shutdown of each guest OS, and a time limit for the cumulative total.

[0020] According to the above configuration, the cumulative shutdown time of each guest OS in test mode, the success or failure of the shutdown of each guest OS, and the time limit for the cumulative shutdown time are further displayed, thereby enabling a more appropriate order for shutting down the guest OSs to be considered.

[0021] A management program according to one embodiment of the present invention is a management program executed on a virtual OS executed on one or more information processing devices, and executes a first management step of managing the shutdown of multiple guest OSes running on the virtual OS, and a second management step of shutting down the one or more information processing devices when all of the multiple guest OSes have been shut down by the first management step, and in the first management step, when information is obtained that the shutdown of a guest OS among the multiple guest OSes has been completed, the program shuts down guest OSes other than the guest OS.

[0022] A management method according to one aspect of the present invention is a management method executed on one or more information processing devices, and includes a first management step of managing the shutdown of multiple guest OSs running on the virtual OS, and a second management step of shutting down the one or more information processing devices when all of the multiple guest OSs have been shut down by the first management step, wherein in the first management step, when information is obtained that the shutdown of a guest OS among the multiple guest OSs has been completed, the method shuts down guest OSs other than the guest OS.

[0023] An information processing system according to one embodiment of the present invention is an information processing system comprising an information processing device, an uninterruptible power supply, and a control device, wherein the information processing device comprises a control unit, and the control unit comprises a first management unit that manages the shutdown of multiple guest OSs running on a virtual OS, and a second management unit that shuts down the information processing device when all of the multiple guest OSs have been shut down by the first management unit, and when the first management unit obtains information that the shutdown of a guest OS among the multiple guest OSs has been completed, it shuts down guest OSs other than the guest OS, the uninterruptible power supply is connected to the information processing device, and the control device controls the information processing device and the uninterruptible power supply.

[0024] An information processing system according to one embodiment of the present invention is an information processing system having a plurality of information processing devices, each of which has a control unit, and the control unit of at least one of the information processing devices has a first management unit that manages the shutdown of a plurality of guest OSes running on a virtual OS, and a second management unit that shuts down the information processing device when all of the plurality of guest OSes have been shut down by the first management unit, and when the first management unit obtains information that the shutdown of a certain guest OS among the plurality of guest OSes has been completed, it shuts down guest OSes other than the certain guest OS.

[0025] The information processing device according to each aspect of the present invention may be realized by a computer. In this case, the control program of the information processing device that causes the computer to operate as each part (software element) of the information processing device to realize the information processing device on the computer, and the computer-readable recording medium on which the control program is recorded, also fall within the scope of the present invention. [Effects of the Invention]

[0026] According to one aspect of the present invention, it is possible to properly shut down a virtualization system. [Brief explanation of the drawings]

[0027] [Figure 1] 1 is a diagram showing a configuration of an information processing system according to a first embodiment of the present invention. [Figure 2] FIG. 1 is a diagram showing an overview of virtual software according to a first embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing a detailed configuration of virtual software and its peripheral configuration according to the first embodiment of the present invention. [Figure 4] 1 is a block diagram showing the configuration of a UPS according to a first embodiment of the present invention. [Figure 5] 1 is a block diagram showing the configuration of a network card according to a first embodiment of the present invention. [Figure 6] 5 is a flowchart showing processing by a server according to the first embodiment of the present invention. [Figure 7] 5 is a flowchart showing the processing of the network card according to the first embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing a display screen of a node list according to the second embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing a display screen of the shutdown time of each virtual machine in a shutdown test according to the second embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing a screen for setting the timeout period of each node according to the second embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing an execution screen of a startup test according to the second embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing a startup priority setting screen according to the second embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing a setting screen related to a UPS according to the second embodiment of the present invention. [Figure 14] FIG. 10 is a diagram showing a setting screen relating to management software according to the second embodiment of the present invention. [Figure 15] FIG. 10 is a diagram showing a script management screen according to the second embodiment of the present invention. [Figure 16] FIG. 10 is a diagram showing a basic setting screen according to the second embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0028] [Embodiment 1] An embodiment according to one aspect of the present invention (hereinafter also referred to as "the present embodiment") will be described below with reference to FIGS. 1 to 7. Note that identical or corresponding parts in the drawings are given the same reference numerals and their description will not be repeated. In this embodiment, for example, an information processing system 100 will be described as a typical example of a virtualization system. To facilitate understanding of the server 1 according to one aspect of the present invention, an overview of the information processing system 100 will first be described using FIG. 1.

[0029] §1. Application Examples (Configuration of information processing system 100) 1 is a diagram showing the configuration of an information processing system 100 according to this embodiment. As shown in Fig. 1, the information processing system 100 is a virtualization system including a server 1, an uninterruptible power supply (UPS) 2, and a network card 3.

[0030] The server 1 is an information processing device, and in FIG. 1, three servers 1a, 1b, and 1c are shown, but there is no limit to the number. The UPS 2 is an uninterruptible power supply, and in FIG. 1, two servers 2a and 2b are shown, but there is no limit to the number. The network card 3 is a control device that controls the server 1 and the UPS 2, and in FIG. 1, two servers 3a and 3b are shown, but there is no limit to the number.

[0031] Servers 1a, 1b, and 1c are connected to UPSs 2a and 2b via power cables C1 and receive power. Servers 1a, 1b, and 1c are connected to each other via network cables C2 so that they can communicate with each other. Servers 1a, 1b, and 1c are also connected to network cards 3a and 3b via network cables C2 so that they can communicate with each other. Network card 3a is inserted into a slot on the back of UPS 2a. Network card 3b is inserted into a slot on the back of UPS 2b.

[0032] §2. Configuration example (Server 1 configuration) 1, server 1a includes control unit 10a, and software executed by control unit 10a includes hypervisor 11, virtualization software 12, management software 13, and virtual machine 14. Servers 1b and 1c include control units 10b and 10c, respectively, and software executed by control units 10b and 10c includes hypervisor 11 and virtual machine 14. Note that control unit 10a of server 1a may not necessarily include virtual machine 14.

[0033] The hypervisor 11 is a virtual OS that comprehensively manages other software on each server, such as AHV by Nutanix (registered trademark) or ESXi by VMware (registered trademark). The virtualization software 12 is software that controls the shutdown of the server 1. The management software 13 is software that communicates with virtual machines 14 on each server and monitors the status of the virtual machines 14, such as Prism by Nutanix or vCSA by VMware. The virtual machines 14 are guest OSs, such as Linux (registered trademark) or Windows (registered trademark).

[0034] The virtualization software 12, management software 13, and virtual machine 14 operate under the management of the hypervisor 11. The virtualization software 12 obtains the status of the virtual machine 14 using the API (Application Programming Interface) of the management software 13, and instructs the virtual machine 14 to shut down.

[0035] (Virtual Software 12 Configuration) 1, the control unit 10a includes, as the virtualization software 12, a basic service unit (first management unit) 122 that manages the shutdown of multiple virtual machines 14 running on the hypervisor 11, and a network card service unit (second management unit) 121 that shuts down the server 1a when all of the multiple virtual machines 14 have been shut down by the basic service unit 122. When the basic service unit 122 acquires information that the shutdown of a certain virtual machine 14 among the multiple virtual machines 14 has been completed, the basic service unit 122 executes the shutdown of the virtual machines 14 other than the certain virtual machine 14.

[0036] FIG. 2 is a diagram showing an overview of the virtualization software 12 according to this embodiment. The virtualization software 12 generates a user interface screen and displays it on a display. The user interface screen displays the content shown in FIG. 2, allowing the user to refer to the current state. That is, the user interface screen displays, for example, the state of the UPS 2, control of the UPS 2 (such as redundancy control), notification to the UPS 2 (such as stopping a virtual machine), communication with the hypervisor 11, the state of the virtual machine 14 via the hypervisor 11, stopping the virtual machine 14 via the hypervisor 11, shutdown control of the virtual machine 14 (priority, group, exception handling), shutdown processing of the virtualization software 12, email notification, and user interface screen control (setting, update, save).

[0037] The virtual software 12 runs using Free BSD, web services (Apache, Apache Tomcat), etc.

[0038] 3 is a diagram showing the detailed configuration of the virtualization software 12 according to this embodiment and the peripheral configuration. As shown in FIG. 3, the virtualization software 12, the network card service unit (daemon) 151, and the Apache 152 run on FreeBSD 15.

[0039] The virtual software 12 includes a network card service unit 121, a basic service unit 122, an email sending unit 123, a stop status memory unit 124, a controller unit 125, a view unit 126, a Nutanix service unit 127, and a VMware service unit 128.

[0040] The network card service unit 121 communicates with the network card 3. The network card service unit 121 includes a network card status acquisition unit 1211, a network card event acquisition unit 1212, a UPS redundancy control unit 1213, and a virtual machine stop notification unit 1214.

[0041] The network card status acquisition unit 1211 acquires the status of the UPS 2 and the status of the battery from the network card 3 via CGI (Common Gateway Interface). The network card event acquisition unit 1212 acquires a shutdown start event from the network card 3 via the network card service unit (daemon) 151. The UPS redundancy control unit 1213 controls the redundancy of the UPS 2 to which the server 1 is connected. The virtual machine stop notification unit 1214 receives a notification (virtual machine stop notification) that the virtual machine 14 has stopped from the basic service unit 122. Then, the virtual machine stop notification unit 1214 transmits the virtual machine stop notification to the network card 3 via the network card service unit (daemon) 151.

[0042] The basic service unit 122 includes a stop control unit 1221 and a self-stop unit 1222. The stop control unit 1221 includes a priority control unit 12211, a group control unit 12212, and a timeout control unit 12213. The stop control unit 1221 instructs Prism 131, which is one of the management software 13, to stop the virtual machine 14 and disable the virtualization configuration via the Nutanix service unit 127. The stop control unit 1221 also instructs vCSA 132, which is one of the management software 13, to stop the virtual machine 14 and disable the virtualization configuration via the VMware service unit 128.

[0043] The self-shutdown unit 1222 shuts down FreeBSD15.

[0044] The email sending unit 123 acquires the shutdown status of the virtual machine 14 from the basic service unit 122 as necessary, and sends the user an email including the shutdown status of the virtual machine 14. The shutdown status storage unit 124 acquires and stores the shutdown status of the virtual machine 14 from the basic service unit 122. The controller unit 125 acquires the shutdown status of the virtual machine 14 from the shutdown status storage unit 124, and displays a progress chart on the shutdown priority setting screen 16 via the view unit 126 and Apache 152, or via Apache 152.

[0045] (Virtual Software 12 and Management Software 13) The management software (third management unit) 13 of the control unit 10a monitors the status of the multiple virtual machines 14 and controls the multiple virtual machines 14. The basic service unit 122 of the virtualization software 12 acquires status information of each of the multiple virtual machines 14 via the management software 13 and executes shutdown of the multiple virtual machines 14 via the management software 13.

[0046] In addition, when all of the multiple virtual machines 14 are shut down by the basic service unit 122, the network card service unit 121 of the virtual software 12 shuts down the server 1 via the network card 3 that controls the server 1 and the UPS 2 connected to the server 1.

[0047] (UPS2 configuration) 4 is a block diagram showing the configuration of the UPS 2 according to this embodiment. As shown in FIG. 4, the UPS 2 includes a power supply unit 61, a control unit 62, a monitoring unit 63, and a communication unit 64.

[0048] When the power from the commercial power supply 4 is normal, the power supply unit 61 receives power from the commercial power supply 4 and supplies the power to the server 1. When the power from the commercial power supply 4 is abnormal or not being supplied, the power supply unit 61 supplies power to the server 1 from an internal battery 75. The power supply unit 61 switches the power source (commercial power supply 4 or battery 75) that supplies power to the server 1 in response to an instruction from the control unit 62.

[0049] The control unit 62 controls the opening and closing of the input relay 72 and output relay 76 of the power supply unit 61 and the switching of the output switch 79 in response to instructions from the monitoring unit 63 and the communication unit 64. The monitoring unit 63 monitors the status of the noise filter 71 of the power supply unit 61 and transmits the monitoring result indicating whether the power from the commercial power source 4 is normal or not to the control unit 62 and the communication unit 64. The communication unit 64 transmits the monitoring result from the monitoring unit 63 to the server 1. In addition, the communication unit 64 instructs the control unit 62 to switch the power source in response to instructions from the server 1.

[0050] (Configuration of power supply unit 61) As shown in FIG. 4, the power supply unit 61 includes a noise filter 71, an input relay 72, a power line 73, a converter 74, a battery 75, an output relay 76, an inverter 77, a power line 78, an output switch 79, and a noise filter 80.

[0051] During normal operation, under the control of the control unit 62, the input relay 72 is closed, the output relay 76 is opened, and the output switch 79 is switched to the power line 73 side. In this case, power from the commercial power supply 4 is supplied to the server 1 via the noise filter 71, the input relay 72, the power line 73, the output switch 79, and the noise filter 80. The power from the commercial power supply 4 also passes through the noise filter 71, the input relay 72, and the converter 74 to charge the battery 75.

[0052] In the backup operation, under the control of the control unit 62, the input relay 72 opens, the output relay 76 closes, and the output switch 79 switches to the power line 78 side. In this case, power from the battery 75 is supplied to the server 1 via the output relay 76, inverter 77, power line 78, output switch 79, and noise filter 80. Note that power from the commercial power source 4 is not supplied to the server 1.

[0053] In the event of an abnormality in converter 74, inverter 77, or the like within power supply unit 61, control unit 62 closes input relay 72, opens output relay 76, and switches output switch 79 to the power line 73 side. In this case, power from commercial power supply 4 is supplied to server 1 via noise filter 71, input relay 72, power line 73, output switch 79, and noise filter 80. Note that power from commercial power supply 4 is not used to charge battery 75.

[0054] (Network card 3 configuration) FIG. 5 is a block diagram showing the configuration of the network card 3 according to this embodiment. As shown in FIG. 5, the network card 3 includes a control unit 31, a UPS communication unit 32, a network communication unit 33, a monitoring unit 34, and a storage unit 35. The control unit 31 controls the overall operation of the network card 3. The UPS communication unit 32 communicates with the UPS 2 via a slot in the UPS 2. The network communication unit 33 communicates with the server 1 via a network cable C2, and is, for example, a network USB. The monitoring unit 34 monitors time during shutdown processing. The storage unit 35 stores and reads data in response to instructions from the control unit 31, and is, for example, an HDD or SSD.

[0055] (Server 1 processing) Fig. 6 is a flowchart showing the processing of the server 1 according to this embodiment. Fig. 6 particularly shows the processing of the virtual software 12 in the control unit 10a of the server 1a. The processing of the virtual software 12 will be described below with reference to Fig. 6.

[0056] (Step S601) In the server 1a, the virtualization software 12 acquires information about the management software 13 (for example, information about the API).

[0057] (Step S602) The virtualization software 12 acquires the operation status (whether the virtual machine 14 is running or not) of the virtual machine 14 through the API of the management software 13. In this case, the management software 13 acquires the operation status of the virtual machine 14 in the server 1a, and also acquires the operation status of the virtual machines 14 in the servers 1b and 1c via the network cable C2. The management software 13 then passes the acquired operation status of the virtual machine 14 to the virtualization software 12.

[0058] (Step S603) The virtualization software 12 acquires the status of the UPS 2a and 2b through the API of the management software 13. In this case, the management software 13 instructs the network cards 3a and 3b to notify the status of the UPS 2a and 2b, respectively, via the network cable C2. The management software 13 then passes the acquired status of the UPS 2a and 2b to the virtualization software 12.

[0059] (Step S604) The virtualization software 12 determines whether or not shutdown is necessary by referring to the operating state of the virtual machine 14 acquired in step S602 and the states of the UPSs 2a and 2b acquired in step S603. For example, if there is a running virtual machine 14 and both the UPSs 2a and 2b are in backup operation, shutdown is necessary.

[0060] If shutdown is necessary (YES in step S604), the virtual software 12 executes the process of step S605. If shutdown is not necessary (NO in step S604), the virtual software 12 executes the process of step S601 again.

[0061] (Step S605: First Management Step) The virtualization software 12 executes a shutdown of a certain virtual machine 14 that is currently running via the management software 13 (that is, by using the API of the management software 13).

[0062] (Step S606) The virtualization software 12 checks whether the operation of the virtual machine 14 that executed the shutdown has stopped via the management software 13. If the operation of the virtual machine 14 has stopped (YES in step S606), the virtualization software 12 executes the determination in step S609. If the operation of the virtual machine 14 has not stopped (NO in step S606), the virtualization software 12 executes the determination in step S607.

[0063] (Step S607) The virtual software 12 determines whether or not to perform exception processing (for example, time monitoring timeout processing). If exception processing is to be performed (YES in step S607), the virtual software 12 executes the determination in step S608. If exception processing is not to be performed (NO in step S607), the virtual software 12 executes the determination in step S606 again.

[0064] (Step S608) The virtualization software 12 executes a forced shutdown process for the virtual machine 14 via the management software 13. Then, the virtualization software 12 executes the determination in step S609.

[0065] (Step S609) The virtualization software 12 determines whether or not another virtual machine 14 is running via the management software 13. If another virtual machine 14 is running (YES in step S609), the virtualization software 12 executes the process of step S605 again. If another virtual machine 14 is not running (NO in step S609), the virtualization software 12 executes the process of step S610.

[0066] (Step S610: Second Management Step) The virtualization software 12 notifies the network cards 3a and 3b of the stoppage of operation of all virtual machines via the management software 13. As a result, the server 1 is shut down.

[0067] (Network card 3 processing) Fig. 7 is a flowchart showing the processing of the network card 3 according to this embodiment. The processing of the network card 3 will be described below with reference to Fig. 7. This processing is performed by the control unit 31 when the network communication unit 33 of the network card 3 receives a notification from the virtualization software 12 that the operation of all virtual machines has been stopped.

[0068] (Step S701) The control unit 31 of the network card 3 executes the shutdown of the virtual software 12 via the network communication unit 33 and the network cable C2.

[0069] (Step S702) The control unit 31 executes the shutdown of the management software 13 via the network communication unit 33 and the network cable C2.

[0070] (Step S703) The control unit 31 releases the connection of the virtual storage via the network communication unit 33 and the network cable C2. The virtual storage is a virtual storage device that is configured (logically connected) from multiple physical storage devices (HDDs (Hard Disk Drives), SSDs (Solid State Drives), etc.) in one or more servers 1. By releasing the connection of the virtual storage, it becomes possible to shut down the power to each physical storage device.

[0071] Furthermore, the physical storage devices that make up the virtual storage do not necessarily have to be built into or connected to server 1, but may be NAS (Network Attached Storage) that is directly connected to network cable C2 and shared by multiple servers 1 via network cable C2, or may be a mixture of storage devices under server 1 and NAS.

[0072] (Step S704) The control unit 31 executes the shutdown of the hypervisor 11 via the network communication unit 33 and the network cable C2.

[0073] (Step S705) The control unit 31 executes shutdown of the UPS 2 via the UPS communication unit 32 .

[0074] (Effects of the First Embodiment) According to this embodiment, instead of performing the next process according to a set time, the shutdown state of the virtual machine 14 is grasped and the next process is performed, thereby making it possible to appropriately shut down the information processing system 100, which is a virtualization system. Furthermore, if the next process cannot be performed for some reason, a timeout process is used to forcibly shut down the information processing system 100, and the next process is performed, thereby shutting down the information processing system 100. Furthermore, by notifying the network card 3 that all the virtual machines 14 have been shut down, it is possible to immediately execute scripts for shutting down the hypervisor 11, which is a virtual OS, unbinding virtual storage, and the like.

[0075] [Embodiment 2] A second embodiment of the present invention will be described below. For ease of explanation, the same reference numerals will be used to designate components having the same functions as those described in the first embodiment, and the description thereof will not be repeated.

[0076] In this embodiment, a screen managed by the virtualization software 12 and displayed on a display of the server 1, a remote terminal (not shown), or the like will be described.

[0077] 8 is a diagram showing a display screen of a node list according to this embodiment. As shown in Fig. 8, the node list shows the status of the server 1, the UPS 2, the network card 3, the virtual machine 14, and the like.

[0078] The server 1 may have a test mode in which a plurality of virtual machines (guest OSs) 14 are shut down in a predetermined order. In this case, upon receiving an instruction to start the test mode through a user operation, the control unit 10 of the server 1 executes the test mode.

[0079] In the test mode, the control unit 10 executes a shutdown priority acquisition process to acquire a shutdown priority indicating the order in which each node is to be shut down, a node shutdown process to stop each node in sequence according to the acquired shutdown priority, and a shutdown time display process to display the time from the shutdown instruction time to the shutdown completion report to each node as the shutdown time.

[0080] FIG. 9 is a diagram showing a display screen showing the shutdown time of each virtual machine 14 in a shutdown test according to this embodiment.

[0081] The server 1 may further include a controller unit (display control unit) 125 that generates screen data for displaying the shutdown time of each virtual machine 14 in the test mode.

[0082] As shown in FIG. 9, the above screen data may further include an estimated shutdown time (cumulative time) for each virtual machine 14, whether the shutdown of each virtual machine 14 was successful, and a maximum time (time limit for the cumulative time).

[0083] The estimated time is the total shutdown time estimated by the server 1 executing the test mode from the time when the server 1 issues a shutdown instruction to the virtual machines 14 to the time when the server 1 reports completion of the shutdown of the virtual machines 14. The maximum time is the time during which power can be supplied by the battery 75 in the case of backup operation. If the estimated time is within the maximum time, the shutdown of all virtual machines 14 will be completed within the time during which power can be supplied by the battery 75, and therefore there can be said to be no problem.

[0084] When the shutdown of the virtual machine 14 is completed normally, the display control unit generates screen data including, for example, a black band corresponding to the virtual machine 14. When the shutdown of the virtual machine 14 is completed abnormally, the display control unit generates screen data including, for example, a red band corresponding to the virtual machine 14.

[0085] 10 is a diagram showing a screen for setting the timeout time for each node according to this embodiment. As shown in Fig. 10, the screen for setting the timeout time allows adding necessary nodes and setting the timeout time.

[0086] FIG. 11 is a diagram showing a startup test execution screen according to this embodiment. As shown in FIG. 11, the startup test execution screen shows the startup order of each node and the startup time of each node. The server 1 may perform startup tests on multiple virtual machines (guest OSs) 14 in a predetermined order. In this case, upon receiving an instruction to start the startup test through a user operation, the control unit 10 of the server 1 executes the startup test. The startup test is performed after the test mode so that the user can confirm that each node has started up normally.

[0087] In the startup test, the control unit 10 executes a startup priority acquisition process to acquire a startup priority indicating the order in which each node is to be started, a node startup process to start each node in sequence according to the acquired startup priority, and a startup time display process to display the time from the startup instruction time to the startup completion report to each node as the startup time.

[0088] Fig. 12 is a diagram showing a startup priority setting screen according to this embodiment. As shown in Fig. 12, on the startup priority setting screen, the user can change the startup priority of each node by operating the up and down buttons.

[0089] When a user wants to change the startup priority of each node, the user operates the server 1 to instruct the display of a startup priority setting screen. Upon receiving the instruction to display the startup priority setting screen, the control unit 10 of the server 1 displays the startup priority setting screen on the display of the server 1. Then, when the startup priority is changed on the setting screen by the user's operation, the control unit 10 stores the changed startup priority in a storage unit (not shown). Separately, upon receiving an instruction to start the information processing system 100, the control unit 10 reads the startup priority from the storage unit and starts up each node according to the startup priority.

[0090] Fig. 13 is a diagram showing a setting screen for the UPS 2 according to this embodiment. As shown in Fig. 13, on the setting screen for the UPS 2, it is possible to set an operation action, a standby time, a stop time, and stop conditions for an input power supply abnormality.

[0091] Fig. 14 is a diagram showing a setting screen for the management software 13 according to this embodiment. As shown in Fig. 14, on the setting screen for the management software 13, it is possible to set Prism, which is one of the management software 13, and the IP address / host name, user ID, password, etc. of the server 1 to which Prism connects.

[0092] 15 is a diagram showing a script management screen according to this embodiment. As shown in Fig. 15, on the script management screen, the IP addresses / host names of scripts executed by the network card 3 can be managed.

[0093] Fig. 16 is a diagram showing a basic setting screen according to this embodiment. As shown in Fig. 16, on the basic setting screen, the network card 3, the UPS 2, the management software 13, the stop priority and the start priority of each node can be set in order, and the settings can be confirmed.

[0094] [Software implementation example] The control block of the server 1 (particularly, the control unit 10) may be realized by a logic circuit (hardware) formed on an integrated circuit (IC chip) or the like, or may be realized by software.

[0095] In the latter case, the server 1 includes a computer that executes instructions from a program, which is software that realizes each function. This computer includes, for example, one or more processors and a computer-readable recording medium storing the program. The object of the present invention is achieved when the processor in the computer reads and executes the program from the recording medium. The processor may be, for example, a CPU (Central Processing Unit). The recording medium may be a "non-transitory tangible medium," such as a ROM (Read Only Memory), a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The server may also include a RAM (Random Access Memory) for loading the program. The program may be supplied to the computer via any transmission medium capable of transmitting the program (such as a communication network or broadcast waves). One aspect of the present invention may also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.

[0096] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of symbols]

[0097] 1, 1a, 1b, 1c Server (information processing device) 2, 2a, 2b UPS (uninterruptible power supply) 10, 10a Control section 3, 3a, 3b Network card (control device) 11 Hypervisor (Virtual OS) 12 Virtual Machines 13 Management software (third management department) 14 Virtual Machine (Guest OS) 121 Network Card Service Department (Second Management Department) 122 Basic Services Department (First Management Department) 125 Controller unit (display control unit)

Claims

1. An information processing device including a control unit, The control unit a first management unit that executes shutdown of a plurality of guest OSs; a controller unit that acquires shutdown statuses of the plurality of guest OSs and generates screen data for displaying a shutdown progress chart of the plurality of guest OSs; the controller unit displays a progress chart of the shutdown of the plurality of guest OSs as a Gantt chart according to the length of the shutdown time of each guest OS; Information processing device.

2. the controller unit displays a shutdown priority setting screen for allowing a user to set a shutdown priority indicating an order for shutting down the plurality of guest OSs; displaying the progress chart on the stop priority setting screen; The information processing device according to claim 1 .

3. The screen data further includes a shutdown time of each guest OS.

3. The information processing device according to claim 1 or 2.

4. The screen data further includes at least one of the following: a cumulative total time of shutdown times of each guest OS, a success or failure of shutdown of each guest OS, and a maximum time of shutdown times of each guest OS. The information processing device according to claim 1 .

5. the information processing apparatus has a shutdown test mode for shutting down a plurality of guest OSs in a predetermined order; the controller unit, in the shutdown test mode, before shutting down the plurality of guest OSs, displays a shutdown test execution screen indicating the order in which the plurality of guest OSs will be shut down and the shutdown time of each guest OS. The information processing device according to claim 1 .

6. the controller unit acquires the stop status of the plurality of guest OSs, and displays in the Gantt chart a band corresponding to a guest OS that has terminated normally and a band corresponding to a guest OS that has terminated abnormally in different colors. The information processing device according to claim 1 .

7. An information processing device including a control unit, The control unit a first management unit that executes the startup of a plurality of guest OSs; a controller unit that acquires the startup status of the plurality of guest OSs and generates screen data for displaying a startup progress chart of the plurality of guest OSs. Information processing device.

8. The controller unit displaying a boot priority setting screen for a user to set boot priorities indicating an order in which the plurality of guest OSs are to be booted; displaying the progress chart on the startup priority setting screen; The information processing device according to claim 6 .

9. The screen data further includes the boot time of each guest OS.

8. The information processing device according to claim 6 or 7.

10. The screen data further includes at least one of a cumulative total boot time of each guest OS and a maximum boot time of each guest OS. The information processing device according to claim 6 .

11. The screen data further includes displaying a progress chart of the booting of each guest OS as a Gantt chart according to the length of booting time of each guest OS. The information processing device according to claim 6 .

12. the information processing device has a boot test mode for booting a plurality of guest OSs in a predetermined order; the controller unit displays a startup test execution screen indicating the order in which the guest OSes are to be started and the startup time of each guest OS before starting the guest OSes in the startup test mode. The information processing device according to claim 7 .

13. A management program executed on one or more information processing devices, a first management step of performing a shutdown of the plurality of guest operating systems; a screen data generating step of acquiring shutdown statuses of the plurality of guest OSs and generating screen data for displaying a shutdown progress chart of the plurality of guest OSs; Run In the screen data generating step, the shutdown progress chart of the plurality of guest OSs is displayed as a Gantt chart according to the length of shutdown time of each guest OS. Management program.

14. A management method executed on one or more information processing devices, comprising: a first management step of performing a shutdown of the plurality of guest operating systems; a screen data generating step of acquiring shutdown statuses of the plurality of guest OSs and generating screen data for displaying a shutdown progress chart of the plurality of guest OSs; Including, In the screen data generating step, the shutdown progress chart of the plurality of guest OSs is displayed as a Gantt chart according to the length of shutdown time of each guest OS. Management method.

15. A management program executed on one or more information processing devices, a first management step of performing booting of a plurality of guest operating systems; a screen data generating step of acquiring boot statuses of the plurality of guest OSs and generating screen data for displaying a progress chart of the booting of the plurality of guest OSs; A management program that runs

16. A management method executed on one or more information processing devices, comprising: a first management step of performing booting of a plurality of guest operating systems; a screen data generating step of acquiring boot statuses of the plurality of guest OSs and generating screen data for displaying a progress chart of the booting of the plurality of guest OSs; Management methods including.

Images