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, one or more of which configure virtual machines. [Background technology]

[0002] In computer systems, advances in virtualization technology have led to the emergence of software-controlled SDx (SDC (Software Defined Computing), SDN (Software Defined Networking), and SDS (Software Defined Storage). a ge) etc.) are utilized.

[0003] Computer systems are becoming more complex, requiring software to control SDx in addition to various elements such as business applications, management software, operating systems, hypervisors, and hardware.

[0004] In a computer system, for example, it is necessary to carry out planned power outages on a regular basis, and the system must be shut down and started up accordingly. However, there is a relationship between each element, and the order in which they are shut down and started up must be taken into consideration.

[0005] However, as systems become more complex, it becomes difficult to control them manually while taking into account the dependencies between each element, and planning and working on them takes a lot of time.

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

[0007] Furthermore, Patent Document 2 discloses a technique for controlling the activation of a plurality of communication units by using activation priority information for activating the communication units. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-10772 [Patent Document 2] Japanese Patent Application Publication No. 2019-164621 Summary of the Invention [Problem to be solved by the invention]

[0009] The technology disclosed in Patent Document 1 can determine the processing order between virtual servers when performing startup or shutdown processing, but does not take into consideration the processing order when performing startup or shutdown processing for other elements, including physical elements such as physical servers. When determining the startup and shutdown sequence of a computer system, it is necessary to take physical factors into consideration.

[0010] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a technology that can appropriately collect and manage startup and / or shutdown dependencies between virtual elements and physical elements in a computer system. [Means for solving the problem]

[0011] In order to achieve the above-mentioned object, one aspect of a dependency understanding system is a dependency understanding system that has a plurality of physical servers and collects and manages information in a computer system in which the plurality of physical servers constitute virtual machines, and has a processor that acquires correspondence information between physical elements in the computer system and the virtual machines, and based on the correspondence information, identifies dependencies in startup and / or shutdown between the virtual machines and the physical elements, and stores relationship information indicating the dependencies in a memory unit. [Effects of the Invention]

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

[0013] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a computer system according to one embodiment. [Figure 2] FIG. 2 is a hardware configuration diagram of a dependency relationship grasping system according to an embodiment. [Figure 3] FIG. 3 is a diagram illustrating the configuration of a relevance table according to an embodiment. [Figure 4] FIG. 4 is a diagram showing the configuration of a group configuration table according to an embodiment. [Figure 5] FIG. 5 is a diagram showing the configuration of a management target table according to an embodiment. [Figure 6] FIG. 6 is a flowchart of a table creation process according to an embodiment. [Figure 7] FIG. 7 is a flowchart of a relevance table creation (update) process according to an embodiment. [Figure 8] FIG. 8 is a flowchart of a table update process according to one embodiment. [Figure 9] FIG. 9 is a flowchart of a startup information output process according to an embodiment. [Figure 10] FIG. 10 is a diagram showing a startup information display screen according to an embodiment. [Figure 11] FIG. 11 is a flowchart of a stop information output process according to an embodiment. [Figure 12] FIG. 12 is a diagram showing a stop information display screen according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] The following description of the embodiments will be given with reference to the drawings. Note that the embodiments described below do not limit the scope of the invention as claimed, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0015] In the following explanation, information may be described using the expression "AAA table", but the information may be expressed in any data structure. In other words, to show that the information does not depend on the data structure, the "AAA table" can be called "AAA information".

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

[0017] The computer system 1 includes a dependency relationship understanding 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 communicatively connected via the FC switch 40. The one or more servers 20 and the dependency relationship understanding system 10 are communicatively connected via the LAN switch 50.

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

[0019] The server 20 is a physical server having a processor and a memory. Among the multiple servers 20, there is a server having an OS (Operating System) 21 and running 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 tracking system 10.

[0020] Furthermore, among the multiple servers 20, there is a group of servers 20 that configure virtual storage 24, a virtual network 25, and a virtual infrastructure 26 by virtualizing the physical elements of the multiple servers 20. Such servers 20 have a hypervisor 23 that creates and runs a virtual machine 27 (VM) on the virtual infrastructure 26. The virtual machine 27 has an OS 21 and runs 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, for example, by a VM, or may be configured by a non-virtualized server 20. The SDx management server 28 includes, for example, an SDN (Software Defined Networking) management server 28a that manages the virtual network 25, and an SDS (Software Defined Storage) management server 28b that manages the virtual storage 24. a The SDN management server 28a, the SDS management server 28b, and the SDC management server 28c manage the virtual infrastructure 26. The SDN management server 28a, the SDS management server 28b, and the SDC management server 28c each include an agent 28d that detects changes to the configurations managed by each server and notifies the dependency relationship understanding system 10.

