JP2017191467A - System management support device, system management support method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for automatically generating a design specification from a construction procedure.SOLUTION: A system management support device includes: input means that inputs a script in which the construction procedure of a system is described; analysis means that extracts predetermined components included in the script as nodes, generates links between the nodes on the basis of the dependence relations between the nodes, and stores information on the nodes and information on the links in a data storage unit; and output means that reads the node information and link information from the data storage unit, creates a directed graph from the node information and link information, and outputs the directed graph.SELECTED DRAWING: Figure 1

Description

  The present invention relates to the technical field of system operation and management.

  Conventionally, various systems have been constructed and operated on a network. In the prior art, when building / operating a system, it is used to create a construction procedure manual for system construction and before construction, to create a construction procedure manual. It is indispensable to create a “design document” to be used.

  The above “design document” is used by an operator who maintains the system during system operation. For example, a monitoring system that monitors a system failure notifies a “server name” in which an alert has occurred and the alert content (log keyword, TCP / IP port address down, process down, etc.). The operator matches this alert with the design document, grasps what has happened, and takes action according to the response procedure manual or the like.

  For the “construction procedure manual” and “design document”, there are tools that support creation. As for the construction procedure manual, for example, there are automated tools disclosed in Non-Patent Documents 1 to 3. As for the design document, for example, there is a design document automatic creation assist tool disclosed in Non-Patent Documents 5 and 6.

https://www.ansible.com/, search April 6, 2016 https://www.chef.io/chef/, retrieved on April 6, 2016 https://puppetlabs.com/, April 6, 2016 search http://www.itsmf-japan.org/, retrieved on April 6, 2016 https://www.microsoft.com/en-us/dev/default.aspx, April 6, 2016 search http://www.sint.co.jp/products/obdz/product/product.html, April 6, 2016 search http://h50146.www5.hp.com/info/newsroom/pr/fy2003/fy03-047.html, April 6, 2016 search http://www.zabbix.com/jp/, April 6, 2016 search http://www-06.ibm.com/systems/jp/software/director/, April 6, 2016 search

  Since the construction procedure manual and the design document describe “how to make” and “results made” for the same system, the parameters are the same. However, these had to be created twice and were in operation. In addition, when modifying or changing the system during operation, it was necessary to create a new “change procedure manual” and recreate and modify the “design document” in accordance with the change. Although the support tools described above reduce the operation of creating procedure manuals and design documents, there is no change in the necessity to create two fundamentally.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a technique capable of automatically creating a design document from a construction procedure document.

According to the embodiment of the present invention, an input means for inputting a script describing a system construction procedure;
Analyzing means for extracting a predetermined component included in the script as a node, creating a link between nodes based on a dependency relationship between nodes, and storing node information and link information in a data storage unit;
Provided with a system management support device comprising: output means for reading node information and link information from the data storage unit, creating a directed graph from the node information and link information, and outputting the directed graph Is done.

  According to the embodiment of the present invention, a design document can be automatically created from a construction procedure document.

It is a block diagram of the system management assistance apparatus 100 in embodiment of this invention. It is a figure which shows the example of an automatic construction script. It is a figure which shows the example of the construction procedure manual which performs an automatic construction script. It is a figure for demonstrating creation of the directed graph data showing a dependence relationship. It is a figure for demonstrating the display of data. It is a figure for demonstrating the example of a search of a relationship, and a display. It is a figure for demonstrating the example of a search of a relationship, and a display. It is a figure which shows the example 1 of a display. It is a figure which shows the example 2 of a display. It is a figure which shows the example 3 of a display. It is a figure which shows the example 4 of a display. It is a figure which shows the example 5 of a display. It is a figure which shows the example 6 of a display. It is a figure which shows the example 7 of a display regarding the influence grasp of a change. It is a figure which shows the example 8 of a display regarding the influence grasp of a change. It is a figure which shows the example 9 of a display regarding the influence grasp of a change. It is a figure for demonstrating the setting and cause identification of a failure location. It is a figure for demonstrating the example regarding cause identification. It is a figure for demonstrating the example regarding cause identification. It is a figure for demonstrating the example regarding cause identification. It is a figure for demonstrating the outline | summary of construction procedure automatic creation. It is a figure for demonstrating the example of construction procedure automatic creation. It is a figure for demonstrating the operation example of construction procedure automatic creation. It is a figure for demonstrating the operation example of construction procedure automatic creation. It is a figure for demonstrating the operation example of construction procedure automatic creation.

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

