JP2019036252A - Test automation device, test method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To comprehensively identify a failure test site and easily grasp the influence of a failure test when conducting a failure test on a system composed of a plurality of virtual servers and a virtual network. SOLUTION: In a test automation device, a set of components of the system is extracted from an automatic construction script used for constructing the system, and predetermined components are extracted as nodes based on the dependency relationship between the nodes. Then, based on the configuration management information acquisition means that creates a link between the nodes and creates a directed graph, and the dependency relationship between the predetermined components shown by the directed graph, the connection relationship between the components is selected from the set of the components. It is provided with an inter-element connection information creating means for creating inter-element connection information indicating the above, and a test execution means for identifying a failure test site based on the inter-element connection information and executing a failure test for the failure test site. [Selection diagram] Fig. 3

Description

  The present invention relates to a technique for performing a failure test on a system including a plurality of virtual servers and a virtual network.

  Systems that provide cloud services and application services are built with fault tolerance. Conventionally, failure durability has been confirmed by passing a test by manually generating a failure manually and confirming that the system operates normally.

  In confirming failure durability, failure points that cause failures have been intentionally extracted by engineers from past experience, and comprehensiveness has been confirmed through reviews and the like.

  As a conventional technique, failure test automation has been realized by a tool that automatically generates a load, a limited application service switching test tool, and the like. Although a failure point and an expected result are prepared for a specific application, it is not versatile and is applied only to the specific application.

  Also, in recent years, a method has been used such as taking down a randomly configured server and confirming that the service can still be provided, but this means that the system can operate even if it is wrong rather than finding an error. This is the last method to confirm, and when an error is found, the design must be performed again.

  In recent years, a method called “Lineage Drive Fault Injection” may be used to inadvertently insert erroneous settings into the system and check the operation of the system. However, completeness and expected results are not available. First, an engineer configures where to put an incorrect setting and the behavior at that time.

Implementation and evaluation of failure cause automatic identification / recovery function by CMDB using automatic construction script, Yusaku Numata, Masamasa Kamiya, Shoji Hashimoto, Daigo, January 19, 2017, IEICE Tech.

  In the prior art, it is difficult to determine the effect of the failure test, so it is difficult to determine whether the result of the failure test is an expected result. Further, in the prior art, the failure test location is something that an engineer must manually consider, so it is difficult to comprehensively identify the failure test location.

  In particular, in a virtual environment composed of virtual servers, virtual networks, and the like that have become widespread in recent years, the number of failure points has increased compared to a conventional bare metal environment, and therefore a solution to the above point is required.

  The present invention has been made in view of the above points, and when performing a failure test on a system configured with a plurality of virtual servers and virtual networks, the failure test location can be comprehensively identified, The purpose is to provide a technology that makes it possible to easily grasp the effects of failure tests.

According to the disclosed technology, a test automation device that identifies a failure test location of a system configured with a plurality of virtual servers and virtual networks,
A set of system components is extracted from the automatic configuration script used to construct the system, a predetermined component is extracted as a node, and a link between nodes is created based on the dependency between the nodes. Configuration management information acquisition means for creating a directed graph
Inter-element connection information creating means for creating inter-element connection information indicating a connection relation between the constituent elements from the set of constituent elements based on the dependency relation between the predetermined constituent elements indicated by the directed graph;
There is provided a test automation device comprising: test execution means for identifying a failure test location based on the inter-element connection information and executing a failure test for the failure test location.

  According to the disclosed technology, it is possible to comprehensively identify fault test locations when performing fault tests on a system consisting of multiple virtual servers and virtual networks, and easily grasp the effects of fault tests. Techniques are provided that enable this to be done.

1 is an overall configuration diagram of a system in an embodiment of the present invention. It is a figure for demonstrating an automatic construction script and configuration management information. 2 is a functional configuration diagram of the test automation apparatus 100. FIG. 2 is a hardware configuration diagram of the test automation apparatus 100. FIG. It is a flowchart which shows the flow of a process. It is a figure which shows the example of an object system. It is a figure which shows the example of the connection information between elements. It is a figure which shows the example of a failure test point. It is a figure which shows the example of a failure test point. It is a figure for demonstrating a configuration management information acquisition process. It is a figure which shows the example of structure management information. It is a figure which shows the example of the automatic construction script regarding an application. It is a figure which shows the example of the construction procedure manual which performs an automatic construction script. It is a figure which shows creation of the directed graph data which shows a dependence relationship. It is a flowchart which shows the preparation procedure of directed graph data. It is a figure which shows the other example of the directed graph data which shows dependence. It is a figure for demonstrating the production method of the connection information between elements. It is a figure for demonstrating the example of a test method.

  Hereinafter, an embodiment (this embodiment) of the present invention will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

  This embodiment is premised on a virtual / real machine mixed environment including a plurality of virtual servers, one or a plurality of virtual networks, real machines of networks and information systems, physical networks, and the like. The “virtual environment” in this specification includes not only a virtual environment that does not include a real machine but also a virtual / real machine mixed environment.

