Dependency understanding system, dependency understanding method, and dependency understanding program

Abstract

To make it possible to appropriately collect and manage start and / or stop dependencies for virtual elements and physical elements in a computer system.SOLUTION: A dependency understanding system 10 that collects and manages information in a computer system 1 having a plurality of servers 20 and configuring a virtual machine 27 by the plurality of servers 20, comprises a processor configured to: acquire correspondence relationship information between physical elements (20, 30, 40, 50, or the like) and the virtual machine 27 in the computer system 1; identify a dependency in starting and / or stopping between the virtual machine and the physical elements based on the correspondence relationship information; and store relational information indicating the dependency in a database 15.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a technique for collecting and managing information in a computer system having a plurality of physical servers and configuring virtual machines by one or more of the physical servers.

Background Art

[0002] In a computer system, due to the development of virtualization technology, SDx (such as SDC (Software Defined Computing), SDN (Software Defined Networking), SDS (Software Defined Storage), etc.) controlled by software is being utilized.

[0003] In a computer system, in addition to various elements such as business applications, management software, an OS, a hypervisor, and hardware, software for controlling SDx is also required, making the system more complex.

[0004] In a computer system, for example, it is necessary to perform regular planned power outages, and accordingly, it is necessary to stop and start the system. However, there is a relationship between each element, and it is necessary to consider the stop order and start order.

[0005] However, due to the complexity of the system, it is difficult to manually control it considering the dependency relationships of each element, and a lot of time is required to make plans and perform operations.

[0006] As a related technique, for example, Patent Document 1 discloses a technique for extracting communication connection relationships between virtual servers from communication histories and determining the processing order when performing startup processing or stop processing for virtual servers.

[0007] Also, Patent Document 2 discloses a technique for controlling the startup of a plurality of communication units using startup priority information for starting a communication unit.

Prior Art Documents

Patent Document

[0008]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0009] In the technology disclosed in Patent Document 1, it is possible to determine the processing order between virtual servers when performing startup processing or stop processing, but the processing order when performing startup processing or stop processing for other elements including physical elements such as physical servers is not considered. When performing the startup and stop order of a computer system, it is required to consider physical elements as well.

[0010] The present invention has been made in view of the above circumstances, and an object thereof is to provide a technology capable of appropriately collecting and managing the startup and / or stop dependency relationships for virtual elements and physical elements in a computer system.

Means for Solving the Problems

[0011] To achieve the above object, a dependency relationship grasping system according to one aspect is a dependency relationship grasping system that has a plurality of physical servers and collects and manages information in a computer system in which virtual machines are configured by the plurality of physical servers, and has a processor, and the processor acquires correspondence relationship information between physical elements in the computer system and the virtual machines, and based on the correspondence relationship information, identifies the startup and / or stop dependency relationships between the virtual machines and the physical elements, and stores relevant information indicating the dependency relationships in a storage unit.

Effects of the Invention

[0012] According to the present invention, it is possible to appropriately collect and manage the startup and / or stop dependencies of virtual elements and physical elements in a computer system.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0014] Embodiments will be described with reference to the drawings. Note that the embodiments described below do not limit the invention according to the claims, and not all of the elements and combinations thereof described in the embodiments are essential for the solution means of the invention.

[0015] In the following description, information may be described in terms of an "AAA table", but the information may be represented in any data structure. That is, in order to indicate that the information is independent of the data structure, the "AAA table" can be referred to as "AAA information".

[0016] FIG. 1 is an overall configuration diagram of a computer system according to an embodiment.

[0017] The computer system 1 includes a dependency grasping system 10, one or more servers 20, one or more storages 30, an FC (Fibre Channel) switch 40, and a LAN switch 50. The one or more servers 20 and the one or more storages 30 are communicably connected via the FC switch 40. Also, the one or more servers 20 and the dependency grasping system 10 are communicably connected via the LAN switch 50.

[0018] The FC switch 40 relays data between the server 20 and the storage 30. The LAN switch 50 relays data between the servers 20 or between the server 20 and the dependency grasping system 10. The storage 30 is a physical storage and stores various data.