(Outline of this embodiment)
In this embodiment, the “construction procedure manual” and “design document” created by the system developer in the past are only created as “construction procedure manual”. In the present embodiment, as the “construction procedure manual”, for example, an automatic construction script used in a construction automation tool disclosed in Non-Patent Document 1 is used.

  Then, the system management support apparatus 100 described later analyzes the automatic construction script and creates a design document. This design document is created as a directed graph, and it is possible to display the dependency relationship in the system in an easy-to-understand manner based on the effective graph.

  For the purpose of grasping the dependency relationship, for example, a parameter indicating the dependency relationship described in the automatic construction script, the execution order of the automatic construction script, the same parameter, the parameter inclusion relationship, the parameter naming rule, and the like are used.

  In addition, when analyzing the automatic construction script, not only the information for each server that constitutes the system but also the dependency relationship between the servers that constitute the system is analyzed to obtain information on the entire system. It is possible to display.

  Hereinafter, the configuration and operation of the system management support apparatus 100 in the present embodiment will be described in detail. In the display example described below, a link indicating dependency relation, a line indicating relevance, or the like may be given a color for easily indicating the dependency relation or relevance.

(Device configuration)
FIG. 1 shows a configuration example of a system management support apparatus 100 in the present embodiment. As shown in FIG. 1, the system management support apparatus 100 includes an analysis unit 101, a data storage unit 102, a conversion unit 103, an operation screen creation unit 104, a related information search unit 105, a failure location setting unit 106, a cause search unit 107, A change procedure creation unit 108 is included. The outline of the operation of each part is as follows.

  The analysis unit 101 creates node information and link information corresponding to the directed graph from the input automatic construction script, and stores the created node information and link information (collectively referred to as directed graph data) in the data storage unit 102. . The analysis unit 101 also extracts related information such as the relationship between parameters from the automatic construction script and stores the extracted information in the data storage unit 102. The data storage unit 102 stores directed graph data, related information, and the like.

  The conversion unit 103 converts the data stored in the data storage unit 102, the data created by the operation screen creation unit 104, and the like into data for display (eg, HTML, PDF, PostScript) and outputs the data. The operation screen creation unit 104 creates data (e.g., data on an interface screen for inputting change information) for a user to perform an operation on the screen.

  The related information search unit 105 searches for information related to certain information based on the directed graph data, the related information, and the like. The failure location setting unit 106 sets a node that becomes a failure location in the directed graph. The cause search unit 107 searches and identifies a node that is presumed to be the cause of the failure based on the failure location or the like. The change procedure creating unit 108 creates a construction procedure for making a change in the system (eg, changing a set address).

  The system management support apparatus 100 according to the present embodiment can be realized, for example, by causing a computer to execute a program describing the processing contents described in the present embodiment. That is, the function of the system management support apparatus 100 is to execute a program corresponding to the processing executed by the system management support apparatus 100 using hardware resources such as a CPU, memory, and hard disk built in the computer. Can be realized. 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.

  Hereinafter, processing contents of each functional unit in the system management support apparatus 100 will be described in detail.

(Directed graph data creation process)
First, directed graph data creation processing executed by the analysis unit 101 will be described. As described above, the analysis unit 101 creates directed graph data from the automatic construction script.

  FIG. 2 shows an example of an automatic construction script that becomes an input to the analysis unit 101. As shown in FIG. 2, the automatic construction script used in this 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 software for building an AP (application) server (for example, a Web server), the automatic construction script normally installs software “install_ [identification name]”, the installed software There are three blocks: “setting_ [identification name]” for setting and “start_ [identification name]” for starting the set software. FIG. 2 shows that the software has an identifier = AAAA and has the three blocks. In the example of FIG. 2, each block is called a role.

  Also, in general, a “switchback procedure” is created for construction, but the switchback procedure is the reverse of the construction procedure, “start” is “stop”, “setting” is “reset”, and “install” is “uninstall” Are made into a block by associating them. Since this corresponding block is used for automatic generation of a construction procedure to be described later, it is stored in advance in the data storage unit 102 as input data.

  Note that FIG. 2 shows an example in which all three of install / setting / start (uninstall / reset / stop as the switch-back procedure) are available, but setting / start (reset Some have only (/ stop), others have only setting (reset), such as OS user settings.

  FIG. 3 is a diagram showing an image when a Web server is constructed by installing and setting software AAAA by applying the block shown in FIG. As shown in FIG. 3, a construction procedure manual (which is also included in the automatic construction script input to the analysis unit 101) describing the block execution procedure is prepared, and each block is loaded according to the construction procedure manual. Is executed (install / setting / start). In the construction procedure manual, the target server ("Web" in the example of FIG. 3) and blocks to be executed on the server are described in the order of execution. As will be described later, the dependency relationship between blocks and servers can be grasped in this order. Further, the dependency relationship can be grasped by the dependency relationship described in each block, the parameter, or the like. Note that blocks that are not described in the construction procedure manual may be executed according to the dependency relationship between the blocks. The block of the automatic construction script and the construction procedure manual may be collectively referred to as “construction procedure manual”. Hereinafter, “construction procedure manual” refers to a combination of a block of an automatic construction script and a construction procedure manual.

  As shown in FIG. 4, the automatic construction script as described above is input to the analysis unit 101, and the analysis unit 101 creates directed graph data indicating a dependency relationship between blocks or servers.

  Describing the dependency relationship, for example, regarding [install_AAAA] and [setting_AAAA], since software AAAA cannot be set unless it is installed, there is a dependency relationship that [setting_AAAA] depends on [install_AAAA]. In this case, in this embodiment, [install_AAAA] ← [setting_AAAA] 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, it cannot start, so [start_AAAA] depends on [setting_AAAA], that is, [setting_AAAA] ← [start_AAAA] 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_AAAA] ← [setting_AAAA] ← [start_AAAA] is described as an effective graph. The analysis unit 101 creates directed graph data corresponding to such a directed graph.

  Note that the dependency relationship exists not only within a single software module but also between software modules. 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]
