JP2016131286A - Verification support program, verification support apparatus, and verification support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To properly acquire information to be used in verification of an information processing system.SOLUTION: A verification support program causes a computer to execute: acquiring information on settings of a plurality of information processing apparatuses 2 and network devices 4-6, from the above apparatuses 2 and devices 4-6, by use of first information identifying each of the information processing apparatuses 2 and network devices 4-6 arranged in an information processing system 1 to be verified; acquiring second information 11c on relationships between the information processing apparatuses 2 and network devices 4-6, on the basis of the acquired information on settings; acquiring third information 11d on one or more information processing apparatuses 2 and network devices 4-6 satisfying a condition for selecting one or more information processing apparatuses 2 and network devices 4-6 to be used in operation verification of the information processing system 1, on the basis of the second information 11c; and outputting the acquired third information 11d to a verification apparatus 20 for operation verification or a device 10.SELECTED DRAWING: Figure 11

Description

  The present invention relates to a verification support program, a verification support apparatus, and a verification support method.

  In systems such as cloud systems that provide various services to users, it is important to provide an “unstoppable” system that can continue to use services even if an abnormality occurs in the time zone that the user (customer) wants to use. .

  For this reason, verification (availability verification) may be performed to confirm that the business does not stop due to the occurrence of a failure in the system. For example, in the availability verification, a process is performed in which an arbitrary device (device) or part of the system is pseudo-faulted and the influence on the user when a pseudo-fault occurs is confirmed and determined.

  In order to obtain an appropriate availability verification result, the relationship between the devices provided in the system is specified, and then a failure point that causes a failure and a point that checks the influence on the user (physical device and VM (Virtual Machine) ) Information) is important. Note that the relationship between devices includes, for example, a role of a VM to be installed, an operation / management / user function, an active / standby system, and the like. For example, an availability verification operator determines the following information based on the relationship between devices as information used for system availability verification and uses it for availability verification.

(A) A service (for example, VM) used by the user.
(B) A physical server on which the VM operates.
(C) A management server (for example, a cloud management server) that manages VMs and physical servers.
(D) A failure point that causes a failure.
(E) Opposite switch facing the failure point (switching to a redundant path).

  The selection of the information (a) to (e) is performed by the operator in the following flow, for example.

  (1) All failure points and points for confirming effects (impact confirmation points) are determined based on the configuration diagram and specifications including information on the devices provided in the system, for example, device name and routing information (configuration).

  (2) Based on the operation logic of the system redundancy function described in the specification, the relationship between the devices is derived, and the items to be actually verified for availability are selected.

  In a relatively large-scale system such as a cloud system, for example, about several tens to several hundreds of devices may be provided for each of a plurality of systems such as one or more user systems, operation systems, and business systems. In such a case, it is difficult to easily specify the items (a) to (e). Therefore, in the above (1), a failure point and an effect confirmation point are determined as expected values for what function of which system in which system is to be broken. And in said (2), the relationship of an apparatus is derived | led-out from the operation logic of a system redundancy function, and the item of said (a)-(e), such as an apparatus which generate | occur | produces a pseudo failure, is determined.

  As a related technology, a technology that extracts instrument information from P & ID (Piping and Instrumentation Drawings), recognizes instrumentation based on knowledge data, and creates a device list. Is known (see, for example, Patent Document 1).

  There is also known a technique for describing the configuration of a virtual network based on information about the configuration and operation state of network devices captured in a database when verifying the characteristics and performance of the network using the virtual network (for example, patents). Reference 2).

  Furthermore, the input equipment configuration diagram of the target plant is interpreted using the knowledge data on the function / structure / operation of the target plant stored as a functional system model, and used for plant management by inferring the relationship between each equipment. There is also known a technique for generating target knowledge (see, for example, Patent Document 3).

JP 11-338903 A JP-A-8-328984 JP-A-6-259108

  In recent years, in a system such as a cloud system, the scale of the system tends to increase and the relationship between devices (between devices) tends to be complicated. When the scale of the system becomes large and the number of devices reaches several hundred to several thousand, it is difficult to specify the relationship of the devices for availability verification by hand such as an operator without omission.

  As an example, when a redundancy function is established by a plurality of operation logics in a large-scale system, the relationships among the respective devices become complicated, and it becomes difficult to specify all the relationships. If the device relationship is specified by mistake due to the occurrence of an omission of the device relationship, etc., the above information (a) to (e) may be incorrect. It is different from what I had.

  In addition, the redundancy state (operation / standby) on the specification may be different from the current redundancy state. In this case, when the failure point (d) and the effect confirmation points (a) to (c) and (e) are determined based on the configuration diagram and the specification, an error in determining the failure point and the effect confirmation point may occur. Due to the occurrence of an indexing error at each point, the above information (a) to (e) becomes incorrect, which makes it difficult not only to perform sufficient availability verification, but also to cause a system malfunction. is there.

  In one aspect, an object of the present invention is to accurately acquire information used for verification of an information processing system.

  In one aspect, the verification support program of this case makes a computer perform the following processes. The processing uses each of the plurality of information processing devices and the plurality of network devices by using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified. Get information about device settings from Further, the processing acquires second information related to the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information related to the setting. Further, the processing is based on the second information, and the third information regarding one or more information processing devices and network devices that satisfy the selection condition of one or more information processing devices and network devices used for operation verification of the information processing system. Get information. Further, the processing outputs the acquired third information to a verification device or the computer that performs the operation verification.

  In one aspect, information used for verification of the information processing system can be accurately acquired.

It is a figure which shows the structural example of the cloud system as an example of one Embodiment. It is a figure explaining an example of the availability verification process by the availability verification apparatus shown in FIG. It is a figure which shows the example of an access of the operation system in the cloud system shown in FIG. FIG. 4 is a diagram illustrating an example of switching to a standby system when a failure occurs in an active system in FIG. 3. It is a figure which shows the function structural example of the verification assistance apparatus shown in FIG. It is a figure which shows an example of the apparatus list information shown in FIG. It is a figure which shows an example of the apparatus detailed information shown in FIG. It is a figure which shows an example of the apparatus detailed information shown in FIG. It is a figure which shows an example of the relationship information shown in FIG. It is a figure which shows an example of the relationship information shown in FIG. It is a figure which shows an example of the production | generation flow of the verification information by the availability verification apparatus shown in FIG. It is a flowchart explaining the operation example of the verification assistance apparatus which concerns on one Embodiment. It is a flowchart explaining the operation example of the production | generation process of the apparatus detailed information regarding the switch which concerns on one Embodiment. It is a flowchart explaining the operation example of the production | generation process of the apparatus detailed information regarding the server which concerns on one Embodiment. It is a flowchart explaining the operation example of the production | generation process of the apparatus detailed information regarding the storage apparatus which concerns on one Embodiment. It is a figure which shows the hardware structural example of the node shown in FIG.

  Embodiments of the present invention will be described below with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude various modifications and technical applications that are not explicitly described below. That is, the present embodiment can be implemented with various modifications without departing from the spirit of the present embodiment. Note that, in the drawings used in the following embodiments, portions denoted by the same reference numerals represent the same or similar portions unless otherwise specified.