[0019] The server 20 is a physical server and has a processor and a memory. Among the plurality of servers 20, there is a server that has an OS (Operating System) 21 and executes an application (App in the figure) 22 on the OS 21. The OS 21 of such a server that performs processing independently includes an agent 21a that detects changes in the physical configuration information of the server 20 and notifies the dependency grasping system 10.

[0020] Among the plurality of servers 20, there is a group of servers 20 that configure a virtual storage 24, a virtual network 25, and a virtual infrastructure 26 by virtualizing the physical elements of the plurality of servers 20. Such a server 20 has a hypervisor 23 that creates and executes a virtual machine 27 (VM) on the virtual infrastructure 26. The virtual machine 27 has an OS 21 and executes an application 22 on the OS 21.

[0021] The computer system 1 has an SDx management server 28 that manages the virtualization of the group of servers 20. The SDx management server 28 may be configured by, for example, VMs, or may be configured by non-virtualized servers 20. The SDx management server 28 includes, for example, an SDN (Software Defined Networking) management server 28a that manages the virtual network 25, an SDS (Software Defined Storage) management server 28b that manages the virtual storage 24, and an SDC (Software Defined Computing) management server 28c that manages the virtual infrastructure 26. The SDN management server 28a, the SDS management server 28b, and the SDC management server 28c include an agent 28d that detects changes in the configurations managed by each server and notifies the dependency grasping system 10.

[0022] The dependency grasping system 10 is a system that manages, for example, the startup and / or stop dependencies between virtual elements and physical elements in the computer system 1. The dependency grasping system 10 includes an information acquisition unit 11, an information arrangement unit 12, a result output unit 13, a configuration change detection unit 14, and a database 15.

[0023] The information acquisition unit 11 acquires configuration information of physical elements (such as servers 20, storage 30, FC switches 40, LAN switches 50, etc.) from the physical elements (for example, information on the configuration of the physical elements themselves and connection relationships with other physical elements: correspondence relationship information), and acquires configuration information about virtual elements (virtual machines) from the SDx management server 28 (for example, information on elements (physical elements, virtual elements) that configure or are related to the virtual elements: correspondence relationship information).

[0024] The information organizing unit 12 organizes the configuration information acquired by the information acquisition unit 11 and generates correlation information indicating the activation and stop dependency relationships between virtual elements and physical elements.

[0025] The result output unit 13 outputs information on elements that depend on the activation and stop of a desired element based on the correlation information.

[0026] The configuration change detection unit 14 receives configuration changes of elements (physical elements, virtual elements) from the server 20 and the SDx management server 28, detects whether the configuration change affects the activation and stop dependency relationships between the managed elements, and performs a process of acquiring configuration information when there is an impact.

[0027] The database 15 stores a correlation table 16 that manages information on the activation and stop dependency degrees between elements, a group configuration table 17 that manages information on the configuration of a group (a host group composed of multiple physical servers, a virtual network composed of multiple physical servers, a virtual storage composed of multiple physical servers, etc.), and a management target table 18 that manages targets for managing activation and stop dependency relationships in the dependency relationship grasping system 10.

[0028] Next, the hardware configuration of the dependency relationship grasping system 10 will be described.

[0029] FIG. 2 is a hardware configuration diagram of a dependency relationship grasping system according to an embodiment.

[0030] The dependency relationship grasping system 10 is configured by a computer such as a PC (Personal Computer) or a general-purpose server, and includes a communication interface (I / F) 101, a CPU 102 as an example of a processor, an input device 103, a storage device 104, a memory 105, and a display device 106, and these components are communicably connected via a bus 107.

[0031] The communication I / F 101 is an interface such as a wired LAN card or a wireless LAN card, and communicates with other devices (e.g., server 20) via a network.

[0032] The CPU 102 executes various processes according to a program (dependency grasping program) stored in the memory 105 and / or the storage device 104. The information acquisition unit 11, the information arrangement unit 12, the result output unit 13, and the configuration change detection unit 14 are configured by the CPU 102 executing the dependency grasping program.

[0033] The memory 105 is, for example, a RAM, and stores programs executed by the CPU 102 and necessary information.