<Processing Procedure of Analysis Unit 101>
The analysis unit 101 to which the automatic construction script is input creates directed graph data in the following procedure.

  Step S101) First, the analysis unit 101 acquires server information to which a series of blocks are applied. For example, the analysis unit 101 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.

  (Step S102) Next, the analysis unit 101 divides a plurality of blocks in the automatic construction script into three groups of install / setting / start for each target server to form nodes. As described above, depending on the application target of the script, there may be only install, only setting, and the like.

  In step S102, for example, there are three install / setting / start script blocks related to software A, and if there is setting as a script block related to network settings, the analysis unit 101 sets the install node, setting Create a node, start node, and create a setting node for network settings.

  Step S103) Next, the analysis unit 101 associates variables (parameters) associated with each block by dividing them into groups such as network / filepath / id / device. In other words, file paths, networks, users, logs, 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 102 To do. More specifically, the file path is forward matching, the network is segment management, the user is id, name, $ home, the log is local and remote, the conf is the file storage location and read at startup, the service is automatic startup, the startup order, etc. From the viewpoint, match, mismatch, and relationship are extracted. As an example, if 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.

  Step S <b> 104) The analysis unit 101 creates link information for connecting 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.

  Step S105) The analysis unit 101 stores the node information, link information, parameter related information, and the like obtained by the above processing in the data storage unit 102 in association with server information.

  An image of data stored in the data storage unit 102 is shown on the left side of FIG. The image corresponds to the input information shown on the right side. In the example of FIG. 4, node information of install_AAAA, setting_AAAA, and start_AAAA, and link information indicating that there is a dependency represented by “install_AAAA ← setting_AAAA ← start_AAAA” between them are stored in the data storage unit 102. Further, as shown in the figure, a parameter is associated with each node.

(Conversion and display operations)
The conversion unit 103 converts the directed graph data created as described above, and outputs the converted data in a format suitable for visualization. For example, when displaying as a Web screen on a user terminal via a network, the conversion unit 103 converts the directed graph data into html data and outputs it. The conversion unit 103 can also convert the directed graph data into print data or data that can be used in mathematical expressions and output the data. Further, the conversion unit 103 may be a functional unit including a display, and a directed graph may be displayed on the display.

  FIG. 5 shows an example in which a directed graph relating to the construction of the AP server is output as a Web page from the Web server to the user terminal. In the example described below, this mode is assumed.

  The conversion unit 103 creates display data from the directed graph data stored in the data storage unit 102 and outputs the display data in the following procedure. Hereinafter, as an example, a case where a directed graph for “AP server” is displayed will be described.

  Step S201) The conversion unit 103 acquires all the node information related to the AP server from the data storage unit 102.

  (Step S202) Next, the conversion unit 103 acquires link information including the acquired node (that is, using the node as an end point).

  Step S203) Then, the conversion unit 103 creates a directed graph from the node information and the link information. The directed graph created here is, for example, an image of a directed graph.

  Step S204) The conversion unit 103 converts the created directed graph into data to be displayed (eg, PDF / HTML / PS) and outputs the data.

  In the above example, a directed graph related to one server, which is an AP server, is displayed. However, the directed graph can also be displayed by connecting directed graphs of a plurality of servers.

  For example, in the directed graph data (shown in the display image for convenience) stored in the data storage unit 102 shown in FIG. 6A, there is a dependency between the AP server and the LB (load balancing) server. In some cases, as shown in FIG. 6B, a display in which the directed graphs of the servers are connected can be performed. FIG. 6 shows an example in which software AAAA is installed on the AP server and software lb is installed on the LB server. The same applies to FIG. 7 described below.