[1] One Embodiment [1-1] Configuration Example of Cloud System FIG. 1 is a diagram illustrating a configuration example of a cloud system 1 as an example of an embodiment. As shown in FIG. 1, the cloud system 1 can exemplarily include a plurality of servers 2, a plurality of switches (SW) 4 to 6, a plurality of storage apparatuses 7, a verification support apparatus 10, and an availability verification apparatus 20. .

  The server 2 is a physical server (information processing apparatus) that provides various services by executing an application that runs on an OS (Operating System). In the example of FIG. 1, the servers 2 include management servers 2a and 2b and a plurality of user servers 2c.

  The management servers 2a and 2b perform various management and maintenance in the cloud system 1, such as the SWs 4 to 6, the storage device 7, and the user server 2c (VM 3). An administrator or a maintenance person of the cloud system 1 performs management or maintenance using the management server 2a or 2b. The management servers 2a and 2b may also execute the VM 3, and the management by the management servers 2a and 2b may be executed by the VM 3 operating on the management servers 2a and 2b.

  The management servers 2a and 2b are made redundant. In the example of FIG. 1, the management server 2a is set as the active system and the management server 2b is set as the standby system. Note that the active system is a device that operates normally (operation), and the standby system normally stands by in the idle state or standby (power saving or stopped) state, and operates on behalf of the active system when the active system fails. Equipment.

  The user server 2 c is a server that is connected to each SW 4 and provides various services to the user. For example, the user server 2c executes a plurality (two in FIG. 1) of VMs 3 (VMs 3a and 3b) on the hypervisor or OS and provides them to the user. In FIG. 1, the active user server 2c is taken as an example.

  The VM 3 is a virtual machine provided to the user and provides various services such as a web service to the user. The user can perform various operations such as access to the storage apparatus 7 (active user storages 7b and 7c) using the VM 3 or an application executed on the VM 3.

  SW4 is a switch of a server TOR (Top Of Rack) that is directly connected to the device (server 2). In the example of FIG. 1, SW4 of the server TOR includes business SW4a and 4b used for business, storage SW4c and 4d used for storage, and management SW4e and 4f used for management. These SW4 are made redundant, and the business SW 4a, storage SW 4c, and management SW 4e connected to the management server 2a are active, and the business SW 4b, storage SW 4d, and management SW 4f connected to the management server 2b are standby. Is set.

  The aggregation SW 5 can have a function such as link aggregation that bundles a plurality of physical links and handles them as one logical link. In the example of FIG. 1, the aggregation SW5 includes business aggregation SWs 5a and 5b used for business, storage aggregation SW5c and 5d used for storage, and management aggregation SW5e and 5f used for management. These aggregation SW5 are made redundant, and the same kind of aggregation SW5 are connected to each other. For example, a business aggregation SW 5a, a storage aggregation SW 5c, and a management aggregation SW 5e connected to the business SW 4a, the storage SW 4c, and the management SW 4e are set as the operation system. Further, the business aggregation SW 5b, the storage aggregation SW 5d, and the management aggregation SW 5f connected to the business SW 4b, the storage SW 4d, and the management SW 4f are set as standby systems.

  Although illustration is omitted in FIG. 1 for simplification, the actual cloud system 1 may include several tens of servers 2, a server TOR SW4, a storage TOR SW6, and a storage device 7, which will be described later. is there. The aggregation SW 5 can perform access control (switching) by collectively (aggregating) connections with these devices.

  Further, the business aggregation SWs 5a and 5b and the management aggregation SWs 5e and 5f are connected to an external network (not shown) such as the Internet and other systems, respectively, and can switch access to a route connected to the external network.

  SW6 is a storage TOR switch directly connected to the device (storage device 7). In the example of FIG. 1, SW6a and 6b are mentioned as SW6 of the storage TOR. These SW6 are made redundant, and SW6a connected to the storage aggregation SW5c is set as the active system, and SW6b connected to the storage aggregation SW5d is set as the standby system.

  Each of SW4-6 is preferably a switch having a plurality of ports and having a relatively fast switching performance. Examples of SW4-6 include network devices such as L2 (Layer 2) switches and L3 (Layer 3) switches.

  The storage device 7 is hardware that stores various data, programs, and the like. Examples of the storage device 7 include devices such as RAID (Redundant Arrays of Inexpensive Disks) and storage servers. The storage device 7 can include one or more storage devices such as a magnetic disk device such as an HDD (Hard Disk Drive) and / or a semiconductor drive device such as an SSD (Solid State Drive). In the example of FIG. 1, examples of the storage device 7 include management storages 7a and 7d used for the management servers 2a and 2b, and user storages 7b, 7c, 7e, and 7f used for the user server 2c.

  In addition, the storage apparatus 7 is made redundant. In the example of FIG. 1, the management storage 7a connected to the SW 6a, the user storages 7b and 7c are the operation system, the management storage 7d connected to the SW 6b, and the user. The storages 7e and 7f are set as standby systems. In this case, the data stored in the management storage 7a is copied to the management storage 7d by various methods such as mirroring or snapshot, and the data stored in the user storages 7b and 7c is copied to the user storages 7e and 7f, respectively. Good.

  Furthermore, in the storage apparatus 7, the entire storage area can be logically divided into a plurality of storage areas, and these can be managed by identification information, for example, LUN (Logical Unit Number). For example, the management storages 7a and 7d are each divided into 30 logical storage areas (LUN number = 30), and the user storages 7b, 7c, 7e, and 7f are each 15 logical storage areas (LUN number = 15). ).

  The management servers 2a and 2b, SW4-6, and the storage device 7 are not limited to the numbers and connection relationships illustrated in FIG. 1, and any number may be provided, and other connection relationships may be provided. It is also good. In addition to the server 2, SW 4 to 6, and storage device 7 illustrated in FIG. 1, the storage system 1 switches the access from the operation server 2 to the operation server 2 having an operation function in the storage system 1. The SWs 4 to 6 and the storage device 7 used by the operation server 2 may be provided.

  The verification support apparatus 10 acquires information regarding the relationship between devices in the cloud system 1, determines information used for availability verification of the cloud system 1 based on the information regarding device relationships, and sends the determined information to the availability verification device 20. provide. As an example, the verification support apparatus 10 selects the following information (A) to (E) from information related to the relationship between devices and outputs the selected information to the availability verification apparatus 20. The information (A) to (E) includes an address, such as an IP (Internet Protocol) address. Details of the verification support apparatus 10 will be described later.