[0022] The dependency understanding system 10 is a system that manages the startup and / or shutdown dependencies between virtual elements and physical elements in the computer system 1. The dependency understanding system 10 includes an information acquisition unit 11, an information organization 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 (for example, information on the configuration of the physical element itself, information on the connection relationship with other physical elements: correspondence information) from physical elements (servers 20, storage 30, FC switches 40, LAN switches 50, etc.), and acquires configuration information about virtual elements (virtual machines) (for example, information on the elements (physical elements, virtual elements) that configure or are related to the virtual elements: correspondence information) from the SDx management server 28.

[0024] The information organizing unit 12 organizes the configuration information acquired by the information acquiring unit 11, and generates association information that indicates the dependency relationships between the virtual elements and the physical elements with respect to start and stop.

[0025] The result output unit 13 outputs information on elements that depend on the start and stop of the desired element based on the relevance 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 will affect the startup and shutdown dependencies between the elements it manages, and if there is an impact, performs processing to obtain configuration information.

[0027] The database 15 stores an association table 16 that manages information on the degree of startup and shutdown dependency between elements, a group configuration table 17 that manages information on the configuration of a group (a host group consisting of multiple physical servers, a virtual network consisting of multiple physical servers, a virtual storage consisting of multiple physical servers, etc.), and a managed object table 18 that manages objects for which startup and shutdown dependencies are managed by the dependency understanding 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 understanding system 10 is composed of 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 each of these components is connected to each other so that they can communicate with each other 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 (for example, the server 20) via a network.

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

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

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

[0035] The input device 103 is, for example, a mouse, a keyboard, etc., and accepts information input by a user. The display device 106 is, for example, a display, and displays and outputs screens including various types of information (for example, a start-up information display screen 200 (see FIG. 10) and a stop-down information display screen 300 (see FIG. 12)).

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

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