(Overall system configuration)
FIG. 1 shows the overall configuration of the system in the present embodiment. As shown in FIG. 1, the system in the present embodiment includes a plurality of servers 10 and a test automation device 100. The plurality of servers 10 constitutes a service system that provides various network services to users. Each of the servers 10 is a virtual server (also referred to as a virtual machine) on which one or a plurality of applications operate. Each of the servers 10 may be constructed on one physical machine (computer), or a plurality of servers 10 may be constructed on one physical machine. The servers 10 are connected to the network. The network is one or more virtual networks constructed by virtual machines on one or more physical machines (computers).

  Each server 10 can be various AP (application) servers (Web, DB, LB (load balance), etc.), routers, switches, etc., depending on the application (software) to be operated there.

  When the server 10 connects to the network, an IP address, a NIC (Network Interface Card), or the like is used. The IP address and NIC may also be virtually allocated in the virtual environment.

  The test automation apparatus 100 is an apparatus that automates a failure test in a service system. As will be described later, the test automation apparatus 100 creates inter-element connection information from configuration management information, exhaustively extracts fault test locations, and executes fault tests on fault test locations using a predetermined method. Can do.

(Overview of configuration management information)
Here, an outline of the configuration management information that is the base of the inter-element connection information in the present embodiment will be described.

  In this embodiment, installation / setting / startup of an application on each server is performed using an automatic construction script. Furthermore, in the present embodiment, setting (construction) of a virtual machine (hereinafter referred to as VM) and OS installation / setting are also performed using an automatic construction script. The OS installation / setting includes network settings.

  The “VM setting”, “OS installation / setting”, and “AP installation / setting” using the automatic construction script may be executed by the test automation apparatus 100, or a device other than the test automation apparatus 100 may be used. The test automation apparatus 100 may store an automatic construction script used for “VM setting”, “OS installation / setting”, and “AP installation / setting” for each server, It can be acquired from a server or the like.

  The test automation apparatus 100 acquires configuration management information (a set of component elements) of hardware (hereinafter referred to as HW), OS, and AP from the automatic construction script used for each setting described above for each server. Holds management information. Here, the HW is an HW emulated on the virtual machine, and the configuration management information of the HW includes, for example, a disk size, a memory size, a CPU count, a NIC count, and the like. The OS configuration management information includes, for example, partition information, host name, OS name, OS version, IP address assigned to NIC, and the like.

  The automatic construction script is basically a list of “command: parameter”, and the test automation apparatus 100 can acquire the configuration management information by extracting the parameter from the automatic construction script.

  As for the AP configuration management information, the system construction device 100 can acquire the configuration management information as information of a directed graph composed of nodes and links indicating the AP dependency as described in Non-Patent Document 1, for example. .

  FIG. 2 is a diagram for explaining the automatic construction script and the configuration management information. In FIG. 2, reference numeral 14 denotes an HW automatic construction script, 15 denotes an OS automatic construction script, and 16 denotes an AP automatic construction script. However, in FIG. 2, not the automatic construction script itself but information included in the automatic construction script is shown. The conversion logic 17 and the configuration management information DB 18 are functions that exist in the test automation apparatus 100. Specifically, the conversion logic 17 is a function in the configuration management information acquisition unit 110 described later, and the configuration management information DB 18 is a part of the data storage unit 140.

  As shown in FIG. 2, a VM HW is constructed by the HW automatic construction script 14, an OS is constructed by the OS automatic construction script 15, and an AP or the like executed on the OS is constructed by the AP automatic construction script 16. Is done. The conversion logic 17 creates configuration management information from each automatic construction script and stores it in the configuration management information DB 18.

  Also, the conversion logic 17 uses the configuration management information stored in the configuration management information DB 18 to create an automatic construction script corresponding to the automatic construction script from which the configuration management information is extracted. It is also possible to set the AP or the like. This can be used, for example, to recover a configuration dropped by a failure test.