(A) VM3 used by the user.
(B) User server 2c on which VM3 operates.
(C) Management server 2a or 2b.
(D) A failure point that causes a failure. For example, at least one of the server 2, SW 4 to 6, the storage device 7, and their components (ports, etc.)
(E) Opposite SWs 4 to 6 that face the failure point (switch to a redundant path).

  The availability verification device 20 uses the information input from the verification support device 10 to perform availability verification on the cloud system 1 according to the procedure illustrated in FIG. Hereinafter, a processing example of availability verification by the availability verification device 20 will be described with reference to FIG.

  As shown in FIG. 2, the availability verification device 20 stores the information (A) to (E) input from the verification support device 10 in a memory or the like, and performs a confirmation process using the information. And the availability verification apparatus 20 performs a determination process using the information obtained by the confirmation process, and outputs the result of the determination process to the worker.

  Here, the confirmation processing includes the following processing. First, the availability verification device 20 performs normal confirmation on each of the devices (A) to (E) input from the verification support device 10. For example, the availability verification device 20 transmits a predetermined command to each address (A) to (E) and determines whether or not a response time to the command is a predetermined threshold value or less. May be performed. In this case, the availability verification device 20 determines that all devices to be verified are normal if the response time is equal to or less than a predetermined threshold, while the device whose response time exceeds the predetermined threshold is abnormal. Judge and end the process.

  When all the devices to be verified are normal, the availability verification device 20 identifies the failure point according to (D) input from the verification support device 10, and simulates the device or its parts with respect to the failure point device. Instruct them to break down. For this instruction, a command for calling (enabling) a function of a pseudo failure for testing or maintenance provided by the server, the switch, or the storage device may be used.

  When a pseudo failure occurs at the failure point, the availability verification device 20 performs confirmation (abnormality confirmation) of the abnormal state of each device (A) to (E). In the abnormality confirmation, for example, the availability verification device 20 accesses (logs in) the server 2, SW 4 to 6, and the storage device 7, and these redundant devices detect an error, so that the operation system changes to the standby system. It is determined whether or not the switching is properly performed.

  Further, the availability verification device 20 confirms the error notification (failure detection message) from each device notified to the management server 2a or 2b of (C). For example, the availability verification device 20 outputs a command or the like that causes the management server 2a or 2b to output an error notification received from another device by the management server 2a or 2b. Then, the availability verification device 20 refers to the error notification from the other device received from the management server 2a or 2b, so that the error notification is transmitted from the appropriate server 2, SW4-6, and storage device 7. To check. This confirmation result is used to determine whether or not the management server 2a or 2b has been appropriately notified with a message indicating that the operation system from the redundant device has been switched to the standby system.

  Here, an example in which the device is switched from the active system to the standby system will be described with reference to FIGS. 3 and 4. In FIG. 3, a thick line arrow indicates a path through which the user server 2c on which the VM 3 is mounted accesses the storage device 7 (user storage 7b). In other words, during normal operation, access is performed through the route of the user server 2c (active system) -storage SW 4c (active system) -storage aggregation SW 5c (active system) -SW 6a (active system) -user storage 7b (active system). .

  In this case, when a pseudo failure occurs in the active storage SW4c that is the failure point, the standby storage SW4d that is the opposite switch operates instead of the storage SW4c as shown in FIG. That is, when a pseudo failure occurs in the storage SW 4c, the user server 2c (active system) -storage SW 4d (standby system) -storage aggregation SW 5d (standby system) -storage aggregation SW 5c (operation system) -SW 6a (operation system) -use Access is performed through the route of the user storage 7b (active system).

  Next, the availability verification device 20 transmits a command instructing the recovery of the pseudo failure to the failure point of (D), and changes the operation state of the failure point from the pseudo failure state to the normal state.

  Then, the availability verification device 20 collects log information such as logs and traces from each of the devices (A) to (E) and stores it in a memory or the like. As a method for collecting log information, there is a method in which the availability verification device 20 transmits a command for outputting log information to each address, and receives log information output from each device. Thus, the confirmation process ends.

  Further, the availability verification device 20 performs a determination process including the following processes based on the log information collected in the confirmation process. At this time, log information related to (A) to (C) and (E) is mainly used as log information of points (effect check points) for checking the influence on the user.

  The availability verification device 20 determines the time (switching time) from when the pseudo failure occurs until the operating SWs 4 to 6 are switched from the active system to the standby system.

  Further, the availability verification device 20 confirms the influence of the occurrence of the pseudo failure on the performance of the VM 3 (for example, a Web service). In this effect confirmation, for example, the response time of the web page may be used as an index indicating how long it takes for the user using the web service to display the web page after the occurrence of the pseudo failure.

  Finally, the availability verification device 20 outputs the switching time and the result of the effect check (response time, etc.) to the worker, and the determination process ends. As a result output method, the result is displayed on the monitor of the availability verification device 20, the e-mail attached with the result is transmitted to the operator, the result is stored in a storage device such as the HDD of the availability verification device 20, or these There are various known methods such as combining the above.

[1-2] Configuration Example of Verification Support Device Next, a configuration example of the verification support device 10 will be described. The verification support device 10 directly or indirectly collects detailed information of devices from a large number of devices arranged on the cloud system 1 and extracts the relationship between the devices in the cloud system 1 to obtain availability (redundancy). This creates information used for verification.

  Here, the relationship between devices may include the following information for each device (server 2, SW4-6, and storage device 7) provided in the cloud system 1.

<SW4-6>
A network system (maintenance / management / business / storage) of a VLAN (Virtual Local Area Network) used.
Location in the cloud system 1 (server TOR / storage TOR / aggregation).
・ Active / standby system.
The type (operation / management / user) of the connected host (server 2).

<Server 2>
The role of the VM 3 installed in the server 2
-Functions for operation / management / user.
・ Active / standby system.
・ Network switching function.
-Server cluster configuration.
LUN group of the connected storage device 7

<Storage device 7>
A disk area storage destination of the VM 3 mounted on the server 2
Configuration information (LUN number, capacity, port address).
The type (operation / management / user) of the connected host (server 2).
-Storage number (how many storages have the corresponding function).

  Details of the relationship between the devices will be described together with each function of the verification support apparatus 10. As illustrated in FIG. 5, the verification support apparatus 10 can include a holding unit 11, an information acquisition unit 12, an information conversion unit 13, a verification information extraction unit 14, and an output unit 15 exemplarily as functional configurations.

  The holding unit 11 is an example of a storage device that stores data. As illustrated in FIG. 5, the holding unit 11 includes a plurality of device list information 11a, a plurality of device detailed information 11b, a plurality of relationship information 11c, and verification information 11d. Hold.

  The information acquisition unit 12 obtains detailed device information (setting information) from each device based on device list information 11a (first information) which is device list information (information for specifying devices) provided in the cloud system 1. Acquired and stored in the holding unit 11 as device detailed information 11b. The device detailed information 11b is information used to create device relationships.

  FIG. 6 shows an example of the device list information 11a. The device list information 11a includes, for example, a host name for identifying a device, an IP address as an example of an address, an ID (Identifier) for logging in to the device, and a password (Password). In the example of FIG. 6, the device list information 11a is an individual file for each of the SWs 4 to 6, the server 2, and the storage device 7 (for example, each mounted rack), but may be a single file.

  The information acquisition unit 12 acquires the detailed information of the device directly or indirectly from the device indicated by the host name using the device list information 11a set by the worker or the like in the verification support apparatus 10. As an example, the information acquisition unit 12 logs in to a device on the cloud system 1 and acquires information related to the setting of the device, so that the function (i1) on the cloud system 1 and the current active / standby system (i2) In addition, information corresponding to the type of device is generated (see FIGS. 7 and 8).

  Hereinafter, a method of creating the device detailed information 11b by the information acquisition unit 12 will be described for each type of device.

<About Device Detailed Information 11b of SW4-6>
(Determination of function i1)
The information acquisition unit 12 takes in data from the device list information 11a, acquires (selects) an IP address of any SW4-6, and logs in to the acquired IP address using an ID and password. Then, the information acquisition unit 12 acquires the configuration information (setting information) of the logged-in SW4-6, determines the VLAN ID or the like in the configuration information, and determines the function (i1) of the SW4-6.

  The cloud system 1 often has a structure in which a network is divided by VLAN or the like for each function. Therefore, the information acquisition unit 12 acquires the configuration information of the SWs 4 to 6 and confirms the VLAN ID (and the tag and untag of the VLAN), so that the functions of the SWs 4 to 6 and the route are used. Is judged.

  For example, when the VLAN ID is 10X (X is an integer from 0 to 9; for example, 100 to 109), the function i1 = management, when the VLAN ID is 20X, i1 = business, when the VLAN ID is 30X, i1 = storage, VLAN If the ID is not set, it can be determined that i1 = maintenance. The correspondence relationship between the value of the VLAN ID and the function is not limited to the above-described example, and the information acquisition unit 12 may recognize an appropriate correspondence relationship depending on the configuration and specifications of the cloud system 1.