(Relevance search and display)
In the present embodiment, the related information search unit 105 can search for related data having no dependency, and the conversion unit 103 can display the related data.

  For example, as shown in FIG. 7A, it is assumed that the directed graph data has no dependency between the AP server and the LB server, but the same IP address is set. In this case, for example, as shown on the upper side of FIG. 7B, an operation button indicating that the search is performed is displayed together with the directed graph for the AP server. The screen data related to the operation of the operation buttons and the like is created by the operation screen creation unit 104 and displayed via the conversion unit 103.

  When the user operates the operation button, the related information search unit 105 searches for information related to the directed graph of the AP server in the data storage unit 102. Here, the related information search unit 105 detects that the same IP address as the IP address associated with the setting node of the AP server is present in the directed graph data of the LB server, as shown in the lower part of FIG. 7B. The directed graph of the AP server and the directed graph of the LB server are displayed together with the IP address. As a result, it can be seen at a glance that the same IP address is set.

  The processing of the related information search unit 105 is executed by the following procedure, for example.

  Step S251) The related information search unit 105 searches the information specified by the user from the operation screen.

  Step S252) Then, the related information search unit 105 searches for information related to the specified information. As an example, if the specified information is a specific IP address of a certain node, a node having segment information including the IP address is searched. If the specified information is a specific file path of a certain node, a node having information that matches the file path up to a predetermined number of characters is searched.

  Step S253) The related information search unit 105 displays information including the related nodes searched as described above.

(Specific example of display)
Hereinafter, specific display examples displayed by the functions described so far in the system management support apparatus 100 according to the present embodiment will be described.

  Here, the input information to the analysis unit 101 includes AP (application) server construction information and LB (load balancing) server construction information. The AP server construction information includes BBBB (software that runs on the interpreter CCCC) that performs daemonization, CCCC scripts that BBBB targets to be daemonized, user setting information for CCCC scripts, and CCCC that is CCCC script interpreters , Including DDDD, which is the database software used by the CCCC script, and a block of the automatic construction script corresponding to each of the network setting information. In addition, the LB server construction information includes a block of an automatic construction script corresponding to each of EEEE, which is Web server software, and network setting information.

  FIG. 8 shows Display Example 1. Since both the BBBB and CCCC scripts operate on the CCCC, the CCCC is designated as a dependency as shown by the arrows with the arrows (1) and (2) in FIG. Similarly, the dependency of install / setting / start in software called EEEE is displayed for the LB server.

  FIG. 9 shows a display example 2. In each block in the automatic construction script used in this embodiment, parameters are used for installation and setting. As described above, this can be grasped by each block, and the dependency relationship across the servers can be displayed with the associated contents. Relevance can be displayed in consideration of not only parameter matching but also partial matching of file paths, network segment inclusion relationships, and the like. Thereby, the relevance and the influence range can be grasped. Such relevance detection is executed by the related information search unit 105 of the system management support apparatus 100.

  In the example shown in FIG. 9, the IP address (10.0.0.1) used in the AP server setting_BBBB (more specifically, BBBB.conf) is specified as the parameter used in the LB server block setting_EEEE. And it is shown by the dotted line that these two are related.

  In addition, since the address used in the network_setting of the LB server is included in the segment described in BBBB.conf, this is also displayed as related.

  FIG. 10 shows a display example 3. In the display example 3, the dependency relationship between servers is displayed. For example, as shown in FIG. 10B, the analysis unit 101 grasps the dependency relationship between servers based on the “execution order” of server construction described in the construction procedure manual, and determines the dependency relationship between servers. You can set a link to show. In the example of FIG. 10B, since the LB server is constructed first with the AP server first, the dependency relationship “AP server ← LB server” is established, and the display as shown in FIG. 10A is performed. Can do. In addition to grasping the dependency relationship in the execution order of the construction procedure manual, it is also possible to grasp the dependency relationship based on the meaning of the parameters inside the script.

  FIG. 11A shows a display example 4. Depending on the system, there may be a dependency relationship in which a module inside the server also relates, such as “module 1 of server A depends on server B, and server B depends on module 2 of server A”. Display example 4 is a display example in such a case. As in the case of the display example 3, the analysis unit 101 can grasp such dependency relationships based on the construction procedure manual.

  As shown in FIG. 11B, in this example, the execution procedure in the construction procedure manual is in the order of (1) CCCC of the AP server, (2) LB server, and (3) BBBB of the AP server. . Therefore, as shown in FIG. 11A, the dependency relationship “CCCC of AP server ← LB server ← BBBB of AP server” is displayed. The CCCC in FIG. 11A corresponds to the module 2, the LB server in FIG. 11A corresponds to the server B, and the BBBB in FIG. 11A corresponds to the module 1.

  FIG. 12 shows a display example 5. This is an example in which the analysis unit 101 grasps the inter-server dependency using parameters. In the display example 5, the parameters of the automatic construction script are named according to a certain rule, so that the analysis unit 101 grasps the dependency relationship between the servers based on the parameter naming rule, and understands the dependency relationship Directed graph data based on.

  Specifically, the following variable names are used as IP address variable names for round robin destinations and standby addresses.