(Configuration example of test automation apparatus 100)
FIG. 3 is a diagram illustrating an example of a functional configuration of the test automation apparatus 100. As shown in FIG. 3, the test automation apparatus 100 includes a configuration management information acquisition unit 110, an inter-element connection information creation unit 120, a test execution unit 130, and a data storage unit 140.

  The configuration management information acquisition unit 110 acquires configuration management information from the automatic construction script. The inter-element connection information creation unit 120 creates inter-element connection information based on the configuration management information. The test execution unit 130 identifies (extracts) a failure test location based on the inter-element connection information, and performs a failure test on the identified failure test location using a predetermined method. The data storage unit 150 stores various data including an automatic construction script, configuration management information, inter-element connection information, a failure test method, and the like.

  The test automation apparatus 100 can be realized, for example, by causing a computer to execute a program describing the processing contents described in the present embodiment. In other words, the function of the test automation apparatus 100 is executed by executing a program corresponding to the process executed by the test automation apparatus 100 using hardware resources such as a CPU, memory, and hard disk built in the computer. It is possible to realize. The above-mentioned program can be recorded on a computer-readable recording medium (portable memory or the like), stored, or distributed. It is also possible to provide the program through a network such as the Internet or electronic mail.

  FIG. 4 is a diagram illustrating a hardware configuration example when the test automation apparatus 100 is realized by a computer. The test automation apparatus 100 illustrated in FIG. 4 includes a drive device 200, an auxiliary storage device 202, a memory device 203, a CPU 204, an interface device 205, a display device 206, an input device 207, and the like that are connected to each other via a bus B. .

  A program that realizes processing in the test automation apparatus 100 is provided by a recording medium 201 such as a CD-ROM or a memory card. When the recording medium 201 storing the program is set in the drive device 200, the program is installed from the recording medium 201 to the auxiliary storage device 202 via the drive device 200. However, it is not always necessary to install the program from the recording medium 201, and the program may be downloaded from another computer via a network. The auxiliary storage device 202 stores the installed program and stores necessary files and data.

  The memory device 203 reads the program from the auxiliary storage device 202 and stores it when there is an instruction to start the program. The CPU 204 (processor) implements functions related to the test automation apparatus 100 in accordance with a program stored in the memory device 203. The interface device 205 is used as an interface for connecting to a network. The display device 206 displays a GUI (Graphical User Interface) or the like by a program. The input device 207 includes a keyboard and mouse, buttons, a touch panel, and the like, and is used to input various operation instructions.

(Overall process flow)
FIG. 5 is a flowchart showing an overall flow of processing executed by the test automation apparatus 100. First, the configuration management information acquisition unit 110 in the test automation apparatus 100 acquires configuration management information from the automatic construction script (S101).

  Next, the inter-element connection information creation unit 120 creates inter-element connection information from the configuration management information (S102). Subsequently, the test execution unit 130 identifies a failure test location from the inter-element connection information, and executes a failure test on the identified failure test location according to a predetermined procedure (S103).

  Details of the processing of each step of S101 to S103 will be described later.