(Determination of position i3 in cloud system 1)
The determination of the position (i3) of the SW4-6 in the cloud system 1, that is, whether the SW4-6 is the TOR SW4 and 6 or the aggregation SW5 can be determined by determining the link aggregation setting of the SW4-6. . Whether the TOR SWs 4 and 6 are the server TOR SW 4 or the storage TOR SW 6 can be confirmed from the configuration information of the TOR SWs 4 and 6.

  For example, the information acquisition unit 12 can confirm the link aggregation information of any SW4 to 6 and can determine that the position (i3) is i3 = aggregation if ON and i3 = TOR if OFF. If it is determined that i3 = TOR, the information acquisition unit 12 refers to the configuration information of the TOR SWs 4 and 6 and describes whether the connection destination is the server 2 or the storage device 7 in “port description”. It can be judged from. For example, if the server name is described in “port description”, the information acquisition unit 12 can determine that i3 = server TOR, and if the storage device name is described, i3 = storage TOR.

(Determination of relation i2)
In the operational system / standby system relationship (i2) of the cloud system 1, one of the two systems is designated as the active system, and the opposite side (opposite switch) is designated as the standby system. Therefore, the information acquisition unit 12 acquires data from the device list information 11a, acquires (selects) the IP address of an arbitrary server 2, and logs in to the acquired IP address using an ID and password. Then, the information acquisition unit 12 refers to the setting of the redundancy function of the logged-in server 2 and identifies the aggregation SW 5 that is the monitoring setting target of the active / standby system. For the TOR SWs 4 and 6, the information acquisition unit 12 can identify the active / standby system by recognizing the aggregation SW 5 connected to the SW 4 and 6.

  For example, the information acquisition unit 12 logs into the server 2 and issues a GLS (Global Link Services) command for confirming the setting of the redundancy function to the logged-in server 2. Thereby, it is possible to determine whether or not the aggregation SW 5 connected to the server 2 is an active switch. As an example, the information acquisition unit 12 can determine that the relationship i2 = active system when the aggregation SW5 is an active system and i2 = standby system when the aggregation SW5 is a standby system.

  Further, the information acquisition unit 12 checks the configuration information of the TOR SW4 and 6 for the TOR SW4 and 6 of the i3 = server TOR or storage TOR, and determines whether or not it is connected to the operational system of the aggregation SW5. To do. As a result, the information acquisition unit 12 determines that i2 = active system if TOR SW4 and 6 are connected to the operating system of aggregation SW5, and i2 = standby system if TOR SW4 and 6 are connected to the standby system of aggregation SW5. It can be judged.

  When i1 = maintenance, the SWs 4 to 6 are server TORs, and there are many cases where there is no standby system and only the active system. Therefore, the information acquisition unit 12 determines i2 = active system as the active / standby system (i2) for SW4 to 6 determined as i1 = maintenance, and i3 = server as the position (i3) in the cloud system 1 You may judge it as TOR.

(Determination of connection system i4)
The information acquisition unit 12 compares the name of the higher-level connection server 2 obtained from the configuration information of SW4 to SW6 with the server name obtained from the device list information 11a, so that the server 2 is managed system, user system, operational system It is possible to determine the connection system (i4). For example, the information acquisition unit 12 determines whether or not the management servers 2a and 2b exist in the higher level connection server 2 from the configuration information of the SW4 to SW6, and if it exists, i4 = management system as the connection system (i4). Judgment can be made. In addition, it is determined whether or not the user server 2c exists in the host connection server 2, and if it exists, it can be determined that i4 = user system as the connection system (i4). Further, if none of the management servers 2a and 2b and the user server 2c exists in the higher level connection server 2, it can be determined that i4 = active system.

  The information acquisition unit 12 creates the detailed information of the SW4 to 6 acquired as described above as the device detailed information 11b together with the contents of the device list information 11a of the SW4 to 6 (see FIG. 7) and saves it in the holding unit 11 To do.

<Server 2>
(Determination of function i1)
The information acquisition unit 12 takes in data from the device list information 11a, acquires (selects) the IP address of an arbitrary server 2, and logs in to the acquired IP address using an ID and password. And the information acquisition part 12 determines the function of the server 2 by acquiring ID (VMID) of VM mounted in the server 2 which logged in, and determining the said VMID.

  For example, the information acquisition unit 12 may use i1 = management if the VMID is a special VMID for the management VM, i1 = operation if the VMID is a VMID unified for the operator, and the VMID may be a random VMID unique to the user. I1 = user. Note that the VMID arrangement is not limited to the above example, and the information acquisition unit 12 may recognize an appropriate correspondence according to the operation of the VM (VM3) in the cloud system 1 or the like.

(Determination of relation i2)
The information acquisition unit 12 confirms the redundant function by transmitting an operation / standby confirmation command such as PCL (PPAR (Physical Partition) configuration list) or HAproxy to the server 2.

  For example, the information acquisition unit 12 can determine that i2 = active system when the response to the confirmation command indicates the active side, and i2 = standby system when the response to the confirmation command indicates the standby side.

(Determination of installed VM type i3)
The information acquisition unit 12 confirms the OS type (i3) of the VM 3 installed in the server 2 by a command of the hypervisor of the VM 3. For example, the information acquisition unit 12 may determine that i3 = RHEL (Red Hat Enterprise Linux (registered trademark)), i3 = SuSE, i3 = Windows (registered trademark) Server 2012 according to the response content to the command. it can.

(Determination of disk storage location i4)
The information acquisition unit 12 can confirm the connection between the VMID and the virtual disk by the VM 3 (management VM 3) operating on the management servers 2a and 2b, and determine the storage location (i4) of the disk. For example, the information acquisition unit 12 refers to a virtual disk allocation table to the VM 3 and the like, based on the correspondence between the VMID and the virtual disk, i4 = management storage operation system, i4 = user storage standby system 1, i4 = use The storage storage such as the user storage standby system 2 can be determined.

  The information acquisition unit 12 creates the detailed information of the server 2 acquired as described above as the device detailed information 11b together with the contents of the device list information 11a of the server 2 (see FIG. 7), and stores it in the holding unit 11.

<Storage device 7>
(Determination of function i1)
The information acquisition unit 12 takes in data from the device list information 11a and the device detailed information 11b related to the server 2, and acquires (selects) the IP addresses of the arbitrary storage device 7, the arbitrary user server 2c, and the arbitrary management servers 2a and 2b. ) Then, the information acquisition unit 12 logs in to the acquired user server 2c and the management servers 2a and 2b using the ID and password, and determines whether or not the acquired storage device 7 exists at each access destination. Thus, the function of the storage device 7 is determined.

  For example, when the storage device 7 is set as the access destination in the user server 2c, the information acquisition unit 12 is i1 = user, and when the storage device 7 is set as the access destination in the management servers 2a and 2b. Can be determined as i1 = management.

(Determination of relation i2)
The information acquisition unit 12 logs in to the server 2 in which the storage device 7 is detected by the determination of the function i1, and checks whether the storage device 7 is an active system. For example, the information acquisition unit 12 can determine that if the storage device 7 set in the server 2 is an active system, i2 = active system, and if the storage system 7 is a standby system, i2 = standby system.

(Determination of storage number i3)
The information acquisition unit 12 logs into the server 2 in which the storage device 7 is detected by the determination of the function i1, and confirms the storage number of the storage device 7, that is, the number of the storage device 7 having the corresponding function. For example, the information acquisition unit 12 can determine that i3 = 1 if the storage number is 1, and i3 = 2 if the storage number is 2.