[0034] The storage device 104 is an example of a storage unit, and is, for example, a hard disk or a flash memory, and stores programs executed by the CPU 102 and data used by the CPU 102. The storage device 104 stores a dependency grasping program that executes various processes of the dependency grasping system 10 as a program, and stores the database 15.

[0035] The input device 103 is, for example, a mouse, a keyboard, etc., and accepts input of information by the user. The display device 106 is, for example, a display, and displays and outputs a screen including various information (e.g., startup information display screen 200 (see FIG. 10), stop information display screen 300 (see FIG. 12)).

[0036] Next, the relevance table 16 will be described in detail.

[0037] FIG. 3 is a configuration diagram of a relevance table according to an embodiment.

[0038] The relevance table 16 is a table that manages the activation and stop dependencies between a certain element (virtual element, physical element) and the elements that constitute or are related to that element (referred to as constituent elements). The records of the relevance table 16 include fields of number (♯) 16a, element 16b, constituent element 16c, is it a group? 16d, dependency (at stop) 16e, and dependency (at startup) 16f.

[0039] In number (#) 16a, the record number is stored. In element 16b, the identification information (name, etc.) of the element that the record targets is stored. In constituent element 16c, the identification information of the elements that constitute or are related to the element corresponding to the record (referred to as constituent elements) is stored. In is it a group? 16d, information indicating whether the constituent element corresponding to the record is a group, that is, whether it is composed of a plurality of elements, is stored. In this embodiment, when the constituent element corresponding to the record is a group, True is stored, and when it is not a group, False is stored.

[0040] In dependency (at stop) 16e, information indicating the dependency of the constituent element corresponding to the record on the element at the time of stop is stored. In this embodiment, as the dependency, "essential" is stored when the stop of the element is essential at the time of stop, and "optional" is stored when the stop of the element is not essential. In dependency (at startup) 16f, information indicating the dependency of the element corresponding to the record on the constituent element at the time of startup is stored. In this embodiment, as the dependency, "essential" is stored when the startup of the constituent element is essential at the time of startup, and "optional" is stored when the startup of the constituent element is not essential.

[0041] Next, the group configuration table 17 will be described in detail.

[0042] FIG. 4 is a configuration diagram of a group configuration table according to an embodiment.

[0043] The group configuration table 17 is a table that manages the configuration of groups and has records for each group. The records in the group configuration table 17 include fields of a number (#) 17a, a group 17b, a minimum number 17c, and a plurality of elements (element 1 17d, element 2 17e, element 3 17f, element 4 17g, element 5 17h, etc.).

[0044] The number (#) 17a stores the record number. The group 17b stores the group name of the group corresponding to the record. The minimum number 17c stores the minimum number of elements (minimum number) required to operate as the group corresponding to the record. The plurality of elements (element 1 17d, element 2 17e, element 3 17f, element 4 17g, element 5 17h, etc.) store the identification information of the elements (physical elements) that make up the group. Here, the relevance information corresponds to the relevance table 16 and the group configuration information table 17.

[0045] Next, the management target table 18 will be described in detail.

[0046] FIG. 5 is a configuration diagram of a management target table according to an embodiment.

[0047] The management target table 18 is a table that manages elements (management target elements) to be managed for startup and stop by the dependency grasping system 10 and stores records for each management target element. The records in the management target table 18 include fields of a number (#) 18a and a management target element 18b. The number (#) 18a stores the record number. The management target element 18b stores the identification information of the management target element corresponding to the record. Examples of the management target elements include virtual machines (management target virtual machines), servers (physical servers), etc.

[0048] Next, the processing operation by the dependency grasping system 10 will be described.

[0049] First, the table creation process executed by the dependency grasping system 10 at the start of the first operation will be described.

[0050] FIG. 6 is a flowchart of table creation processing according to an embodiment.

[0051] First, the information acquisition unit 11 acquires configuration information of physical elements (server 20, storage 30, FC switch 40, LAN switch 50, etc.) from physical elements (e.g., information on the configuration of the physical elements themselves and information on the connection relationships with other physical elements), and acquires configuration information on virtual elements (virtual machines, etc.) from the SDx management server 28 (e.g., information on the physical elements constituting or related to the virtual elements) (S11). The configuration information on virtual elements includes, for example, information such as the network to which the virtual machine is connected, the disks to which it is connected, and the system disk of the virtual machine.

[0052] Next, the information arrangement unit 12 executes relevance table creation processing (virtual machine elements) (see FIG. 7) for creating records related to virtual machines in the relevance table 16 based on the configuration information on virtual elements (S12). According to this relevance table creation processing (virtual machine elements) (see FIG. 7), records related to virtual machines in the relevance table 16 (e.g., records numbered 1 to 7 in number 16a in FIG. 3) are created.

[0053] Next, the information arrangement unit 12 creates records related to physical servers in the relevance table 16 based on the configuration information on physical elements (S13). According to this step, records related to physical servers in the relevance table 16 (e.g., records numbered 8 and 9 in number 16a in FIG. 3) are created.

[0054] Next, the information arrangement unit 12 extracts the constituent elements of the group and the minimum number of elements required for the group for the groups registered as constituent elements in the relevance table 16 based on the configuration information on the virtual machines acquired from the SDx management server 28, creates a group configuration table 17 based on the extracted information (S14), and ends the table creation processing.

[0055] According to this table creation process, the relevance table 16 and the group configuration table 17 in the initial state in the computer system 1 are created.

[0056] Next, the relevance table creation process (virtual machine element) in step S12 will be described in detail.

[0057] FIG. 7 is a flowchart of the relevance table creation (update) process according to an embodiment. The relevance table creation process (virtual machine element) is the process of steps S21 to S31 in FIG. 7.

[0058] First, the information organizing unit 12 adds a record to the relevance table 16 with the virtual machine as an element, the physical server as a component, not a group (False), and the dependency (at stop) and the dependency (at startup) as "essential" as a record about the physical server (target physical server) on which the virtual machine operates, that is, the physical server that constitutes the virtual machine. (S21).

[0059] Next, the information organizing unit 12 determines whether the target physical server belongs to a host group based on the configuration information obtained from the SDx management server 28 (S22).

[0060] As a result, if it is determined that the target physical server belongs to a host group (S22: Yes), the information organizing unit 12 adds a record to the relevance table 16 with the virtual machine as an element, the host group as a component, a group (True), and the dependency (at stop) and the dependency (at startup) as "essential", and changes the dependency (at startup) in the record of the target physical server to "optional" (S23), and proceeds to the process of loop A (S24 to S25). Here, the reason for arbitrarily changing the dependency (at startup) of the target physical server is that the virtual machine may be composed of a physical server different from the target physical server belonging to the host group, and is not limited to the target physical server.

[0061] On the other hand, when it is determined that the target physical server does not belong to the host group (S22: No), the information sorting unit 12 proceeds with the processing to the processing of loop A (S24 to S25).

[0062] Next, the information sorting unit 12 executes the processing of loop A (S24 to S25) with each of all the networks connected to the virtual machine as a processing target. Here, the network to be processed is referred to as the target network.

[0063] In the processing of loop A, the information sorting unit 12 determines whether the target network is a virtual network (S24).

[0064] As a result, when it is determined that the target network is a virtual network (S24: Yes), the information sorting unit 12 adds to the relevance table 16 a record with the virtual machine as an element, the target network as a constituent element, the group as True, and the dependency (at stop) and the dependency (at startup) as "arbitrary" as a record for the target network (S25), and ends the processing of loop A for the target network.

[0065] On the other hand, when it is determined that the target network is not a virtual network (S24: No), the information sorting unit 12 ends the processing of loop A for the target network.

[0066] When the processing of loop A for the target network ends, the information sorting unit 12 executes the processing of loop A with the next network as the target network, and when the processing of loop A for all the connected networks ends, it exits loop A.

[0067] Next, the information sorting unit 12 executes the processing of loop B (S26 to S31) with each of all the disks connected to the virtual machine as a processing target. Here, the disk to be processed is referred to as the target disk.

[0068] In the process of loop B, the information sorting unit 12 determines whether the target disk is a system disk (S26).

[0069] As a result, if it is determined that the target disk is a system disk (S26: Yes), the information sorting unit 12 adds to the relevance table 16 a record with the virtual machine as an element, the storage where the target disk is stored as a component, and the dependency (at shutdown) and the dependency (at startup) set to "essential" as a record regarding the storage where the disk is stored (S27), and proceeds with the process to step S29.

[0070] On the other hand, if it is determined that the target disk is not a system disk (S26: No), the information sorting unit 12 adds to the relevance table 16 a record with the virtual machine as an element, the storage where the target disk is stored as a component, and the dependency (at shutdown) and the dependency (at startup) set to "optional" as a record regarding the storage where the disk is stored (S28), and proceeds with the process to step S29.

[0071] In step S29, the information sorting unit 12 determines whether the target storage is a virtual storage.

[0072] As a result, if it is determined that the target disk is a virtual storage (S29: Yes), the information sorting unit 12 sets the record regarding the storage where the disk is stored as a group (True) (S30), and adds to the relevance table 16 a record with the entity element as an element, the component of the entity element (e.g., physical storage) as a component, and the dependency (at shutdown) and the dependency (at startup) set to "essential" as a record regarding the entity of the virtual storage where the entity of the target disk is stored (e.g., physical server), and ends the process of loop B for the target disk.

[0073] On the other hand, if it is determined that the target disk is not a virtual storage (S29: No), the information sorting unit 12 ends the process of loop B for the target disk.

[0074] When the processing of loop B for the target disk is completed, the information organizing unit 12 executes the processing of loop B with the next disk as the target disk. When the processing of loop B for all the connected disks is completed, it exits loop B and ends the relevance table creation process (virtual machine element).

[0075] Next, the table update process by the dependency relationship grasping system 10 will be described.

[0076] FIG. 8 is a flowchart of the table update process according to an embodiment.

[0077] The table update process is executed, for example, when a configuration change notification is received from the agent 28d of the SDx management server 28. Note that the agent 28d notifies the dependency relationship grasping system 10 of the change content when, in the computer system 1, for example, operations such as changing the host (server) on which the virtual machine operates, adding a virtual machine disk, or changing the virtual machine network occur.

[0078] The configuration change detection unit 14 of the dependency relationship grasping system 10 refers to the management target table 18 and determines whether the notified configuration change affects the management target elements (S41).

[0079] As a result, when it is determined that the configuration change has no effect on the management target elements (S41: No), it means that there is no need to update the table, so the configuration change detection unit 14 ends the table update process.

[0080] On the other hand, when it is determined that the configuration change affects the management target elements (S41: Yes), the configuration change detection unit 14 notifies the information acquisition unit 11 of the change location, and the information acquisition unit 11 that has received the notification acquires the configuration information of the change location from the SDx management server 28 (S42).

[0081] Next, the information organizing unit 12 executes a relevance table update process (virtual machine element) (see FIG. 7) for updating the relevance table 16 based on the configuration information of the changed portion (S43).

[0082] Next, the information organizing unit 12 updates the information related to the physical server in the relevance table 16 based on the configuration information of the changed portion (S44).

[0083] Next, based on the update information of the changed portion acquired from the SDx management server 28, the information organizing unit 12 extracts the components of the group and the minimum number of elements required for the group for the elements of the group updated in the relevance table 16, updates the group configuration table 17 (S45), and ends the table update process.

[0084] According to this table update process, in the computer system 1, when the configuration information related to the management target element is changed, the relevance table 16 and the group configuration table 17 can be appropriately updated according to the change content.

[0085] Next, the relevance table update process (virtual machine element) in step S43 will be described in detail.

[0086] The relevance table update process (virtual machine element) is the process of steps S20 to 31 in FIG. 7.

[0087] First, the information organizing unit 12 deletes the records in the relevance table 16 in which the virtual machine targeted for configuration change is an element (S20). Note that hereafter, the process is the same as the relevance table creation process.

[0088] Next, the startup information output process for outputting the information of other elements that need to be started when starting the target element will be described.

[0089] FIG. 9 is a flowchart of the startup information output process according to an embodiment.

[0090] When the result output unit 13 receives a designation of an element to be activated by the user (activation target element, in this example, for example, a virtual machine) (S51), it refers to the relevance table 16 and checks the components corresponding to the activation target element (S52).

[0091] Next, the result output unit 13 executes the processing of loop C (S53 to S56) with each of the confirmed components as a processing target. Here, the component to be processed is referred to as the target component.

[0092] In the processing of loop C, first, the result output unit 13 refers to the record in the relevance table 16 of the target component and determines whether the activation dependency of the target component at the time of activation is "essential" (S53).

[0093] As a result, when the activation dependency of the target component at the time of activation is "essential" (S53: Yes), the result output unit 13 determines whether the target component is a group (S54).

[0094] As a result, when it is determined that the target component is a group (S54: Yes), the result output unit 13 outputs to the activation information display screen 200 (see FIG. 10) a list of each element belonging to the group, the minimum number of elements required for the activation of this group, and the elements that the activation target element was activated at the time of stop (in the relevance table 16, the components associated with the activation target elements in the group) (S55), and ends the processing of loop C for the target component. On the other hand, when it is determined that the target component is not a group (S54: No), the result output unit 13 outputs the target component to the activation information display screen 200 (S56), and ends the processing of loop C for the target component.

[0095] On the other hand, when the activation dependency of the target component at the time of activation is not "essential" (S53: No), the result output unit 13 ends the processing of loop C for the target component.

[0096] When the processing of loop C for the target component is completed, the result output unit 13 executes the processing of loop C with the next component as the target component. When the processing of loop C for all the target components that have been confirmed is completed, it exits loop C and ends the startup information output processing.

[0097] Next, the startup information display screen 200 will be described.

[0098] FIG. 10 is a diagram showing a startup information display screen according to an embodiment. The startup information display screen 200 in FIG. 10 is an example of a startup information display screen when the relevance table 16 is in the state shown in FIG. 3 and the group configuration table 17 is in the state shown in FIG. 4, and the virtual machine 1 is input as the startup target element.

[0099] The startup information display screen 200 includes a startup target element display area 201 for displaying the startup target element and a startup essential element display area 202 for displaying the elements that are essential for startup as a premise.

[0100] In the startup essential element display area 202, the components that require startup are displayed. When the component is a group, a list of the elements belonging to that group is displayed. In the example of FIG. 10, a list of the elements belonging to host group 1 required for the startup of virtual machine 1 and a list of the elements belonging to virtual storage 1 are displayed. Also, in the startup essential element display area 202, the minimum number of elements 202a (for example, the number of physical servers) required for the startup of the group is displayed. Further, in the startup essential element display area 202, the stop-time element information 202b that can identify the element that constituted the startup target element at the time of stop among the elements of the group (for example, when the startup target element is a virtual machine, the server) is displayed. According to this stop-time element information 202b, the element that constituted the startup target element at the time of stop can be identified. Therefore, it is possible to operate in the same state as at the time of stop, and it is possible to appropriately prevent unevenness in resources.

[0101] Next, the stop information output process for outputting information on other elements that require stopping when stopping the element to be stopped will be described.

[0102] FIG. 11 is a flowchart of the stop information output process according to an embodiment.

[0103] When the result output unit 13 receives a designation of an element to be stopped (the element to be stopped, in this example, for example, a physical server) from the user (S61), it refers to the relevance table 16 and checks the elements of which the element to be stopped is a constituent element (S62).

[0104] Next, the result output unit 13 executes the processing of loop D (S63 to S64) with each of the confirmed elements as a processing target. Here, the element to be processed is referred to as the target element.

[0105] In the processing of loop D, the result output unit 13 refers to the record of the relevance table 16 of the target element and determines whether the dependency at the time of stopping for the target element is "essential" (S63).

[0106] As a result, when the dependency at the time of stopping for the target element is "essential" (S63: Yes), the result output unit 13 outputs this element as an element that must be stopped to the stop information display screen 300 (see FIG. 12) (S64), and ends the processing of loop D for the target element.

[0107] On the other hand, when the dependency at the time of stopping for the target element is not "essential" (S63: No), the result output unit 13 ends the processing of loop D for the target element.

[0108] When the processing of loop D for the target element ends, the result output unit 13 executes the processing of loop D with the next element as the target element, and when the processing of loop D for all the confirmed target elements ends, it exits loop D.

[0109] Next, the result output unit 13 determines whether there is a group including the element to be stopped (S65).

[0110] As a result, when it is determined that there is no group including the target component (S65: No), the result output unit 13 ends the stop information output process.

[0111] On the other hand, when there is a group including the target component (S65: Yes), the result output unit 13 executes the processes of loop E (S66 to S69) with each group including the stop target element as a processing target. Here, the processing target group is referred to as the target group.

[0112] In the process of loop E, the result output unit 13 determines whether or not at least the minimum required number of elements are activated even if the stop target element is stopped for the target group (S66).

[0113] As a result, when it is determined that at least the minimum required number of elements are not activated (S66: No), the result output unit 13 checks the elements that the group consists of from the relevance table 16 (S67).

[0114] Next, the result output unit 13 executes the processes of loop F (S68 to S69) with each of the checked elements as a processing target.

[0115] In the process of loop F, the result output unit 13 determines whether or not the dependency at the time of stop for the processing target element is "essential" (S68).

[0116] As a result, when it is determined that the dependency at the time of stop for the processing target element is "essential" (S68: Yes), the result output unit 13 outputs to the stop information display screen 300 (see FIG. 12) that it is essential to stop this processing target element (S69), and ends the process of loop F for the processing target element.

[0117] On the other hand, when it is determined that the dependency at the time of stop for the processing target element is not "essential" (S68: No), the result output unit 13 ends the process of loop F for the processing target element.

[0118] When the processing of loop F for the element to be processed is completed, the result output unit 13 executes the processing of loop F with the next element as the element to be processed, and when the processing of loop F for all the confirmed elements is completed, it exits loop F.

[0119] On the other hand, when it is determined that the minimum required number of elements are activated (S66: Yes), the result output unit 13 exits the processing of loop F.

[0120] When exiting loop F, the result output unit 13 executes the processing of loop E with the next group as the target group, and when the processing of loop E for all the confirmed groups is completed, it exits loop E and ends the stop information output processing.

[0121] Next, the stop information display screen 300 will be described.

[0122] FIG. 12 is a diagram showing a stop information display screen according to an embodiment. The stop information display screen 300 in FIG. 12 is an example of a stop information display screen when the physical server 1 is input as the stop target element in the case where the relevance table 16 is in the state shown in FIG. 3 and the group configuration table 17 is in the state shown in FIG. 4.

[0123] The stop information display screen 300 includes a stop target element display area 301 for displaying the stop target element and a stop essential element display area 302 for displaying elements that must be stopped in advance. In the example of FIG. 12, the virtual machine 1 and the virtual machine 2 are displayed in the stop essential element display area 302. In this example, the virtual machine 1 is output (displayed) by the processing of step S64, and the virtual machine 2 is output by the processing of step S69. According to this stop information display screen, it is possible to appropriately display the virtual machines that must be stopped when stopping the physical server.

[0124] Note that the present invention is not limited to the above-described embodiment, and can be appropriately modified and implemented without departing from the spirit of the present invention.

[0125] For example, in the above embodiment, the dependencies regarding stop and start were managed, but the present invention is not limited thereto, and the dependencies regarding either stop or start may be managed.

[0126] Also, in the above embodiment, only the elements essential for starting the elements to be started were displayed, but the present invention is not limited thereto, and elements (any elements) related to the elements to be started may also be displayed. Also, only the elements essential for stopping the elements to be stopped were displayed, but the present invention is not limited thereto, and elements (any elements) related to the elements to be stopped may also be displayed.

[0127] Also, in the above embodiment, part or all of the processing performed by the processor may be performed by a hardware circuit. Also, the program in the above embodiment may be installed from a program source. The program source may be a program distribution server or a recording medium (for example, a portable recording medium).

Explanation of Signs

[0128] 1... computer system, 10... dependency grasping system, 11... information acquisition unit, 12... information arrangement unit, 13... result output unit, 14... configuration change detection unit, 15... database, 16... relevance table, 17... group configuration table, 18... management target table, 20... server, 21... OS, 21a... agent, 22... application, 23... hypervisor, 24... virtual storage, 25... virtual network, 26... virtual infrastructure, 27... virtual machine, 28... SDx management server, 30... storage, 40... FC switch, 50... LAN switch, 101... communication I / F, 102... CPU, 103... input device, 104... storage device, 105... memory, 106... display device

Claims

1. A dependency understanding system that collects and manages information in a computer system having a plurality of physical servers and configuring virtual machines using the plurality of physical servers, A processor is included. The processor, acquiring information on a correspondence relationship between a physical element in the computer system and the virtual machine; A dependency understanding system that identifies dependencies in startup and / or shutdown between the virtual machine and the physical element based on the correspondence information, and stores association information indicating the dependencies in a memory unit.

2. The virtual machine can be configured by any one of a plurality of physical servers that configure a host group; The processor, Obtaining host group configuration information indicating a plurality of physical servers that constitute the host group; identifying a host group to which the physical server constituting the virtual machine belongs based on the host group configuration information, identifying a dependency relationship in starting and / or stopping between the virtual machine and the host group, and storing the identified dependency relationship in the storage unit while including it in the association information; The host group configuration information is stored in the storage unit. The dependency relationship understanding system according to claim 1 .

3. The host group configuration information includes the minimum number of the physical servers required to configure the host group. The dependency relationship grasping system according to claim 2 .

4. the dependencies include dependencies on startup; The processor, When the physical server constituting the virtual machine belongs to the host group, the dependency relationship between the virtual machine and the physical server is set to be optional and the dependency relationship between the virtual machine and the host group is set to be mandatory. The dependency relationship grasping system according to claim 2 .

5. The processor, The dependency relationship information regarding the start and / or stop of the elements and / or element groups related to the virtual machine is also included in the relationship information and stored in the storage unit; The dependencies include information about whether the elements and / or groups of elements are required or optional for starting and / or stopping the virtual machine. The dependency relationship understanding system according to claim 1 .

6. The processor, Receive notifications when configuration changes related to virtual machines occur, determining whether the notified change is a change related to a managed virtual machine that is a managed virtual machine; If the change is related to a managed virtual machine, acquiring new correspondence relationship information between the managed virtual machine and a physical element in the computer system; The association information is updated based on the new correspondence information. The dependency relationship understanding system according to claim 1 .

7. The processor, Accepts instructions for the virtual machine to be started, Identifying a physical server and / or a host group required to start the virtual machine to be started based on the relevance information, and outputting information indicating the identified physical server and / or host group. The dependency relationship grasping system according to claim 2 .

8. The processor, Display information indicating the minimum number of physical servers required in the host group required for the startup. The dependency relationship grasping system according to claim 7.

9. The processor, Displaying information capable of identifying a physical server that constituted the virtual machine at the time of the previous stop in a host group required for the start The dependency relationship grasping system according to claim 8.

10. The processor, Receives instructions from the physical server to be stopped, Based on the correlation information, a virtual machine required for shutting down the physical server to be shut down is identified, and information indicating the identified virtual machine is output. The dependency relationship grasping system according to claim 2 .

11. 1. A dependency grasping method for a dependency grasping system that collects and manages information in a computer system having a plurality of physical servers and configuring virtual machines using the plurality of physical servers, comprising: The dependency relationship understanding system includes: acquiring information on a correspondence relationship between a physical element in the computer system and the virtual machine; Based on the correspondence information, a dependency relationship in starting and / or stopping between the virtual machine and the physical element is identified, and association information indicating the dependency relationship is stored in a storage unit. How to understand dependencies.

12. A dependency grasping program that causes a computer to execute a process for managing dependencies in starting and / or stopping between physical elements and virtual machines constituted by the physical servers in a computer system having a plurality of physical servers, the program comprising: The computer includes: acquiring information on a correspondence relationship between a physical element in the computer system and the virtual machine; A dependency understanding program that identifies dependency relationships in the startup and / or shutdown between the virtual machine and the physical element based on the correspondence information, and stores association information indicating the dependency relationships in a memory unit.

Images