net_ip_listen = 10.0.0.1
net_ip_target = 10.0.0.1
Based on the naming rule and the IP address value, the analysis unit 101 can grasp the dependency relationship between the servers, RoundRobin source → RoundRobin destination, and can display the display example 5 as a result. In addition, by using a different naming convention, it is possible to grasp the dependency relationship between client and server. For example, since the operation of the client stops when the server has fallen first, the user can recognize that “the server is dropped after the client is dropped” by displaying such a dependency.

  In addition to the above example, for example, the IP address of the other server set in the DB server ⇒ ACL (ACcess List, access list), the IP address of the other server set in the Web server ⇒ Forward destination As described above, it is possible to grasp and display the dependency relationship according to the characteristics of the server.

  FIG. 13 shows a display example 6. In display example 6, the network address assigned to the device name eth0 in the AP server (10.0.0.1/24, the address of the local server) is used by the web server EEEE. It is estimated to be the forward destination and displayed. That is, the dependency relationship is LB server → AP server.

<Display example for grasping the impact of changes>
The related information search unit 105 of the system management support apparatus 100 can search for and grasp the influence location associated with the change of the system based on the relevance information stored in the data storage unit 102, and can display it. It is.

  Examples of system changes include changing the IP address by releasing the network, and upgrading the software version by dealing with the vulnerability.

  FIG. 14 shows a display example 7 related to grasping the influence of the change. In the display example 7, it is displayed that the setting of the BBBB is affected as a result of the related information search unit 105 searching for the related part by changing the IP address of the LB server. In other words, it is indicated that the IP address after the change of the LB server is out of (not included in) the BBBB ACL segment.

  FIG. 15 shows a display example 8. The display example 8 is an example in which the affected part of the change when the CCCC vulnerability countermeasure (software version upgrade) is performed is displayed. Specifically, in the BBBB using CCCC, it is displayed that the path for specifying CCCC is different from the path where CCCC is installed.

  FIG. 16 shows a display example 9. Display example 9 is an example in which the effect of the change to add the NIC (eh1) to the AP server is displayed. This example shows that the IP address of eh1 and the IP address of eth0 of the LB server are the same segment.

(About fault location setting and cause specific processing)
Next, processing executed by the failure location setting unit 106 and the cause searching unit 107 of the system management support apparatus 100 will be described. FIG. 17 is a diagram for explaining the outline of the processing. In the example of FIG. 17, the same data as the directed graph data shown in FIG. It is assumed that a screen (FIG. 6B) showing the dependency relationship is displayed. The processing procedure when a failure occurs is performed as follows. In this procedure, the example of FIG. 17 is used as appropriate.

  Step S301) When information indicating a failure location is input from the monitoring system or manually to the system management support apparatus 100, the operation screen creation unit 104 displays the failure location so as to stand out. In the example of FIG. 17, the start block of the LB server is displayed prominently. Further, the failure location setting unit 106 stores information on the failure location in the data storage unit 102.

  Step S302) Next, the cause search unit 107 searches for a link having the failure point node as an end point, and displays the start point node prominently as an influence point. In the example of FIG. 17, start_AAAA is displayed prominently as the node at the start point of the link whose end point is the node at the failure location (LB server start).

  Step S303) Further, the cause search unit 107 searches for a link starting from the node at the failure location, and displays the node at the end point prominently as the cause (suspected location). In the example of FIG. 17, the setting of the LB server is displayed conspicuously as the node at the end point of the link starting from the node at the fault location (start of the LB server). The suspected part is checked against the actual system.

  Step S304) When a plurality of suspected places are displayed, the place where the doubt is clear clears the display as the suspected place.

  Step S305) The cause search unit 107 searches for a link having the suspected place as the starting point, transitions the end point node as a further suspected place, and returns to step S303. In step S303, the suspected location is regarded as a failure location and processing is performed.