(Determination of LUN number i4)
The information acquisition unit 12 logs into the server 2 where the storage device 7 is detected by the determination of the function i1, issues a confirmation command for confirming the number of LUNs to the server 2, and determines the number of LUNs from the response content to the confirmation command. To do. For example, the information acquisition unit 12 can determine that i4 = 30 if the number of LUNs is 30, and i4 = 15 if the number of LUNs is 15.

  The information acquisition unit 12 creates the detailed information of the storage device 7 acquired as described above as the device detailed information 11b together with the contents of the device list information 11a of the storage device 7 (see FIG. 8), and saves it in the holding unit 11 To do.

  The device detailed information 11b is an individual file for each of SW4-6, the server 2, and the storage device 7 (for example, each mounted rack) in the examples of FIGS. 7 and 8, but is a single file. Also good.

  Returning to the description of FIG. 5, the information conversion unit 13 converts the device detail information 11 b generated by the information acquisition unit 12 into device relationship information 11 c (second information) in a format that can be used by the availability verification device 20. Convert. The relationship information 11c is information in which a list of device types is associated with a list of unique roles focusing on the redundant configuration in the cloud system 1.

  9 and 10 show an example of the relationship information 11c. The relationship information 11c includes, for example, an IP address as an example of an address and the role of the device having the IP address. For example, the information conversion unit 13 extracts the detailed information of i1 to i4 in the device detailed information 11b for each IP address, and connects each of i1 to i4 with a semicolon (;), thereby converting the device detailed information 11b to the relationship information 11c. Can be converted to The “role” in which each of i1 to i4 in the relationship information 11c is connected by a semicolon (;) is easy to compare with the failure point and the effect confirmation point defined in advance in the availability verification device 20 (easy to search and analyze It is converted to a format that is easy to do. The “role” is not limited to the above-described format, and may be expressed in various formats.

  Note that the relationship information 11c is an individual file for each of the SW4 to SW6, the server 2, and the storage device 7 (for example, each mounted rack) in the examples of FIGS. Also good.

  As described above, the information acquisition unit 12 and the information conversion unit 13 confirm redundancy for each of the server 2, SW 4 to 6, and the storage device 7 provided in the cloud system 1 and acquire information used for availability verification. By checking the status for this purpose, the relationship between the devices of the entire system is created.

  In other words, the information acquisition unit 12 and the information conversion unit 13 use the device list information 11a (first information), and information related to setting of devices (devices) from each of the plurality of servers 2 and the plurality of SWs 4 to 6. It can be said that it is an example of the 1st acquisition part which acquires the relationship information 11c (2nd information) regarding the relationship of an apparatus based on the acquired information. At this time, the information acquisition unit 12 and the information conversion unit 13 as the first acquisition unit determine each operation state or standby state of the redundant device based on the detailed information of the device, and determine the operation state or standby state. The relationship information 11c is acquired based on the determination result.

  The verification information extraction unit 14 extracts information to be output to the availability verification device 20 from the relationship information 11c converted (created) by the information conversion unit 13 to create verification information 11d (third information), and a holding unit 11. For example, the verification information extraction unit 14 acquires information on failure points and influence confirmation points defined in advance in the availability verification device 20 from the availability verification device 20. This predefined failure point and impact confirmation point information is the failure point and impact confirmation point as the expected value of which function of which system in which system determined by the operator etc. Information representing a role. An example of failure points and influence confirmation points as expected values (an example of selection conditions) is shown below.

(Failure point)
A storage SW (operation system) (4c) of the server TOR connected to the user system server (2c in FIG. 1).

(Effect confirmation point)
An active user server (2c).
-VM (3a, 3b) operating on the user server.
An active management server (2a).
Storage SW of server TOR connected to user system server (standby system: opposite SW of failure point) (4d).

  The role of the failure point and the effect confirmation point as the expected value is obtained by connecting each of i1 to i4 shown in FIG. 7 and FIG. 8 with a semicolon (;) like the role of the relationship information 11c in FIG. 9 and FIG. It is a character string.

  The verification information extraction unit 14 obtains such a character string as an expected value from the availability verification apparatus 20, and thereby plays a role that matches the expected value that is awaited (requested) by the availability verification apparatus 20. 11c can be searched. When the verification information extraction unit 14 detects a role that matches the expected value from the relationship information 11c by the search, the verification information extraction unit 14 extracts the IP address of the device corresponding to the role and stores it in the holding unit 11 as verification information 11d. It is. The availability verification device 20 can perform the above-described availability verification by taking in as input an IP address of a device having a role that matches such an expected value.

  An example of the verification information 11d created by the verification information extraction unit 14 is shown in FIG. As illustrated in FIG. 11, the verification information 11 d includes IP addresses that match the conditions (failure point (D) and impact confirmation points (A) to (C) and (E)) as expected values. It becomes the information associated (fitted) with (E).

  As described above, the verification information extraction unit 14 is based on the relationship information 11c (second information), and includes one or more servers 2 and SW4 that satisfy the selection conditions for one or more devices used for operation verification of the cloud system 1. 6 is an example of the second acquisition unit that acquires the verification information 11d (third information) related to 6. At this time, the verification information extraction unit 14 as the second acquisition unit extracts one or more servers 2 and SWs 4 to 6 having a role satisfying the selection condition from the relationship information 11c, and specifies information for identifying each extracted information. The verification information 11d is generated.

  The output unit 15 reads the verification information 11 d generated by the verification information extraction unit 14 from the holding unit 11 and outputs it to the availability verification device 20.

  As described above, according to the verification support apparatus 10 that extracts a unique role of a device, the current failure point can be obtained by systematizing the device information and the method for confirming the redundancy function and executing the processing. The confirmation point can be determined without omission, and the information used for verification of the cloud system 1 can be accurately acquired.

  Accordingly, the relationship between devices can be accurately derived in a large-scale and complex system such as the cloud system 1 and the input information given to the availability verification device 20 can be reliably generated without omission. Realization of availability verification.

  Further, the verification support apparatus 10 not only obtains information from the configuration diagram, specifications, etc., but also actually logs in to the device (transmits a command) as shown in FIG. Generate a relationship. Thereby, since the information of the redundancy state of the apparatus which changes in real time can be acquired, the role of the current apparatus can be specified accurately.

[1-3] Operation Example Next, an operation example of the verification support apparatus 10 in the cloud system 1 configured as described above will be described with reference to FIGS.

[1-3-1] Overall Processing First, overall processing (verification information generation processing) by the verification support apparatus 10 will be described with reference to FIG. It is assumed that the device list information 11a is set in the holding unit 11 as a premise.

  First, the information acquisition unit 12 acquires detailed information of each device based on the device list information 11a, generates device detailed information 11b (step S1), and stores it in the holding unit 11. Details of the processing in step S1 will be described later.

  Next, the information conversion unit 13 converts the device detailed information 11b into the relationship information 11c in a format corresponding to the request (request) from the availability verification device 20 (step S2). In this conversion process, the information conversion unit 13 combines the detailed information of i1 to i4 in the device detailed information 11b to obtain information representing a unique “role” of the device.

  The verification information extraction unit 14 acquires the failure point and influence confirmation point conditions as expected values from the availability verification device 20 (step S3). The acquisition of this condition may be received together with a request for verification information 11d from the availability verification device 20, for example. Note that the process of step S3 may be performed before or after step S1 or S2, or may be performed in parallel with the processes of steps S1 and S2.

  Next, the verification information extraction unit 14 determines a device that matches the condition from the availability verification device 20 based on the relationship information 11c, and determines the IP address of the device that matches the condition as the condition (failure point and impact check point). The associated verification information 11d is generated (step S4) and stored in the holding unit 11.

  Finally, the output unit 15 outputs the verification information 11d to the availability verification device 20 (step S5), and the process ends.

  Next, with reference to FIG. 13 to FIG. 15, the generation processing of the device detailed information 11b by the information acquisition unit 12 will be described. Hereinafter, for the sake of convenience, the generation processing of the device detailed information 11b will be described for each type of device. However, in practice, the information acquisition unit 12 adds a record of the device detailed information 11b for each device without considering the type of device. The generation processing can be executed in various orders.

[1-3-2] Generation processing of device detailed information related to SW First, generation processing of device detailed information 11b related to SW4 to SW6 will be described with reference to FIG. The information acquisition unit 12 acquires a and b from the device list information 11a of SW4 to 6 and server 2 by setting the IP address of any SW4 to 6 as a and the IP address of any server 2 as b (step S11). (Step S12).

  Next, the information acquisition unit 12 logs in the SWs 4 to 6 of a, acquires configuration information (step S13), determines the VLAN ID, and sets i1 in the device detailed information 11b (step S14). When it is determined in step S14 that i1 = maintenance (step S15, Yes route in step S15), the information acquisition unit 12 sets i2 = active system and i3 = server TOR in the device detailed information 11b (step S16), and processing Goes to step S17.

  In step S17, the information acquisition unit 12 confirms the server 2 connected to the upper level of SWs 4 to 6 of a from the configuration setting, and determines whether it is the management server 2a or 2b (step S18). When the upper server 2 is the management server 2a or 2b (Yes route in step S18), the information acquisition unit 12 sets i4 = management server system in the device detailed information 11b (step S19), and the next a exists. Whether or not (step S20).

  When the next a exists (Yes route in step S20), the process proceeds to step S12, and the information acquisition unit 12 acquires the next a and b from the device list information 11a. On the other hand, when the next a does not exist in Step S20 (No route of Step S20), the information acquisition unit 12 determines whether or not a being saved exists in the holding unit 11 (Step S21). If there is no a being saved in the holding unit 11 (No route in step S21), the process ends.

  On the other hand, in step S18, when the upper server 2 is not the management server 2a or 2b (No route in step S18), the information acquisition unit 12 determines whether the upper server 2 is the user server 2c (step S18). S22). When the upper server 2 is the user server 2c (Yes route in step S22), the information acquisition unit 12 sets i4 = user server system in the device detailed information 11b (step S23), and the process proceeds to step S20. To do. If the upper server 2 is not the user server 2c (No route in step S22), the information acquisition unit 12 sets i4 = operation server system in the device detailed information 11b (step S24), and the process proceeds to step S20. Transition.

  Here, in step S15, when it is not determined that i1 = maintenance in step S14 (No route in step S15), the information acquisition unit 12 confirms the link aggregation setting in a, and determines whether or not it is the aggregation SW5. Is determined (step S25). In the case of aggregation SW5 (Yes route in step S25), the information acquisition unit 12 sets i3 = aggregation in the device detailed information 11b (step S26), logs in to the server 2 in b, and makes a redundancy function by a GLS command. Is confirmed (step S27).

  When it is determined that the aggregation SW 5 is the active system by checking the setting of the redundancy function (step S28, Yes route of step S28), the information acquisition unit 12 sets i2 = active system in the device detailed information 11b ( In step S29), the process proceeds to step S17. On the other hand, when the aggregation SW 5 is not the active system (the standby system) (No route in step S28), the information acquisition unit 12 sets i2 = standby system in the device detailed information 11b (step S30), and the processing is performed in steps. The process proceeds to S17.

  If it is determined in step S25 that the SWs 4 to 6 of a are not the aggregation SW5 (No route in step S25), the information acquisition unit 12 checks the “port description” in the configuration information (step S31). It is determined whether or not the connection destination of a is the server 2 (step S32).

  When the connection destination of a is the server 2 (Yes route in step S32), the information acquisition unit 12 sets i3 = server TOR in the device detailed information 11b (step S33), and the process proceeds to step S35. On the other hand, when the connection destination of a is not the server 2 (No route in step S32), the information acquisition unit 12 sets i3 = storage TOR in the device detailed information 11b (step S34), and the process proceeds to step S35. .

  In step S35, the information acquisition unit 12 determines whether or not the aggregation SW 5 connected to a has already been determined. If the determination is not made for the aggregate SW5 connected to a (No route in step S35), the information for performing the determination of i2 is insufficient. The acquisition unit 12 saves a in the holding unit 11 (step S36), and the process proceeds to step S20.

  Note that the determination on a interrupted here is resumed when it is determined in step S21 that the information acquisition unit 12 determines that a is being saved in the holding unit 11 (Yes route in step S21). In this case, the information acquisition unit 12 reads a saved in the holding unit 11 (step S37), and the process proceeds to step S35.

  If it is determined in step S35 about the aggregation SW5 connected to a (Yes route in step S35), the information acquisition unit 12 determines whether the aggregation SW5 is an active system (step S38). If the aggregation SW 5 is the active system (Yes route in step S38), the information acquisition unit 12 sets i2 = active system in the device detailed information 11b (step S39), and the process proceeds to step S17. On the other hand, when the aggregation SW 5 is not the active system (the standby system) (No route in step S38), the information acquisition unit 12 sets i2 = standby system in the device detailed information 11b (step S40), and the process is step. The process proceeds to S17.

  With the above processing, the generation processing of the device detailed information 11b related to SW4 to 6 ends.