(About inter-element connection information)
Here, the outline of the inter-element connection information used for identifying the failure test location and grasping the influence of the failure in the present embodiment will be described.

  A system having the configuration shown in FIG. 6 is assumed as the target system. As shown in FIG. 6, the system has a configuration in which LB servers, AP servers 1 to 3, a router, and DB servers 1 and 2 are connected as illustrated. An application indicated by AAAA operates on the LB server, an application indicated by CCCC operates on the DB servers 1 and 2, and an application indicated by BBBB operates on the AP servers 1 to 3. The system configuration shown here is grasped by, for example, a system design document.

  FIG. 7 shows an example in which inter-element connection information corresponding to the system of FIG. 6 is graphically displayed. The inter-element connection information is created from configuration management information obtained from the automatic construction script used for constructing the system shown in FIG. For example, the components corresponding to the LB server in the figure are AP (start_AAA), IP address (10.3.130.21), NIC (eth0), and NETWORK (DMZ). The same applies to other servers.

  Information such as AP (start_AAA), IP address (10.3.130.21), and NIC (eth0) is included in configuration management information that is a set of components. Specifically, for a certain server, the AP, IP, NIC, and network name (for example, DMZ) are included in the configuration management information as linked information. As shown in FIG. , AP, IP, NIC, NETWORK connected information can be created.

  In addition, for APs, a dependency relationship is described in the configuration management information. This dependency relationship is indicated by a thick line in FIG. In the example of FIG. 7, the BBBBs of the AP servers 1 to 3 must be activated for the CCCC of the LB server to be activated, and the BBBBs of the AP servers 1 to 3 are activated for the DB servers 1 and 2 to activate. It is shown as a dependency that the CCCC must be activated. Note that the inside of a cluster (such as ap_cluster) has no dependency and is in a parallel relationship.

  And the inter-element connection information shown in FIG. 7 can be obtained by using the method described later based on the dependency relationship and the components in each server.

  By using this inter-element connection information, it is possible to comprehensively identify the location where the failure test should be performed, and to determine what is affected (or where is not affected) when a failure is caused at that location. It can be easily grasped.

  For example, as shown in FIG. 8, it is assumed that a failure occurs in the NIC on the side connected to the NETWORK (DMZ) in the router. Note that causing the failure means, for example, deleting the NIC. In this case, it can be seen that the BBBBs of the AP servers 1 to 3 and the AAA of the LB server that are dependent on the CCCCs of the DB servers 1 and 2 are affected. For example, if a test that causes a failure of the NIC in the actual system does not result in the above prediction, for example, the system may be constructed incorrectly, and countermeasures can be taken .

  It can also be predicted that the NIC (eth0) of the router will not match the configuration management information, and that no other configuration management information will be affected.

  Regarding the identification of fault test locations, for example, the test execution unit 130 can perform exhaustive identification by extracting all the constituent elements constituting the inter-element connection information shown in FIG. 7 as fault test locations. The impact on each failure test location can be easily grasped.

  By performing such identification, nodes (routers, hosts, etc.) alone, failure test locations between nodes, and comprehensive failure test locations across multiple layers (L3 or higher without NIC, cable, link, link down) All fault test points such as path faults) can be extracted.

  FIG. 9 shows another example of inter-element connection information. FIG. 9 shows an example in which AP1 depends on AP2 and AP2 depends on AP3 and 4. AP3 and 4 are in a parallel relationship. In this case, even if a failure occurs at the point indicated by x in FIG. 9, it is AP4 that is affected by the failure of x, and AP3 that is in parallel with AP4 is not affected. Therefore, since the dependency relationship of AP1-> AP2-> AP3 is not broken, it can be predicted that the service is continued.

  Note that the inter-element connection information illustrated in FIG. 7 and the like is merely an example. Any component can be included in the inter-element connection information as long as it is information obtained from the automatic construction script. For example, in FIG. 7, only the start_identification name is shown as the component of the application, but install_identification name and setting_identification name may be included as the component. In addition, an OS, middleware, and the like may be included as components.

  Hereinafter, the processing content by each function part of the test automation apparatus 100 will be described more specifically.