(Display example of fault location setting and cause specific processing)
18 to 20 show specific display examples 1 to 3 regarding the setting of the fault location and the specific processing of the cause.

  FIG. 18 shows that an error has occurred in BBBB (start_BBBB). And according to said step S303, setting_BBBB and start_DDDD (whether DDDD has started) which are the 1st dependence destinations are displayed as a suspected place. The user who sees this display confirms it.

  Here, if there is no change in the setting_BBBB setting (not the cause of failure) and it is found that start_DDDD is the cause (DDDD has not started), start_DDDD remains as a suspected location, as shown in FIG. . By following the dependency destination, setting_network (network setting) and setting_DDDD become suspect locations.

  As a result of investigating these, as shown in FIG. 20, it was finally found that the trouble was caused by the DDDD setting change. In this case, it can be logically understood that the DDDD setting affects the operation of the BBBB in the shortest distance.

  As described above, when a location where a failure has occurred is selected by the system management support apparatus 100 according to the present embodiment, possible locations can be displayed. Even if it is difficult to grasp the relationship on the design document, the dependency relationship can be confirmed with the directed graph, so that the dependency destination can be displayed in an easy-to-understand manner.

(About change procedure automatic creation processing)
Next, processing executed by the change procedure creation unit 108 of the system management support apparatus 100 will be described. FIG. 21 is a diagram for explaining the outline of the processing. The example of FIG. 21 illustrates a case where, for example, the IP address in setting is changed in the directed graph displayed on the left screen. In this case, the operation screen creation unit 104 displays a screen for inputting an address change. When a change operation is performed by the user, the change procedure creation unit 108 creates and outputs a change procedure based on the change content and the directed graph data stored in the data storage unit 102. In the example of FIG. 21, it is shown that a procedure has been created in which AAAA is stopped, address change is set, and AAAA is restarted.

<Specific example of automatic creation of change procedure>
Hereinafter, the change procedure creating process executed by the change procedure creating unit 108 will be described more specifically.

  FIG. 22 shows a directed graph assumed in this example. This example corresponds to the configuration on the AP server side in the specific display example already described. In this example, a procedure creation process when the ACL address in BBBB is changed from 172.16.0.0/28 to 172.16.0.0/24 will be described.

  23 to 25 are flowcharts of processing executed by the change procedure creation unit 108. In order to explain the processing in an easy-to-understand manner, FIGS. 23 to 25 show the progress of procedure creation corresponding to the specific example shown in FIG. Hereinafter, the change procedure creation process will be described with reference to FIGS. 23 and 24 are the same as the flowchart. The procedure is divided into two in order to explain using specific examples.

  As shown in FIG. 23, the change procedure creation unit 108 first selects a construction target node. In a specific example, setting_BBBB is selected in step S1. Next, it is determined whether there is a link having the current target node as an end point. In the specific example, as shown in step S2, since there is the link, the determination is Yes, and the information is recorded in the data storage unit 102 with the start point of the link as the target node and the end point as the parent node. In the specific example, as shown in step S3, the information is recorded in the data storage unit 102 with the start_BBBB that is the link start point as the target node and the setting_BBBB that is the end point as the parent node.

  Next, when it is determined whether or not there is a link having the current target node as an end point, as shown in step S4, since there is no such link, the determination is No, and then a construction that is symmetrical with the target node. Select a procedure node. It is assumed that symmetrical node information is stored in the data storage unit 102 in advance. In the specific example, as shown in step S5, stop_BBBB that is a symmetric node of start_BBBB is selected.

  Next, it is determined whether or not there is even one node in the construction procedure tree. In the specific example, since there is no node as shown in step S6, the determination is No. Next, as shown in step S7, the construction procedure node (stop_BBBB in the concrete example) is designated at the top of the construction procedure tree. .

  Next, it is determined whether or not the current target node matches the selected node. In the specific example, as shown in step S8, since the target node (start_BBBB) does not match the selected node (setting_BBBB), the determination is no, and then the node that called the target node is set as the target node. In the specific example, as shown in step S9 (and S2), setting_BBBB, which is a node that called the target node (start_BBBB), is set as the target node.

  Next, proceeding to FIG. 24, as shown in step S10 in the specific example, a construction procedure node that is symmetrical to the target node is selected. In a specific example, re_setting_BBBB is selected.

  Next, it is determined whether or not there is even one node in the construction procedure tree. In the specific example, as shown in step S11, since there is a node (stop_BBBB), the determination is Yes, and then the construction procedure node is set as the end node of the construction procedure tree. In a specific example, as shown in step S12, re_setting_BBBB is set as a terminal node.

  Next, it is determined whether the target node matches the selected node. In the specific example, as shown in step S13, since they match, the determination is yes, the first half process is terminated, and the process proceeds to the construction procedure output process shown in FIG. At this point, the construction procedure tree of the specific example is as shown in step S14 in FIG.

  In FIG. 25, first, the end of the generated construction procedure tree is selected. In the specific example, as shown in step S15, re_setting_BBBB which is a terminal node is selected. This selected node becomes the current target node.

  Next, it is determined whether there is a link having the current target node as an end point. In the specific example, as shown in step S16, since there is a link whose end point is re_setting_BBBB, the determination is Yes, and then the link start point node is selected as the target node. In a specific example, stop_BBBB is selected as shown in step S17.

  Next, a construction procedure that is symmetrical to the target node is selected, and this is set at the end of the construction procedure tree. In the specific example, as shown in step S18, start_BBBB, which is a symmetrical node of stop_BBBB, is added to the end.

  Next, it is determined again whether there is a link having the current target node as an end point. In the specific example, as shown in step S19, since there is no link having the current target node as the end point, the determination is no, and the entire construction procedure tree is output as shown in step S20.

  In addition, said example is an example in the case of changing the parameter of one node. When changing the parameters of a plurality of nodes, for example, the above procedure may be applied to each node to be changed.