[1-3-3] Generation Processing of Device Detailed Information Related to Server Next, generation processing of device detailed information 11b related to the server 2 will be described with reference to FIG. The information acquisition unit 12 sets a as the IP address of an arbitrary server 2 (step S41), and acquires a from the device list information 11a of the server 2 (step S42).

  Next, the information acquisition unit 12 logs into the server 2 of a, acquires the VMID of the VM mounted on the server 2 (step S43), determines the VMID, and sets i1 in the device detailed information 11b (step S43). S44).

  In addition, the information acquisition unit 12 confirms the redundant function of the server 2 by an operation / standby confirmation command (step S45). When the server 2 is an active system (step S46, Yes route of step S46), the information acquisition unit 12 sets i2 = active system in the device detailed information 11b (step S47), and the process proceeds to step S49. On the other hand, if the server 2 is not the active system (the standby system) (No route in step S46), the information acquisition unit 12 sets i2 = standby system in the device detailed information 11b (step S48), and the process is step. The process proceeds to S49.

  In step S49, the information acquisition unit 12 confirms and determines the OS type of the installed VM3 by using a command of the hypervisor of the VM3, and sets i3 in the device detailed information 11b.

  Further, the information acquisition unit 12 confirms the connection between the VMID and the virtual disk by the management VM 3, sets i4 in the device detailed information 11b (step S50), and determines whether or not the next a exists (step S50). Step S51).

  When the next a exists (Yes route in step S51), the process proceeds to step S42, and the information acquisition unit 12 acquires the next a from the device list information 11a. On the other hand, when the next a does not exist in step S51 (No route in step S51), the process ends.

  With the above processing, the generation processing of the device detailed information 11b related to the server 2 is completed.