(Configuration management information acquisition processing by the configuration management information acquisition unit 110)
First, an example of configuration management information acquisition processing by the configuration management information acquisition unit 110 will be described with reference to FIGS.

  As illustrated in FIG. 10, the configuration management information acquisition unit 110 acquires the configuration management information indicated by 24 from the HW automatic configuration script 21 and the OS automatic configuration script 22 and stores the configuration management information in the data storage unit 140. As an example, the configuration management information acquisition unit 110 extracts parameters indicated by underlining in the HW / OS automatic construction scripts 21 and 22 as configuration management information 24. The acquired HW / OS configuration management information can also be displayed as shown in FIG. 11, for example. In the example shown in FIG. 11, it is indicated that the server 1 and the server 2 belong to the same network, and the server 3 and the server 4 belong to the same network.

  Further, as shown in FIG. 10, the configuration management information acquisition unit 110 acquires the configuration management information 25 from the AP automatic construction script 23 and stores it in the data storage unit 140. In the present embodiment, the configuration management information 25 acquired from the AP automatic construction script 23 is generated as information of a directed graph indicating the dependency relationship of the AP. Based on this dependency and information on the components of each server, the inter-element connection information creating unit 110 of the test automation apparatus 100 creates inter-element connection information.

  FIG. 12 shows an example of an AP automatic construction script that is input to the configuration management information acquisition unit 110. As shown in FIG. 12, the automatic construction script used in the present embodiment is divided into a plurality of blocks in consideration of reuse. Further, values (parameters) used in the block are converted into variables, and the values of the variables are collectively described outside the block. In addition, each block can have a dependency relationship with other blocks.

  More specifically, for example, for an application (software) for constructing an AP server (eg, a Web server), an automatic construction script usually includes “install_ [identification name]” for installing the software, There are three blocks: “setting_ [identification name]” for setting and “start_ [identification name]” for starting the set software. FIG. 12 shows that the software has an identification name = AAAA and has the three blocks. In the example of FIG. 12, each block is called a role.

  Note that FIG. 12 shows an example in which all three of install / setting / start are provided, but there is only setting / start (reset / stop) like the OS network setting, and the OS user setting Some have only setting (reset).

  FIG. 13 is a diagram showing an image in the case of constructing a Web server by applying the block shown in FIG. 12 and performing installation and setting of software AAAA. As shown in FIG. 13, a construction procedure manual (which is also included in the automatic construction script input to the configuration management information acquisition unit 110) describing the execution procedure of the block is prepared, and each block is prepared according to the construction procedure manual. Are loaded and executed (install / setting / start). In the construction procedure manual, the target server (“Web” in the example of FIG. 13) and blocks to be executed on the server are described in the order of execution. In this order, the dependency relationship between blocks and servers can be grasped. Further, the dependency relationship can be grasped by the dependency relationship described in each block, the parameter, or the like.

  As illustrated in FIG. 14, the automatic construction script as described above is input to the configuration management information acquisition unit 110, and the configuration management information acquisition unit 110 creates directed graph data indicating a dependency relationship between blocks or APs.

  Describing the dependency relationship, for example, with respect to [install_AAAAA] and [setting_AAAAA], since software AAAA cannot be set unless it is installed, there is a dependency relationship that [setting_AAAAA] depends on [install_AAAAA]. In this case, in this embodiment, [install_AAAAA] ← [setting_AAAAA] is described as a directed graph so that the arrow is directed toward the dependency. Similarly, since software AAAA does not operate normally unless it is set, [start_AAAAA] depends on [setting_AAAAA], that is, [setting_AAAAA] ← [start_AAAAA] is described.

  That is, it is assumed that there is a “dependency relationship” between two blocks of “a block to be executed in advance for execution of a certain block”. In the example of the above three blocks, [install_AAAAA] ← [setting_AAAAA] ← [start_AAAAA] is described as a directed graph. The configuration management information acquisition unit 110 creates directed graph data corresponding to such a directed graph.

  Dependencies exist not only within a single software module (which may be referred to as an application), but also between software modules as described above. For example, assume that a Web server software module uses a DB server software module, and the Web server software module cannot provide a service unless the DB server software module is started. In this case, the dependency shown by the following directed graph exists.

[Install_database] ← [setting_database] ← [start_database]
↑
[Install_webserver] <-[setting_webserver] <-[start_webserver]
The configuration management information acquisition unit 110 to which the automatic construction script has been input creates directed graph data according to the procedure of the flowchart of FIG.

  S201) First, the configuration management information acquisition unit 110 acquires server information to which a series of blocks are applied. For example, the configuration management information acquisition unit 110 can acquire, as the server information, information on a host that is a target of application of a series of blocks described in a construction procedure manual.

  S202) Next, the configuration management information acquisition unit 110 divides a plurality of blocks in the automatic construction script into three groups of install / setting / start for each target server, and forms nodes. Note that, as described above, depending on the application target of the script, there are cases where only install, only setting, or the like.

  In S202, for example, there are three install / setting / start script blocks related to software A, and when there is setting as a script block related to network settings, the configuration management information acquisition unit 110 includes an install node for software A, A setting node and a start node are created, and a setting node for network setting is created.

  S203) Next, the configuration management information acquisition unit 110 associates the variables (parameters) associated with each block by dividing them into groups such as network / filepath / id / device. In other words, file paths, networks, users, log, conf, services, etc. are grouped according to the contents of the system, and matches, mismatches, relationships (eg, inclusion relationships) are extracted, and the information is stored in the data storage unit 140. To do. As an example, when the setting address in the setting of software A is address 1 and the setting address in the setting of software B is address 1, information indicating that the two have a matching relationship is stored.

  S204) The configuration management information acquisition unit 110 creates link information that links nodes between nodes having a dependency relationship. The dependency relationship can be determined from, for example, a block execution procedure in the construction procedure manual. Further, when there is a description of the dependency relationship in the block, it can be determined from the description.

  S205) The configuration management information acquisition unit 110 stores the node information, link information, parameter related information, and the like obtained by the above processing in the data storage unit 140 in association with server information.

  On the left side of FIG. 14, an image of data stored in the data storage unit 140 is shown. The image corresponds to the input information shown on the right side. In the example of FIG. 14, node information of install_AAAAA, setting_AAAAA, and start_AAAAA, and link information indicating that there is a dependency represented by “install_AAAAA ← setting_AAA ← start_AAAAA” is stored in the data storage unit 140. That is, a directed graph indicating the dependency relationship is stored. Further, as shown in the figure, a parameter is associated with each node.

  In the above example, a directed graph relating to one AP is shown. As another example, FIG. 16 shows an example in which a dependency relationship is represented by connecting directed graphs of a plurality of APs (applications). FIG. 16 illustrates an example in which there is a dependency between AP1 (example: Web) and AP2 (example: LB (load balancing)).

  When the configuration management information acquisition unit 110 performs the construction for server recovery based on the configuration management information, the configuration management information acquisition unit 110 installs a specific AP for the purpose based on the dependency relationship between the APs. , The AP on which the specific AP depends and the AP on which the specific AP depends can be installed together, and the specific AP can be operated correctly.