(Effect of embodiment)
As described above, the present embodiment has the following effects. Hereinafter, it will be described that a problem that is expected to occur due to the conventional technique and that the problem is solved by the technique according to the present embodiment.

1) Improving the accuracy of the design document In the conventional technology, efforts have been made to reduce both the operation of creating the design document and the operation of the construction procedure document. However, it was necessary to confirm whether the information described in the design document was set in the system that was actually constructed. Data extraction from already created deliverables was also limited in displaying module relevance from development code.

  After the system is built, a parameter “intent to use” and a list of application modules “to be installed” are described, so errors are likely to occur.

  On the other hand, according to the technology according to the present embodiment, a design document (directed graph) is automatically generated from an automatic construction script, so a highly accurate design document can be obtained.

2) Ease of understanding the scope of influence and dependencies within a single server In the conventional technology, in order to confirm the system configuration, the dependency between modules, and the location where changes are made, understand the design document itself, The system must be assumed from the design document. Design documents are often created with emphasis on listability, and even if applications and IP addresses installed in a single server are listed, in order to infer their dependencies and affected points Some knowledge was necessary. If there is a lack of knowledge and experience to understand and grasp the entire design document, it is impossible to grasp the configuration of a large system or a system using advanced technology, and overlook the related system and parameters. End up.

  For example, even if you can understand the IP address parameter of the NW device, but you don't know the netmask, you can't understand the relationship between 192.168.0.1 and 192.168.0.0/24 or 192.168.0.129 and 192.168.0.128/25. Similarly, you can understand the mount point and device name of a disk mounted with Linux (registered trademark), but in the case of iSCSI storage, you cannot understand the influence of the initiator name in iSCSI, the VENDOR name in multipath, and the PRODUCT name. Also, a unique ID called uuid is generated by IP address or MAC address, but if this generation is not grasped, the relevance may be overlooked.

  On the other hand, according to the technology according to the present embodiment, the information indicating the valid graph and the relevance is automatically generated from the automatic construction script, so that the relevance of the relevance as described above can be eliminated.

3) Easier understanding of the impact range and dependency of the entire system In the conventional technology, in order to understand the impact of the entire system where the servers depend on each other in complex ways, not only the design document for one server, It was necessary to read all the design documents that seem to be related. This is a difficult task for those with low skills. Design documents are often created with a focus on listability for a single server, and it is difficult to describe all relevance to other servers. In particular, if the parameters of the other server are set for the parameter of the own server, and the influence when the setting is deviated, the listability will be lost and cannot be marked.

  For example, load balancing by the load balancer depends on the DMZ address of the Web server under the load balancer. This is described as “Used by load balancer” as the IP address information of the Web server, and the relationship must be clearly stated on the load balancer side as “Set the IP address of the Web server”. This is an example where it is easy to specify relationships, but it is difficult to specify all relationships. For example, when the access control to a certain server is “10.0.0.0/24”, the server “10.0.0.129/28” is accessible. However, whether this ACL access control can be changed to 10.0.0.0/25 is difficult unless the knowledge of the NW and the relationship between the systems are correctly grasped.

  On the other hand, according to the technology according to the present embodiment, information indicating the valid graph and the relevance is automatically generated from the automatic construction script, so the relevance as described above can be easily grasped.