[1-3-4] Generation processing of device detailed information related to the storage device Next, generation processing of device detailed information 11b related to the storage device 7 will be described with reference to FIG. The information acquisition unit 12 sets the IP address of any storage device 7 as a, the IP address of any user server 2c as b, and the IP addresses of any management servers 2a and 2b as c (step S61). A, b, and c are acquired from 11a (step S62).

  Next, the information acquisition unit 12 logs in to the servers 2 of b and c, respectively, and confirms the presence or absence of the address of a (whether or not a exists at the access destination) (step S63). When the server 2 in which the address of a exists is b (step S64, Yes route of step S64), the information acquisition unit 12 sets i1 = user in the device detailed information 11b (step S65), and the process is step. The process proceeds to S67. On the other hand, if the server 2 in which the address a exists is not b (is c) (No route in step S64), the information acquisition unit 12 sets i1 = management in the device detailed information 11b (step S66). The process proceeds to step S67.

  In step S67, the information acquisition unit 12 logs in to the server 2 in which the address a exists and confirms the setting of the redundancy function (step S67). When the server 2 is an active system (step S68, Yes route of step S68), the information acquisition unit 12 sets i2 = active system in the device detailed information 11b (step S69), and the process proceeds to step S71. On the other hand, when the server 2 is not the active system (the standby system) (No route in step S68), the information acquisition unit 12 sets i2 = standby system in the device detailed information 11b (step S70), and the process is step. The process proceeds to S71.

  In step S71, the information acquisition unit 12 logs in to the server 2 where the address a exists, confirms the storage number a, and sets i3 in the device detailed information 11b.

  Further, the information acquisition unit 12 logs in to the server 2 where the address a exists, executes the LUN number confirmation command, sets i4 in the device detailed information 11b (step S72), and the next a exists. Whether or not (step S73).

  When the next a exists (Yes route in step S73), the process proceeds to step S62, and the information acquisition unit 12 acquires the next a, b, and c from the device list information 11a. On the other hand, when the next a does not exist in step S73 (No route in step S73), the process ends.

  With the above processing, the generation processing of the device detailed information 11b related to the storage device 7 is completed.

  Note that the order in which the information acquisition unit 12 sets i1 to i4 of the device detailed information 11b is not limited to that illustrated in FIGS. 13 to 15 and may be any order.

[1-4] Hardware Configuration Example The server 2, the verification support apparatus 10, and the availability verification apparatus 20 described above may be realized by a computer (information processing apparatus) such as a server. A hardware configuration example of the server 2, the verification support apparatus 10, and the availability verification apparatus 20 is shown in FIG. Since the server 2, the verification support apparatus 10, and the availability verification apparatus 20 can all have the same hardware, a hardware configuration example of the verification support apparatus 10 will be described as a representative. Further, the verification support apparatus 10 and the availability verification apparatus 20 may be the same server or the like.

  As shown in FIG. 16, the verification support apparatus 10 can include a CPU (Central Processing Unit) 10a, a memory 10b, a storage device 10c, an interface unit 10d, an input / output unit 10e, and a reading unit 10f.

  The CPU 10a is an example of an arithmetic processing device (processor) that performs various controls and arithmetic operations. The CPU 10a is communicably connected to the corresponding blocks 10b to 10f via a bus, and executes a program stored in a memory 10b, a storage device 10c, a recording medium 10g, a ROM (Read Only Memory) (not shown), or the like. As a result, various functions can be realized.

  The memory 10b is a storage device that stores various data and programs. When executing the program, the CPU 10a stores and develops data and programs in the memory 10b. The memory 10b may be a volatile memory such as a RAM (Random Access Memory).

  The storage device 10c is hardware that stores various data, programs, and the like. Examples of the storage device 10c include various devices such as a magnetic disk device such as an HDD, a semiconductor drive device such as an SSD, and a nonvolatile memory such as a flash memory and a ROM.

  For example, the storage device 10c can store a verification support program 100 that realizes all or some of the various functions of the verification support device 10. The CPU 10a can realize the function of the verification support apparatus 10 by developing the verification support program 100 stored in the storage device 10c, for example, on a storage device such as the memory 10b and executing it. Similarly, the server 2 and the availability verification device 20 can also store the server program and the availability verification program in the respective storage devices, and the CPU 2 expands and executes these programs in the memory to execute the server 2 and The function of the availability verification device 20 can be realized.

  Note that the holding unit 11 illustrated in FIG. 5 may be realized by the memory 10b or the storage device 10c. In the example of FIG. 16, the memory 10b is shown as being capable of holding the device list information 11a, the device detailed information 11b, the relationship information 11c, and the verification information 11d as the holding unit 11.

  The interface unit 10d is a communication interface that performs connection and communication control between the SWs 4 to 6, the storage device 7, the server 2, the availability verification device 20, and the like by wire or wireless. As the interface unit 10d, for example, an adapter conforming to a wired or wireless LAN or the like can be cited.

  The input / output unit 10e includes at least one of an input device (operation unit) such as a mouse, a keyboard, a touch panel, a microphone for voice operation, and an output device (output unit, display unit) such as a display, a speaker, and a printer. be able to. For example, the input device may be used for operations such as various operations and data input by an operator, and the output device may be used for outputting various notifications.

  The reading unit 10f is a device that reads data and programs recorded on a computer-readable recording medium 10g. The verification support program 100 may be stored in the recording medium 10g. Similarly, for the server 2 and the availability verification device 20, a server program and an availability verification program may be stored and provided in the recording medium, respectively.

  Examples of the recording medium 10g include optical disks such as a flexible disk, CD, DVD, and Blu-ray disk, and flash memories such as a USB memory and an SD card. Examples of the CD include CD-ROM, CD-R, CD-RW and the like. Examples of the DVD include non-temporary recording media such as DVD-ROM, DVD-RAM, DVD-R, DVD-RW, DVD + R, and DVD + RW.

  The hardware configuration of the verification support apparatus 10 described above is an example. Therefore, hardware increase / decrease in the verification support apparatus 10 (for example, addition or omission of arbitrary blocks), division, integration in an arbitrary combination, addition or omission of buses, etc. may be performed as appropriate.

  So far, the verification support apparatus 10 and the availability verification apparatus 20 have been described as being separate apparatuses, but the present invention is not limited to this. For example, the verification support apparatus 10 and the availability verification apparatus 20 may be realized by a single apparatus (information processing apparatus; computer) that executes the verification support program and the availability verification program. In this case, the output of the verification information 11d from the verification support apparatus 10 to the availability verification apparatus 20 can be performed by outputting data from the verification support program to the availability verification program in one apparatus. Further, in order to exchange data between the verification support program and the availability verification program, the holding unit 11 may be referred (shared) by both programs.

  Further, the server 2 may execute at least one of the verification support program and the availability verification program.

  Moreover, although the verification assistance apparatus 10 demonstrated as what extracts the information used for the availability verification of the cloud system 1, it is not limited to this. The system to be verified is not limited to the cloud system 1 and can be various systems. In addition, the verification support apparatus 10 can be applied to operation verification other than availability verification to perform accurate operation verification.

[2] Others While the preferred embodiment of the present invention has been described in detail above, the present invention is not limited to such a specific embodiment, and various modifications and changes can be made without departing from the spirit of the present invention. It can be changed and implemented.

  For example, the functional blocks of the verification support apparatus 10 illustrated in FIG. 5 may be merged in an arbitrary combination or may be divided.

  Further, at least one of the verification support apparatus 10 and the availability verification apparatus 20 may be an apparatus provided outside the cloud system 1. In this case, access to the cloud system 1 by the verification support apparatus 10 and the availability verification apparatus 20 is performed using various communication methods such as Telnet (Teletype network), SSH (Secure Shell), or VPN (Virtual Private Network). May be.