(Inter-element connection information creation processing by inter-element connection information creation unit 120)
Next, the element connection information creation processing by the element connection information creation unit 120 will be described. The information used for creating the inter-element connection information is the configuration management information acquired by the configuration management information acquisition unit 110. The configuration management information includes directed graph information indicating the dependency relationship between APs described above and a set of component elements in each server. Any information can be acquired as a set of components in each server as long as the information is included in the automatic construction script. For example, the following information is acquired. The following shows a case where there are a server 1 and a server 2 as an example.

(1) Components of Server 1 NIC {NIC name: eth0, IP address: 10.160.128.104/26, network name: MZ}
AP {start_AAAA}
NIC {NIC name: eth1, IP address: 10.160.128.105/26, network name: MZ}
・ AP {start_BBBB}
(2) Components of Server 2 NIC {NIC name: eth0, IP address: 10.166.128.199/26, network name: DMZ}
AP {start_CCCC}
In the above example, for example, with respect to the server 1, the server 1 has eth0 as a NIC linked to AAAA, its IP address is 10.160.128.104/26, and the network to be connected is MZ. It is shown that there is eth1 as the NIC linked to BBBB, its IP address is 10.160.128.105/26, and the connected network is MZ. .

  In addition, the server 2 has eth0 as the NIC linked to the CCCC, the IP address is 10.160.128.199/26, and the connected network is DMZ.

  The above is an excerpt from the component information actually acquired. In practice, however, the information is obtained in the form of a json file, for example. In addition, component information can be obtained for all servers constructed by the automatic construction script.

  The inter-element connection information creation unit 120 creates inter-element connection information as illustrated in FIG. 7 from the above-described dependency relationship information between APs and information on the components of each server. Note that the inter-element connection information creating unit 120 may graphically display the created inter-element connection information as shown in FIG. 7, or may hold it as data without displaying it.

  An example of a method for creating inter-element connection information will be described with reference to FIG. Here, it is assumed that AP1 depends on AP2 and AP3 as a dependency. In FIG. 17, the relationship is indicated by a dotted line.

  Initially, the inter-element connection information creation unit 120 knows only the dependency relationship (dotted line relationship) shown in FIG. Here, it is assumed that processing is executed in the order of AP2 and AP3 starting from AP1.

  First, the inter-element connection information creation unit 120 determines whether or not the AP 2 on which the AP 1 depends is in the same server 1 as the AP 1 by searching the component element information. Here, there is no AP 2 in the server 1. Next, the inter-element connection information creation unit 120 searches each server connected to the same network as the network to which the server 1 in which AP1 exists is connected, and determines whether AP2 exists in the server. Judgment is made by searching. Whether two servers belong to the same network can be determined by the name of the network to which the NIC is connected, or can be determined by the network part of the IP address of the NIC.

  Here, the inter-element connection information creation unit 120 detects AP2 in the server 2 connected to the NETWORK1 to which the server 1 is connected. Thereby, the inter-element connection information creating unit 120 creates inter-element connection information of “AP1-IP1-NIC1-NETWORK1-NIC2-IP2-AP2” based on the constituent element information.

  The inter-element connection information creation unit 120 extracts the elements in the component element information as “AP1-IP1-NIC1-NETWORK1-NIC2-IP2-AP2” as inter-element connection information, and connects them. The information may be created, information in which pointers to elements in the component element information are connected may be created, or information in another format may be created.

  Next, the inter-element connection information creation unit 120 determines whether or not the AP 3 on which the AP 1 depends is in the same server 1 as the AP 1 by searching the constituent element information. Here, there is no AP 3 in the server 1. Next, the inter-element connection information creation unit 120 determines whether or not the AP 3 exists in each server connected to the same network as the network to which the server 1 in which the AP 1 exists is connected, by searching the constituent element information. To do. Here, only the server 2 exists as a server connected to the same network as the network to which the server 1 is connected, but there is no AP 3 there.

  Next, the inter-element connection information creating unit 120 has AP3 connected to a server on a network connected to a router connected to NETWORK1, which is a default gateway in the network (NETWORK1) to which server 1 is connected. It is determined by searching the component information whether or not there is. This operation is similar to that of network routing that forwards packets to the default route. The router component information is included in the configuration management information as component information, similar to the server information.

  Here, the inter-element connection information creation unit 120 detects that the AP 3 exists in the server 3. Thereby, the inter-element connection information creation unit 120, based on the component element information, inter-element connection information of “AP1-IP1-NIC1-NETWORK1-NIC4-IP4-router-IP5-NIC5-NETWORK2-NIC3-IP3-AP3”. Create

  Display information shown in FIG. 17 is obtained by graphically displaying the inter-element connection information created by the above processing. In addition, the thick line shown in FIG. 17 shows the connection between elements based on a dependence relationship. By displaying this thick line, it is possible to clearly grasp the dependency relationship between APs, and to easily grasp the influence in the failure test visually.

  The inter-element connection information created by the inter-element connection information creation unit 120 is stored in the data storage unit 140.