4) Ease of maintaining consistency between the design document and the actual environment in continued development The parameters and configuration of the system change due to subsequent specification changes, additional development, and workarounds for troubles. The design document must be modified to follow this change each time. This takes a lot of work.

  On the other hand, according to the technique according to the present embodiment, since the information (design document) indicating the valid graph and the relevance is automatically generated from the automatic construction script, the consistency between the design document and the actual environment can be easily maintained.

5) Cost reduction In order to correctly grasp and operate the system, it is necessary for the technical skill person who is at the same level as the architect and developer to fully understand the design document. It is assumed that operations will be performed. However, this leads to an increase in operating costs.

  On the other hand, according to the technology according to the present embodiment, since a valid graph and information (design document) indicating relevance are automatically generated from an automatic construction script, a technical skill person at the same level as a builder and a developer. Even without it, you can easily grasp the system and reduce costs.

(Summary of embodiment)
In this embodiment, input means for inputting a script describing a system construction procedure, and predetermined constituent elements included in the script are extracted as nodes, and links between nodes are created based on the dependency relationship between the nodes. And analyzing means for storing node information and link information in a data storage unit, reading node information and link information from the data storage unit, creating a directed graph from the node information and link information, There is provided a system management support apparatus comprising output means for outputting the directed graph.

  The analysis unit 101 described in the embodiment is an example of the input unit and the analysis unit. The conversion unit 103 is an example of an output unit. With the above configuration, a directed graph corresponding to the design document can be automatically created from the script corresponding to the construction procedure document.

  The predetermined component is, for example, a block obtained by grouping system construction processing according to the type of construction processing in the script. The analysis unit may determine the dependency relationship based on information described in the block, and the analysis unit determines the dependency relationship based on procedure information included in the script. It is good as well.

  The analysis unit may extract parameters used in the nodes, create relevance information indicating the relevance of the parameters between the nodes, and store the relevance information in the data storage unit.

  Based on the relevance information, it may further comprise relevance detection means for detecting relevance between nodes or relevance between servers including nodes, in which case the output means may include the relevance. It is good also as outputting the directed graph which added the information to show.

  When a certain node in the directed graph is a failure location, the system further comprises cause search means for extracting from the data storage unit a node at a link end point starting from the node at the failure location as a suspected location of the failure cause It is good.

  When receiving an instruction to change a parameter of one or more nodes in the directed graph, a construction procedure for changing the parameter is created based on a dependency relationship between the one or more nodes and another node. It is good also as providing a change procedure preparation means.

  Although the present embodiment has been described in detail 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 100 System management support apparatus 101 Analysis part 102 Data storage part 103 Conversion part 104 Operation screen creation part 105 Related information search part 106 Fault location setting part 107 Cause search part 108 Change procedure creation part

Claims (10)

An input means for inputting a script describing a system construction procedure;
Analyzing means for extracting a predetermined component included in the script as a node, creating a link between nodes based on a dependency relationship between nodes, and storing node information and link information in a data storage unit;
The system management support apparatus comprising: output means for reading node information and link information from the data storage unit, creating a directed graph from the node information and link information, and outputting the directed graph. The system management support apparatus according to claim 1, wherein the predetermined component is a block obtained by grouping system construction processes according to types of construction processes in the script. The system management support apparatus according to claim 2, wherein the analysis unit determines the dependency relationship based on information described in the block. 4. The system management support apparatus according to claim 1, wherein the analysis unit determines the dependency relationship based on procedure information included in the script. 5. The analysis unit extracts parameters used in nodes, creates relevance information indicating relevance of parameters between nodes, and stores the relevance information in the data storage unit. Item 5. The system management support apparatus according to any one of Items 1 to 4. Relevance detecting means for detecting relevance between nodes or relevance between servers including nodes based on the relevance information;
The system management support apparatus according to claim 5, wherein the output unit outputs a directed graph to which information indicating the relevance is added. When a certain node in the directed graph is a failure location, the system further comprises cause search means for extracting from the data storage unit a node at the end point of the link starting from the node at the failure location as the suspected location of the failure cause The system management support apparatus according to claim 1, wherein: When receiving an instruction to change a parameter of one or more nodes in the directed graph, a construction procedure for changing the parameter is created based on a dependency relationship between the one or more nodes and another node. The system management support apparatus according to claim 1, further comprising a change procedure creation unit. A system management support method executed by a system management support device,
An input step for entering a script describing the system construction procedure;
An analysis step of extracting a predetermined component included in the script as a node, creating a link between nodes based on a dependency relationship between the nodes, and storing node information and link information in a data storage unit;
A system management support method comprising: an output step of reading node information and link information from the data storage unit, creating a directed graph from the node information and link information, and outputting the directed graph.   The program for functioning a computer as each means in the system management assistance apparatus of any one of Claims 1 thru | or 8.

Images