[3] Supplementary Notes Regarding the above embodiment, the following supplementary notes are further disclosed.

(Appendix 1)
On the computer,
Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified And acquiring second information regarding the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information regarding the setting,
Based on the second information, obtain third information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system,
Outputting the acquired third information to a verification device or the computer for performing the operation verification;
A verification support program characterized by causing processing to be executed.

(Appendix 2)
The first information includes addresses of the plurality of information processing devices and the plurality of network devices,
The second information includes a correspondence relationship between the addresses of the plurality of information processing devices or the plurality of network devices and the roles of the plurality of information processing devices corresponding to the addresses or the roles of the plurality of network devices. ,
The selection condition includes a role of the one or more information processing devices and network devices used for the operation verification,
The third information includes addresses of the one or more information processing devices and network devices that satisfy the selection condition.
The verification support program according to supplementary note 1, characterized by that.

(Appendix 3)
The second information includes information representing roles of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the third information, one or more information processing devices and network devices having a role satisfying the selection condition are extracted from the second information, and each of the extracted one or more information processing devices and network devices is extracted. Generating information for specifying the third information,
The verification support program according to supplementary note 1 or supplementary note 2, characterized by that.

(Appendix 4)
The information regarding the setting includes information regarding redundancy of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the second information, the operating state or standby state of each of the plurality of redundant information processing devices and the plurality of network devices is determined based on the information related to the setting, and the operating state or standby state is determined. Obtaining the second information based on the determination result of the state;
The verification support program according to any one of appendices 1 to 3, characterized in that:

(Appendix 5)
Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified A first acquisition unit that acquires second information related to the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information related to the setting;
Based on the second information, second information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system is acquired. An acquisition unit;
An output unit that outputs the third information acquired by the second acquisition unit to the verification device that performs the operation verification or the device itself;
A verification support apparatus characterized by that.

(Appendix 6)
The first information includes addresses of the plurality of information processing devices and the plurality of network devices,
The second information includes a correspondence relationship between the addresses of the plurality of information processing devices or the plurality of network devices and the roles of the plurality of information processing devices corresponding to the addresses or the roles of the plurality of network devices. ,
The selection condition includes a role of the one or more information processing devices and network devices used for the operation verification,
The third information includes addresses of the one or more information processing devices and network devices that satisfy the selection condition.
The verification support device according to appendix 5, characterized in that:

(Appendix 7)
The second information includes information representing roles of the plurality of information processing devices and the plurality of network devices,
The second acquisition unit extracts one or more information processing devices and network devices having a role satisfying the selection condition from the second information, and specifies each of the extracted one or more information processing devices and network devices. Information to be generated as the third information,
The verification support apparatus according to Supplementary Note 5 or Supplementary Note 6, wherein

(Appendix 8)
The information regarding the setting includes information regarding redundancy of the plurality of information processing devices and the plurality of network devices,
The first acquisition unit determines an operation state or a standby state of each of the plurality of redundant information processing devices and the plurality of network devices based on the information related to the setting, and determines the operation state or the standby state. Obtaining the second information based on the determination result;
The verification support apparatus according to any one of appendix 5 to appendix 7, characterized by:

(Appendix 9)
Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified And acquiring second information regarding the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information regarding the setting,
Based on the second information, obtain third information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system,
Outputting the acquired third information to the verification device or the own device for performing the operation verification;
A verification support method characterized by that.

(Appendix 10)
The first information includes addresses of the plurality of information processing devices and the plurality of network devices,
The second information includes a correspondence relationship between the addresses of the plurality of information processing devices or the plurality of network devices and the roles of the plurality of information processing devices corresponding to the addresses or the roles of the plurality of network devices. ,
The selection condition includes a role of the one or more information processing devices and network devices used for the operation verification,
The third information includes addresses of the one or more information processing devices and network devices that satisfy the selection condition.
The verification support method according to appendix 9, characterized in that:

(Appendix 11)
The second information includes information representing roles of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the third information, one or more information processing devices and network devices having a role satisfying the selection condition are extracted from the second information, and each of the extracted one or more information processing devices and network devices is extracted. Generating information for specifying the third information,
The verification support method according to supplementary note 9 or supplementary note 10, characterized in that.

(Appendix 12)
The information regarding the setting includes information regarding redundancy of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the second information, the operating state or standby state of each of the plurality of redundant information processing devices and the plurality of network devices is determined based on the information related to the setting, and the operating state or standby state is determined. Obtaining the second information based on the determination result of the state;
The verification support method according to any one of Supplementary Note 9 to Supplementary Note 11, which is characterized in that.

1 Cloud system (information processing system)
2 Server 2a, 2b Management server 2c User server 3, 3a, 3b VM
4, 6, 6a, 6b switch 4a, 4b business switch 4c, 4d storage switch 4e, 4f management switch 5 aggregation switch, switch 5a, 5b business aggregation switch 5c, 5d storage aggregation switch 5e, 5f management aggregation switch 7 storage device 7a , 7d Management storage 7b, 7c, 7e, 7f User storage 10 Verification support device 11 Holding unit 11a Device list information 11b Device detailed information 11c Relationship information 11d Verification information 12 Information acquisition unit 13 Information conversion unit 14 Verification information extraction unit 15 Output unit 20 Availability verification device

Claims (6)

On the computer,
Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified And acquiring second information regarding the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information regarding the setting,
Based on the second information, obtain third information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system,
Outputting the acquired third information to the verification device or the computer for performing the operation verification;
A verification support program characterized by causing processing to be executed. The first information includes addresses of the plurality of information processing devices and the plurality of network devices,
The second information includes a correspondence relationship between the addresses of the plurality of information processing devices or the plurality of network devices and the roles of the plurality of information processing devices corresponding to the addresses or the roles of the plurality of network devices. ,
The selection condition includes a role of the one or more information processing devices and network devices used for the operation verification,
The third information includes addresses of the one or more information processing devices and network devices that satisfy the selection condition.
The verification support program according to claim 1, wherein: The second information includes information representing roles of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the third information, one or more information processing devices and network devices having a role satisfying the selection condition are extracted from the second information, and each of the extracted one or more information processing devices and network devices is extracted. Generating information for specifying the third information,
The verification support program according to claim 1 or 2, characterized in that: The information regarding the setting includes information regarding redundancy of the plurality of information processing devices and the plurality of network devices,
In the acquisition of the second information, the operating state or standby state of each of the plurality of redundant information processing devices and the plurality of network devices is determined based on the information related to the setting, and the operating state or standby state is determined. Obtaining the second information based on the determination result of the state;
The verification support program according to any one of claims 1 to 3, wherein Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified A first acquisition unit that acquires second information related to the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information related to the setting;
Based on the second information, second information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system is acquired. An acquisition unit;
An output unit that outputs the third information acquired by the second acquisition unit to the verification device that performs the operation verification or the device itself;
A verification support apparatus characterized by that. Device setting from each of the plurality of information processing devices and the plurality of network devices, using first information specifying each of the plurality of information processing devices and the plurality of network devices provided in the information processing system to be verified And acquiring second information regarding the relationship between the plurality of information processing devices and the plurality of network devices based on the acquired information regarding the setting,
Based on the second information, obtain third information on one or more information processing devices and network devices that satisfy the selection conditions of the one or more information processing devices and network devices used for operation verification of the information processing system,
Outputting the acquired third information to the verification device or the own device for performing the operation verification;
A verification support method characterized by that.

Images