[0038] The association table 16 is a table for managing the start and stop dependencies between a certain element (virtual element, physical element) and an element (called a component) that constitutes or is related to that element. A record in the association table 16 includes fields for a number (#) 16a, an element 16b, a component 16c, a group? 16d, a dependency (at stop) 16e, and a dependency (at start) 16f.

[0039] The number (#) 16a stores the record number. The element 16b stores the identification information (such as name) of the element targeted by the record. The component 16c stores the identification information of the element (called a component) that constitutes or is related to the element corresponding to the record. Is Group? 16d stores information indicating whether the component corresponding to the record is a group, that is, whether it is made up of multiple elements. In this embodiment, if the component corresponding to the record is a group, True is stored, and if it is not a group, False is stored.

[0040] The dependency (at shutdown) 16e stores information indicating the degree of dependency with which a component corresponding to a record depends on an element at the time of shutdown. In this embodiment, the dependency stored is "mandatory" if the element must be stopped at the time of shutdown, and "optional" if the element does not must be stopped. The dependency (at startup) 16f stores information indicating the degree of dependency with which an element corresponding to a record depends on a component at the time of startup. In this embodiment, the dependency stored is "mandatory" if the element must be started at the time of startup, and "optional" if the element does not must be started.

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

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

[0043] The group configuration table 17 is a table for managing the group configuration and has a record for each group. Each record in the group configuration table 17 includes fields for number (#) 17a, group 17b, minimum number 17c, and multiple 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 required to operate as the group corresponding to the record. The multiple elements (element 1 17d, element 2 17e, element 3 17f, element 4 17g, element 5 17h, etc.) store identification information of the elements (physical elements) that make up the group. Here, the relationship information corresponds to the relationship 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 diagram showing the configuration of a management target table according to an embodiment.

[0047] The managed object table 18 is a table for managing elements (managed object elements) whose start and stop are managed by the dependency understanding system 10, and stores a record for each managed object element. A record of the managed object table 18 includes fields for a number (#) 18a and a managed object element 18b. The number (#) 18a stores the record number. The managed object element 18b stores identification information of the managed object element corresponding to the record. Examples of managed object elements include a virtual machine (managed virtual machine) and a server (physical server).

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

[0049] First, a table creation process that the dependency relationship understanding system 10 executes when it starts operating for the first time will be described.

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

[0051] First, the information acquisition unit 11 acquires configuration information of the physical elements (server 20, storage 30, FC switch 40, LAN switch 50, etc.) (for example, information on the configuration of the physical element itself, information on the connection relationship with other physical elements), and acquires configuration information about the virtual elements (virtual machines, etc.) (for example, information on the physical elements that configure or relate to the virtual elements) from the SDx management server 28 (S11). The configuration information about the virtual elements includes, for example, information on the network to which the virtual machine is connected, the connected disks, the system disk of the virtual machine, etc.

[0052] Next, the information organizing unit 12 executes an association table creation process (virtual machine element) (see FIG. 7) for creating records related to virtual machines in the association table 16 based on the configuration information about the virtual elements (S12). According to this association table creation process (virtual machine element) (see FIG. 7), records related to virtual machines in the association table 16 (for example, records numbered 1 to 7 in number 16a in FIG. 3) are created.

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

[0054] Next, based on the configuration information about the virtual machine obtained 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 groups registered as components in the association table 16, creates a group configuration table 17 based on the extracted information (S14), and terminates the table creation process.

[0055] According to this table creation process, the association table 16 and the group configuration table 17 in the initial state of 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] 7 is a flowchart of the relevance table creation (update) process according to one embodiment. The relevance table creation process (virtual machine element) is the process of steps S21 to S31 in FIG.

[0058] First, the information organizing unit 12 adds to the relationship table 16 a record on which a virtual machine is running, i.e., a record for the physical server (target physical server) that constitutes the virtual machine, with the virtual machine as an element, the physical server as a component, not a group (False), and the dependency (when stopped) and dependency (when started) set to "required" (S21).

[0059] Next, the information organizing unit 12 determines whether or not the target physical server belongs to a host group based on the configuration information acquired 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 for the host group to the association table 16, with the virtual machine as an element, the host group as a component, it being a group (True), and the dependency (at shutdown) and dependency (at startup) set to "required," changes the dependency (at startup) in the record for the target physical server to "optional" (S23), and proceeds to processing of loop A (S24-S25). The dependency (at startup) of the target physical server is changed to "optional" here because the virtual machine may be configured on a physical server other than the target physical server belonging to the host group, and is not limited to the target physical server.

[0061] On the other hand, if it is determined that the target physical server does not belong to a host group (S22: No), the information organizing unit 12 advances the process to the process of loop A (S24 to S25).

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

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

[0064] As a result, if it is determined that the target network is a virtual network (S24: Yes), the information organizing unit 12 adds a record for the target network to the association table 16, with the virtual machine as an element, the target network as a component, it being a group (True), and the dependency (at shutdown) and dependency (at startup) set to "optional" (S25), and terminates the processing of loop A for the target network.

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

[0066] When the processing of loop A for the target network is completed, the information organizing unit 12 performs the processing of loop A with the next network as the target network, and when the processing of loop A for all connected networks is completed, it exits loop A.

[0067] Next, the information organizing unit 12 executes the processing of loop B (S26 to S31) for each of all disks connected to the virtual machine as a processing target. Here, the disks as processing targets are referred to as target disks.

[0068] In the processing of loop B, the information organizing 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 organizing unit 12 adds a record to the association table 16 as a record for the storage in which the disk is stored, with the virtual machine as an element, the storage in which the target disk is stored as a component, and the dependency (at shutdown) and dependency (at startup) set to "required" (S27), and proceeds 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 organizing unit 12 adds a record to the association table 16 as a record for the storage in which the disk is stored, with the virtual machine as an element, the storage in which the target disk is stored as a component, and the dependency (at shutdown) and dependency (at startup) set to "optional" (S28), and proceeds to step S29.

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

[0072] As a result, if it is determined that the target disk is virtual storage (S29: Yes), the information organizing unit 12 sets the record for the storage in which the disk is stored as a group (True) (S30), and adds a record to the relationship table 16 for a record for an entity element (e.g., a physical server) of the virtual storage in which the entity of the target disk is stored, with the entity element as the element, the constituent element of the entity element (e.g., physical storage) as the constituent element, and with the dependency (at shutdown) and dependency (at startup) set to "required" (S31), and terminates processing 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 organizing unit 12 ends the processing 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 for the next disk as the target disk, and when the processing of loop B for all connected disks is completed, it exits loop B and terminates the association table creation processing (virtual machine element).

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

[0076] FIG. 8 is a flowchart of a table update process according to one 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 when an operation such as changing the host (server) on which a virtual machine runs, adding a disk to a virtual machine, or changing the network of a virtual machine occurs in the computer system 1, the agent 28d notifies the dependency relationship understanding system 10 of the details of this change.

[0078] The configuration change detection unit 14 of the dependency tracking system 10 refers to the managed object table 18 and determines whether or not the notified configuration change will have an effect on the managed object elements (S41).

[0079] As a result, if it is determined that the configuration change has no effect on the managed element (S41: No), this means that there is no need to update the table, and the configuration change detection unit 14 ends the table update process.

[0080] On the other hand, if it is determined that the configuration change will affect the managed elements (S41: Yes), the configuration change detection unit 14 notifies the information acquisition unit 11 of the changed parts, and the information acquisition unit 11, upon receiving the notification, acquires configuration information of the changed parts from the SDx management server 28 (S42).

[0081] Next, the information organizing unit 12 executes the relevance table update process (virtual machine element) (see FIG. 7) to update 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 changes obtained 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 terminates the table update process.

[0084] According to this table update process, when configuration information relating to managed elements is changed in the computer system 1, the association table 16 and group configuration table 17 can be updated appropriately in accordance with the changes.

[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 S31 in FIG.

[0087] First, the information organizing unit 12 deletes the record in which the virtual machine to be changed in configuration is an element from the relevance table 16 (S20). Note that the process thereafter is the same as the relevance table creation process.

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

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

[0090] When the result output unit 13 receives a specification from the user of an element to be started (an element to be started, in this example, for example, a virtual machine) (S51), it refers to the association table 16 and identifies the components corresponding to the element to be started (S52).

[0091] Next, the result output unit 13 performs the processing (S53 to S56) of loop C on each of the confirmed components as a processing target. Here, the components as processing targets are referred to as target components.

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

[0093] As a result, if the degree of dependency at startup for the target component is "essential" (S53: Yes), the result output section 13 determines whether the target component is a group (S54).

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

[0095] On the other hand, if the startup dependency of the target component 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, and when the processing of loop C for all the confirmed target components is completed, the result output unit 13 exits loop C and terminates 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 the startup information display screen when the virtual machine 1 is input as an element to be started, 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.

[0099] The startup information display screen 200 includes a startup target element display area 201 that displays startup target elements, and a startup required element display area 202 that displays elements that must be started as a prerequisite.

[0100] The startup-required element display area 202 displays the elements that need to be started, and if the elements are a group, a list of elements belonging to that group is displayed. In the example of FIG. 10, a list of elements belonging to host group 1 that are necessary for starting virtual machine 1 and a list of elements belonging to virtual storage 1 are displayed. The startup-required element display area 202 also displays the minimum number of elements 202a (e.g., the number of physical servers) required to start the group. The startup-required element display area 202 also displays stop-time element information 202b that can identify elements of the group that constituted the startup target element at the time of shutdown (e.g., servers if the startup target element is a virtual machine). This stop-time element information 202b makes it possible to identify the elements that constituted the startup target element at the time of shutdown. This makes it possible to operate the element in the same state as when it was stopped, thereby making it possible to appropriately prevent resource imbalances, etc.

[0101] Next, a description will be given of a stop information output process for outputting information on other elements that need to be stopped when stopping an element to be stopped.

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

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

[0104] Next, the result output unit 13 performs the processing of loop D (S63 to S64) on each of the confirmed elements as a processing target. Here, the elements as processing targets are referred to as target elements.

[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 level at the time of stopping for the target element is "essential" (S63).

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

[0107] On the other hand, if 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 is completed, 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 is completed, the result output unit 13 exits loop D.

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

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

[0111] On the other hand, if there is a group including the target component (S65: Yes), the result output unit 13 performs the processing of loop E (S66 to S69) for each group including the element to be stopped as the processing target. Here, the group to be processed is referred to as the target group.

[0112] In the processing of loop E, the result output unit 13 determines whether the target group has a minimum required number of elements running even if the element to be stopped is stopped (S66).

[0113] As a result, if it is determined that the minimum required number of elements have not been activated (S66: No), the result output unit 13 checks the elements of which the group is a constituent element from the relevance table 16 (S67).

[0114] Next, the result output unit 13 performs the processing of loop F (S68 to S69) for each of the confirmed elements.

[0115] In the processing of loop F, the result output unit 13 determines whether the dependency at the time of stopping for the element to be processed is "essential" (S68).

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

[0117] On the other hand, if it is determined that the dependency at the time of stopping for the element to be processed is not "essential" (S68: No), the result output unit 13 ends the processing of loop F for the element to be processed.

[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 for the next element to be processed, and when the processing of loop F for all confirmed elements is completed, the result output unit 13 exits loop F.

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

[0120] When loop F is exited, 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 confirmed groups is completed, loop E is exited and the stop information output processing is terminated.

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

[0122] Fig. 12 is a diagram showing a shutdown information display screen according to one embodiment. Shutdown information display screen 300 in Fig. 12 is an example of the shutdown information display screen when physical server 1 is input as an element to be shut down, when relevance table 16 is in the state shown in Fig. 3 and group configuration table 17 is in the state shown in Fig. 4.

[0123] Shutdown information display screen 300 includes a shutdown target element display area 301 that displays elements to be shut down, and a required shutdown element display area 302 that displays elements that must be shut down in advance. In the example of Fig. 12, virtual machine 1 and virtual machine 2 are displayed in the required shutdown element display area 302. In this example, virtual machine 1 is output (displayed) by the processing of step S64, and virtual machine 2 is output by the processing of step S69. This shutdown information display screen makes it possible to appropriately display virtual machines that must be stopped when shutting down a physical server.

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

[0125] For example, in the above embodiment, the dependency relationship regarding stopping and starting is managed, but the present invention is not limited to this, and the dependency relationship regarding either stopping or starting may be managed.

[0126] In the above embodiment, only elements essential for starting the start target element are displayed, but the present invention is not limited to this, and elements related to the start target element (any element) may also be displayed. In addition, although only elements essential for stopping the stop target element are displayed, the present invention is not limited to this, and elements related to the stop target element (any element) may also be displayed.

[0127] In addition, in the above-described embodiments, some or all of the processing performed by the processor may be performed by a hardware circuit. Also, the programs in the above-described embodiments may be installed from a program source. The program source may be a program distribution server or a recording medium (e.g., a portable recording medium). [Explanation of symbols]

[0128] 1...computer system, 10...dependency understanding system, 11...information acquisition unit, 12...information organization unit, 13...result output unit, 14...configuration change detection unit, 15...database, 16...association 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; The processor: acquiring correspondence information between physical elements in the computer system and the virtual machines; A dependency understanding system that identifies a dependency relationship in startup and / or shutdown between the virtual machine and the physical element based on the correspondence information, and stores association information indicating the dependency relationship 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 configure the host group; identifying a host group to which the physical server configuring the virtual machine belongs based on the host group configuration information, identifying a dependency relationship between the virtual machine and the host group in starting and / or stopping, and storing the identified dependency relationship in the storage unit while including it in the relationship information; The host group configuration information is stored in the storage unit. The dependency relationship grasping system according to claim 1 .

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

4. the dependencies include dependencies on invocations; The processor: When the physical server configuring the virtual machine belongs to the host group, the dependency relationship between the virtual machine and the physical server is optional when starting up, and the dependency relationship between the virtual machine and the host group is mandatory when starting up. The dependency relationship grasping system according to claim 2 .

5. The processor: The dependency relationships in the start and / or stop of the elements and / or element groups related to the virtual machine are 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 grasping system according to claim 1 .

6. The processor: Receive notifications of changes to virtual machine configurations, 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, obtain new correspondence relationship information between the managed virtual machine and a physical element in the computer system; The relevance information is updated based on the new correspondence information. The dependency relationship grasping 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 that can identify a physical server that configured 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: Accepts 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 relationship understanding method for a dependency relationship 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, comprising: The dependency relationship understanding system includes: acquiring correspondence information between physical elements in the computer system and the virtual machines; Based on the correspondence relationship 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. 1. A dependency understanding program that causes a computer to execute a process for managing dependencies in starting and / or stopping a physical element and a virtual machine configured by the physical servers in a computer system having a plurality of physical servers, the program comprising: The computer, acquiring correspondence information between physical elements in the computer system and the virtual machines; A dependency understanding program that identifies the dependency relationship in startup and / or shutdown between the virtual machine and the physical element based on the correspondence information, and stores association information indicating the dependency relationship in a memory unit.

Images