(Test execution processing by the test execution unit 130)
Next, test execution processing by the test execution unit 130 will be described. In the present embodiment, a failure occurrence procedure (failure occurrence method) corresponding to a component that can be a failure test location of a failure test is determined in advance, and information on the determined failure occurrence procedure is stored in the data storage unit 140. . There are a plurality of types of procedures for generating a failure for a certain failure test location. However, if the procedure for generating a failure is not determined for the failure test location (when it is left to the engineer's judgment), the procedure at the failure occurrence location in the past test cannot be determined when the actual failure occurs, and the test result May not be very helpful. Therefore, in the present embodiment, a failure occurrence procedure corresponding to components that can be failure test locations is determined in advance.

  FIG. 18 shows an example of a failure occurrence procedure for each component. As shown in FIG. 18, for the component start_ [name], the AP identified by name is stopped. For the component install_ [name], the AP identified by name is uninstalled. For the component setting_ [name], the setting for the AP identified by the name is initialized. These three procedures can be generated automatically (automatically).

  With regard to node (server, switch, etc.), net_dev_self (NIC), and net_ip_self (IP address), all cause a failure with a command corresponding to the corresponding virtual environment. In addition, for name_network (network), filtering (communication interruption) is generated in a switch on the network. These three procedures can be generated from a template.

  As an example, when the inter-element connection information creation unit 120 obtains the inter-element connection information shown in FIG. 17, the test execution unit 130 displays all the elements shown in FIG. 17 (AP1, IP1, NIC1, NETWORK1, NIC2, (IP2, AP2, NIC4, IP4, router, IP5, NIC5, NETWORK2, NIC3, IP3, AP3) are extracted (washed out). Then, a failure test for the target system is performed for each element according to the procedure of FIG.

  In order to perform a failure test, for example, the server may be dropped, but in that case, it is necessary to return to the original state. In such a case, the configuration can be easily executed in the present embodiment that holds the configuration management information. This construction process may be executed by the test automation apparatus 100 or may be executed by another apparatus that has acquired the configuration management information from the test automation apparatus 100.

(Effects of the embodiment)
With the technology according to the present embodiment, it is possible to comprehensively identify the failure test location and easily influence the failure test when performing a failure test on a system composed of a plurality of virtual servers and virtual networks. It becomes possible to grasp. More specifically, for example, the following effects can be obtained.

(1) The effect of a failure can be automatically confirmed in advance. By using configuration management information that includes dependencies, the effect of a failure can be confirmed as a system. That is, it can be confirmed how the state of each configuration management information of the system changes depending on the point where the failure occurs. As a result, it is possible to preliminarily identify changes in the expected state when a failure occurs in the actual system. By comparing this expected result with the actual failure test result, It is possible to check whether the actual system has the fault tolerance and whether the behavior is not expected. Therefore, it is possible to avoid a situation such as causing service interruption due to unexpected behavior in an actual system.

(2) Comprehensiveness of failure test locations can be ensured Configuration management information covers HW / NW / OS / AP information, and it is possible to ensure completeness by specifying all of them as failure test locations. .

(3) A method for generating a fault can be defined. Conventionally, only an outline of a fault such as a “network fault” can be described, and a fault test location based on the description is ambiguous. On the other hand, according to the technique of the present embodiment, for example, a fault test location can be clearly specified like NIC (eth0) in a router as shown in FIG. Then, by defining a failure occurrence command according to the type of component, the failure occurrence method can be clearly defined.

(4) The scope of influence is fixed, and the test is automatically executed and automatically restored. Conventionally, a method of taking a snapshot of the virtual environment as a whole and restoring it every time a test is taken. However, in the first place, since the influence range by the failure test is not correctly grasped, in order to return all environments correctly, it is necessary to take a snapshot of all servers. On the other hand, the technology according to the present embodiment has a clear influence range and can restore the system by using the dependency relationship, so that the time can be shortened.

(5) The merits of the virtual environment can be utilized to the maximum. In this embodiment, configuration management information using a script for fully automatically constructing a system on the virtual environment is used. For this reason, not only the failure test locations but also the procedures and results can be created automatically and comprehensively from the system construction script built on this virtual environment.

  That is, with the technique according to the present embodiment, a fault test that has been performed in an ambiguous manner can be executed with a clear “expected test result”, and test operation can be reduced. In addition, when an actual failure occurs, the location of the new failure ticket generated in the past and the failure occurrence procedure at that time can be confirmed with high reproducibility in a short time.

(Summary of embodiment)
As described above, according to the present embodiment, a test automation device for identifying a failure test location of a system configured by a plurality of virtual servers and virtual networks, which is based on an automatic construction script used for constructing the system And a configuration management information acquisition means for extracting a set of component elements of the system, extracting a predetermined component element as a node, and creating a directed graph by creating a link between nodes based on a dependency relationship between the nodes; Inter-element connection information creating means for creating inter-element connection information indicating a connection relation between the constituent elements from the set of constituent elements based on the dependency relation between the predetermined constituent elements indicated by the directed graph, and the inter-element connection It is provided with a test execution means for identifying a failure test location based on the information and executing a failure test for the failure test location. Test automation and wherein is provided.

  The test execution unit executes the failure test by a method predetermined for each component corresponding to the failure test location, for example.

  The inter-element connection information creating means is configured to add another predetermined component dependent on a predetermined component existing in a certain server in the same server, the same network, or another network in the set of the component elements. The inter-element connection information may be created by searching in order.

  The inter-element connection information may include an application as the predetermined component, a network interface related to the application, an IP address, and a network.

  Although the present embodiment has been described above, the present invention is not limited to the specific embodiment, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. Is possible.

DESCRIPTION OF SYMBOLS 10 Server 100 Test automation apparatus 110 Configuration management information acquisition part 120 Inter-element connection information creation part 130 Test execution part 140 Data storage part 200 Drive apparatus 201 Recording medium 202 Auxiliary storage apparatus 203 Memory apparatus 204 CPU
205 Interface device 206 Display device 207 Input device

Claims (6)

A test automation device for identifying failure test points of a system composed of a plurality of virtual servers and virtual networks,
A set of system components is extracted from the automatic configuration script used to construct the system, a predetermined component is extracted as a node, and a link between nodes is created based on the dependency between the nodes. Configuration management information acquisition means for creating a directed graph
Inter-element connection information creating means for creating inter-element connection information indicating a connection relation between the constituent elements from the set of constituent elements based on the dependency relation between the predetermined constituent elements indicated by the directed graph;
A test automation apparatus comprising: test execution means for identifying a failure test location based on the inter-element connection information and executing a failure test on the failure test location. The test automation apparatus according to claim 1, wherein the test execution unit executes the failure test by a method predetermined for each component corresponding to a failure test location. The inter-element connection information creating means is configured to add another predetermined component dependent on a predetermined component existing in a certain server in the same server, the same network, or another network in the set of the component elements. The test automation apparatus according to claim 1 or 2, wherein the inter-element connection information is created by searching in order. The test according to any one of claims 1 to 3, wherein the inter-element connection information includes an application as the predetermined component, a network interface related to the application, an IP address, and a network. Automation device. A test method executed by a test automation device that identifies a failure test location of a system composed of a plurality of virtual servers and a virtual network,
A set of system components is extracted from the automatic configuration script used to construct the system, a predetermined component is extracted as a node, and a link between nodes is created based on the dependency between the nodes. Configuration management information acquisition step for creating a directed graph
An inter-element connection information creating step for creating inter-element connection information indicating a connection relation between constituent elements from the set of constituent elements based on a dependency relation between predetermined constituent elements indicated by the directed graph;
A test execution step of identifying a failure test location based on the inter-element connection information and executing a failure test on the failure test location.   The program for functioning a computer as each means in the test automation apparatus of any one of Claims 1 thru | or 4.

Images