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

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 constructing/operating a system, it is used to create a "construction procedure manual" for constructing the system, and before construction, it is used to create a construction procedure manual, and after construction, the system is comprehensively checked during operation. It is essential to create a "design document" that will be used for this purpose.

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

There are tools that support the creation of "construction procedures" and "design documents". As for the construction procedure manual, for example, there are automated tools disclosed in Non-Patent Documents 1 to 3. Regarding design documents, for example, there are design document automatic creation assisting tools disclosed in Non-Patent Documents 5 and 6.

Search https://www.ansible.com/, April 6, 2016 Search https://www.chef.io/chef/, April 6, 2016 Search on https://puppetlabs.com/, April 6, 2016 Search http://www.itsmf-japan.org/, April 6, 2016 Search on https://www.microsoft.com/ja-jp/dev/default.aspx, April 6, 2016 http://www.sint.co.jp/products/obdz/product/product.html, search on April 6, 2016 http://h50146.www5.hp.com/info/newsroom/pr/fy2003/fy03-047.html, searched 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

Since the construction procedure manual and the design document describe "how to make" and "result of making" for the same system, the parameters are common. However, these had to be created in duplicate and were in operation. Further, when the system is modified or changed during operation, it is necessary to newly create a "change procedure document" and recreate and modify the "design document" in accordance with the change. Although the support tools described above reduce the work required to create procedure manuals and design documents, there is no change in the fact that two basic tools must be created.

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

According to the embodiment of the present invention, input means for inputting a script describing a system construction procedure,
A plurality of predetermined components included in the script are extracted as a plurality of nodes, a link between the nodes is created based on the dependency between the nodes, and the node information and the link information are stored in the data storage unit. Analytical means,
An output unit that reads out 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.
When a certain node in the directed graph is a failure point, as a suspected point of the cause of the failure, a cause search unit for extracting the node of the end point of the link starting from the node of the failure point from the data storage unit ,
Each of the plurality of predetermined components is a block in which the description of the system construction process is divided into blocks in the script, and the construction process includes installation of software, setting of installed software, and start of the set software. There is provided a system management support device characterized by being any one of a plurality of construction processes including a.

According to the embodiment of the present invention, it becomes possible to automatically create a design document from a construction procedure document.

It is a block diagram of the system management support 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 executes an automatic construction script. It is a figure for explaining creation of directed graph data showing dependence. It is a figure for demonstrating the display of data. It is a figure for demonstrating the example of a search of relatedness, and a display. It is a figure for demonstrating the example of a search of relatedness, 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 grasping the influence of a change. It is a figure which shows the example 8 of a display regarding grasping the influence of a change. It is a figure which shows the example 9 of a display regarding grasping the influence of a change. FIG. 6 is a diagram for explaining setting of a failure location and specification of a cause. It is a figure for explaining an example about cause specification. It is a figure for explaining an example about cause specification. It is a figure for explaining an example about cause specification. It is a figure for explaining the outline of construction procedure automatic creation. It is a figure for explaining a target example of construction procedure automatic creation. It is a figure for explaining an operation example of construction procedure automatic creation. It is a figure for explaining an operation example of construction procedure automatic creation. It is a figure for explaining an operation example of construction procedure automatic creation.

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

(Outline of the present embodiment)
In the present embodiment, the creation of the "construction procedure manual" and the "design document" that the system developer has conventionally performed is limited to the creation of the "construction procedure manual". Further, in the present embodiment, for example, an automatic construction script used in the construction automation tool disclosed in Non-Patent Document 1 is used as the “construction procedure manual”.

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 easily display the dependency relationship in the system based on the effective graph.

For 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 inclusion relation of the parameters, 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 configures the system is analyzed, but also the dependency relationships among the servers that configure the system are analyzed to obtain information about the entire system. It is possible to display.

Hereinafter, the configuration and operation of the system management support apparatus 100 according to the present embodiment will be described in detail. In the example of the display described below, the link indicating the dependency relationship, the line indicating the relationship, and the like may be colored for easy understanding of the dependency relationship and the relationship.

(Device configuration)
FIG. 1 shows a configuration example of the system management support apparatus 100 according to 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, It has a change procedure creation unit 108. The outline of the operation of each part is as follows.

The analysis unit 101 creates node information and link information corresponding to a 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 it 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 for the user to perform an operation on the screen (for example, interface screen data for inputting change information).

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 point setting unit 106 sets a node that becomes a failure point 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 creation 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 content 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 by using the hardware resources such as the CPU, the memory, and the hard disk built in the computer. Can be realized by. The above program can be recorded in a computer-readable recording medium (portable memory or the like), and can be stored or distributed. It is also possible to provide the above program through a network such as the Internet or electronic mail.

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

(Process of creating directed graph data)
First, the process of creating directed graph data 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 is input to the analysis unit 101. The automatic construction script used in the present embodiment is divided into a plurality of blocks in consideration of reuse, as shown in FIG. Further, the values (parameters) used in the block are made into variables, and the values of the variables are collectively described outside the block. Further, it is possible to set a dependency relationship with other blocks in each block.

More specifically, for software for building an AP (application) server (eg: Web server), an automatic build script usually uses "install_[identification name]" to install software, It has three blocks, "setting_[identification name]" for setting and "start_[identification name]" for starting the set software. FIG. 2 shows that the example of the software with the identifier=AAAA has the three blocks. Further, in the example of FIG. 2, each block is called a role.

In addition, a "revertive procedure" is usually created during construction, but the revertive procedure is the reverse direction of the construction procedure: "start" is "stop", "setting" is "reset", and "install" is "uninstall". Are associated with each other to form a block. Since this corresponding block is used for automatic generation of the construction procedure described later, it is stored in the data storage unit 102 in advance as input data.

In addition, FIG. 2 shows an example in which all three of install/setting/start (uninstall/reset/stop as a switchback procedure) are prepared, but setting/start(reset Some have only /stop), some have only setting(reset), such as OS user settings.

FIG. 3 is a diagram showing an image when a Web server is constructed by applying the blocks shown in FIG. 2 and installing and setting software AAAA. As shown in FIG. 3, a construction procedure manual (also included in the automatic construction script input to the analysis unit 101) describing the execution procedure of the block is prepared, and each block is loaded according to the construction procedure manual. , Executed (install/setting/start). In the construction procedure manual, the target server (“Web” in the example of FIG. 3) and blocks to be executed for the server are described in the order of execution. As will be described later, such a sequence makes it possible to grasp the dependency relationship between blocks and between servers. Further, the dependency relation can be grasped also by the dependency relation described in each block, the parameter, or the like. It should be noted that blocks not described in the construction procedure manual may be executed according to the inter-block dependency relationship. Further, the block of the automatic construction script and the construction procedure manual may be collectively referred to as "construction procedure manual". Hereinafter, the "construction procedure manual" refers to the combination of the block of the automatic construction script and the 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 the dependency relationships between blocks and between servers.

Explaining the dependency relationship, for example, regarding [install_AAAA] and [setting_AAAA], since software AAAA cannot be set unless software AAA is installed, there is a dependency relationship that [setting_AAAA] depends on [install_AAAA]. In this case, in the present embodiment, [install_AAA]←[setting_AAA] is described as a directed graph so that the arrow points toward the dependent direction. Similarly, if software AAAA is not set and does not operate normally, it cannot start. Therefore, [start_ AAAA] depends on [setting_ AAAA], that is, [setting_ AAAA]←[start_ AAAA].

That is, it is assumed that there is a "dependency" between two blocks of "a block that should be executed in advance for execution of a certain block". In the example of the above three blocks, [install_AAA]←[setting_AAA]←[start_AAA] is described as a valid graph. The analysis unit 101 creates directed graph data corresponding to such a directed graph.

Note that the dependency relationships exist not only within a single software module but also between software modules. For example, it is assumed that the Web server software module uses the DB server software module and the Web server software module cannot provide the service unless the DB server software module is started. In this case, there is a dependency shown by the following directed graph.

[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 by the following procedure.

(Step S101) First, the analysis unit 101 acquires server information to which a series of blocks is applied. For example, the analysis unit 101 can acquire, as the server information, information on a host to which a series of blocks is applied, which is described in the 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 and makes them into nodes for each target server. As described above, depending on the application target of the script, there are cases where only install or only setting is performed.

In step S102, for example, when there are three script blocks regarding software A, install/setting/start, and setting as a script block regarding network setting, the analysis unit 101 determines that the install node for software A, setting Create node and start node, and create setting node for network settings.

(Step S103) Next, the analysis unit 101 divides and associates variables (parameters) related to each block into groups such as network/filepath/id/device. That is, grouping is performed according to the contents of the system such as file path, network, user, log, conf, service, etc., and matching, non-matching, and relationship (eg, inclusion relationship) are extracted, and the information is stored in the data storage unit 102. To do. More specifically, file path prefix match, network segment management, user id, name, $home, log local and remote, conf file location and read on boot, service autostart, boot order etc. From the viewpoint, match, mismatch, and relationship are extracted. As an example, when the setting address in the setting of the software A is the address 1 and the setting address in the setting of the software B is the address 1, it is determined that both have a matching relationship, and information indicating that is stored.

(Step S104) The analysis unit 101 creates link information that links nodes that have a dependency relationship. The dependency can be determined, for example, from the execution procedure of the block in the construction procedure manual. Further, if there is a description of the dependency relationship in the block, it can be judged from the description.

(Step S105) The analysis unit 101 stores the node information, the link information, the parameter related information, and the like obtained by the above processing in the data storage unit 102 in association with the 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, the node information of install_AAAA, setting_AAAA, start_AAAA and the link information indicating that there is a dependency indicated 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 operation)
The conversion unit 103 converts the directed graph data created as described above and outputs it as data in a format suitable for visualization. For example, when displaying as a Web screen on the user terminal via the 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 used in a mathematical formula and output the converted data. Further, the conversion unit 103 may be a functional unit including a display, and the directed graph may be displayed on the display.

FIG. 5 shows an example of a case where a directed graph relating to the construction of an AP server is output as a web page from a web server to a user terminal. This form is assumed in the example described below.

The conversion unit 103 creates display data from the directed graph data stored in the data storage unit 102 and outputs the display data according to the following procedure. In the following, as an example, a case of displaying a directed graph for the “AP server” will be described.

(Step S201) The conversion unit 103 acquires all information of nodes 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, with the node as an end point).

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 the directed graph.

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

In the above example, the directed graph for one server called the AP server is displayed, but it is also possible to display the directed graphs of a plurality of servers by connecting them.

For example, in the directed graph data (illustrated in the display image for convenience) stored in the data storage unit 102 shown in FIG. 6A, the dependency relationship between the AP server and the LB (load balancing) server is shown. In some cases, as shown in FIG. 6B, it is possible to perform a display in which directed graphs of the respective servers are linked. Note that FIG. 6 shows an example in which the software AAAA is installed in the AP server and the software lb is installed in 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 that does not have a dependency relationship, and the conversion unit 103 can display the data.

For example, as shown in FIG. 7A, it is assumed that, in the directed graph data, the AP server and the LB server have no dependency, 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 to be 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 creating unit 104 and displayed via the converting unit 103.

When the user operates the operation button, the related information search unit 105 searches the data storage unit 102 for information related to the directed graph of the AP server. 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 exists in the directed graph data of the LB server, and as shown in the lower side of FIG. 7B. In addition, the directed graph of the AP server and the directed graph of the LB server are displayed together with the IP address. With this, it can be seen at a glance that the same IP address is set.

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

(Step S251) The related information retrieval unit 105 retrieves the information itself designated by the user from the operation screen.

Then, the related information search unit 105 searches for information related to the specified information (step S252). As an example, if the designated information is a specific IP address of a node, a node having segment information including the IP address is searched. Further, if the specified information is a specific file path of a node with certain information, a node having information that matches up to a predetermined number of characters in a prefix match with the file path is searched.

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

(Specific example of display)
Hereinafter, in the system management support apparatus 100 according to the present embodiment, specific display examples displayed by the functions described so far 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. Also, the AP server construction information is BBBB (software that runs on the interpreter CCCC) that is a daemon, the CCCC script that BBBB makes a daemon, the user setting information of the CCCC script, and the CCCC that is the CCCC script interpreter. , DDDD which is the database software used by the CCCC script, and the block of the automatic construction script corresponding to each of the network setting information. Further, the LB server construction information includes blocks of an automatic construction script corresponding to each of EEEE which is Web server software and network setting information.

FIG. 8 shows a display example 1. Since both BBBB and CCCC script operate on CCCC, CCCC is instructed as a dependency, as shown by the arrowed lines in (1) and (2) of FIG. Also, the dependency of install/setting/start in the software EEEE is displayed for the LB server.

FIG. 9 shows a display example 2. Each block in the automatic construction script used in this embodiment uses parameters for installation and setting. As described above, this can be grasped in each block, and the dependency relationship across servers can be displayed with the associated content. It is possible to display the relevance in consideration of not only the matching of parameters but also the partial matching of file paths and the inclusion relation of Network segments. As a result, it is possible to grasp the relevance and the influence range. The detection of such a relationship 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 setting_BBBB (more specifically, BBBB.conf) of the AP server is specified in the parameter used in the block setting_EEEE of the LB server. And, it is shown by the dotted line display that these two are related.

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

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

FIG. 11A shows a display example 4. Depending on the system, there may be a dependency relationship in which modules inside the server are also related, 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 also grasp such dependency relationships based on the construction procedure manual.

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

FIG. 12 shows a display example 5. This is an example of the case where the analysis unit 101 grasps the inter-server dependency relationship by the parameter. 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 relation between the servers based on the naming rule of the parameter and the grasped dependency relation. The directed graph data based on is created.

Specifically, the following variable names are used as the variable names of the round-robin destination and the IP address for the standby address.

net_ip_listen=10.0.0.1
net_ip_target=10.0.0.1
Based on this naming rule and the value of the IP address, the analysis unit 101 can grasp the dependency relationship between the servers, that is, RoundRobin source→RoundRobin destination, and as a result, display example 5 can be displayed. Also, by using another naming convention, it is possible to grasp the dependency relationship of client ⇒ server. For example, if the server goes down first, the operation of the client stops. Therefore, by displaying such a dependency relationship, the user can certainly recognize that "the client is dropped and then the server is dropped".

In addition to the above example, for example, the IP address of another server set in the DB server ⇒ ACL (ACcess List, access list), the IP address of another 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 the display example 6, since the web server EEEE uses the network address (10.0.0.1/24, the address of its own server) assigned to the device name eth0 in the AP server, the AP server sends it from the LB server. It is estimated to be the forward destination and is displayed. That is, the dependency is LB server→AP server.

<Display example for understanding the impact of changes>
The related information search unit 105 of the system management support apparatus 100 can search, grasp, and display a location affected by a system change based on the information on the relationship stored in the data storage unit 102. Is.

Examples of system changes include changing the IP address by making the Network public, and upgrading the software version to address vulnerabilities.

FIG. 14 shows a display example 7 regarding the grasp of the influence of the change. In the display example 7, the IP address of the LB server is changed, and as a result of the related information searching unit 105 searching the related portion, it is displayed that the setting of the BBBB is affected. In other words, it is shown that the changed IP address of the LB server is out of the segment of the BBBB ACL (not included).

FIG. 15 shows a display example 8. The display example 8 is an example in which the affected portion of the change when the CCCC vulnerability response (software version upgrade) is performed is displayed. Specifically, it is displayed that in BBBB that uses CCCC, the path that specifies CCCC and the path where CCCC is installed are different.

FIG. 16 shows a display example 9. The display example 9 is an example in which the influence of the change of adding 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 in the same segment.

(Regarding fault location setting and cause identification processing)
Next, the processing executed by the failure point setting unit 106 and the cause search 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. 6A is targeted. Then, it is assumed that the screen showing the dependency relationship (FIG. 6B) 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 point is input to the system management support apparatus 100 from the monitoring system or manually, the operation screen creating unit 104 displays the failure point in a conspicuous manner. In the example of FIG. 17, the start block of the LB server is displayed conspicuously. Further, the fault location setting unit 106 stores information on the fault location in the data storage unit 102.

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

(Step S303) Further, the cause search unit 107 searches for a link having the node at the failure point as a starting point and conspicuously displays the node at the end point as the cause (suspected point). In the example of FIG. 17, the setting of the LB server is conspicuously displayed as the node of the end point of the link starting from the node at the failure point (start of the LB server). Regarding the suspected part, confirmation is performed with respect to the actual system.

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

(Step S305) The cause search unit 107 searches for a link starting from the suspected point, transitions to the node at the end point as a further suspected point, and returns to step S303. In step S303, the suspected portion is regarded as a faulty portion and processed.

(Display example of processing for specifying the location of failure and specifying the cause)
18 to 20 show specific display examples 1 to 3 regarding the setting of the failure point and the process of specifying the cause.

FIG. 18 shows that an error has occurred in BBBB (start_BBBB). Then, according to the above step S303, setting_BBBB and start_DDDD (whether or not DDDD is started), which is the first dependence destination, are displayed as suspicious points. The user who sees this display confirms it.

Here, if it is found that there is no change in the setting of setting_BBBB (not the cause of failure) and the cause is start_DDDD (DDDD has not started), start_DDDD remains as the suspected place, as shown in FIG. .. Then, by tracing the dependence destination, setting_network (setting of network) and setting_DDDD become suspected places.

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

As described above, the system management support apparatus 100 according to the present embodiment can display a possible location by selecting a location where a failure has occurred. 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 automatic change procedure creation process)
Next, the 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 shows a case where the IP address in setting is changed in the directed graph displayed on the left screen. In this case, the operation screen creating unit 104 displays a screen for inputting an address change. Then, when a change operation is performed by the user, the change procedure creation unit 108 creates and outputs a change procedure based on the content of the change and the directed graph data stored in the data storage unit 102. The example of FIG. 21 shows that a procedure has been created in which AAAA is stopped, address change settings are made, 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 premised on this example. This example corresponds to the configuration on the AP server side in the specific display example described above. Then, 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 show flowcharts of processing executed by the change procedure creating unit 108. In addition, in order to explain the processing in an easy-to-understand manner, FIGS. 23 to 25 show the progress of the procedure creation corresponding to the specific example shown in FIG. Hereinafter, the change procedure creation process will be described with reference to FIGS. Note that FIGS. 23 and 24 have the same flowchart. The procedure is divided into two in order to explain using a concrete example.

As shown in FIG. 23, the change procedure creation unit 108 first selects a node to be constructed. In the specific example, setting_BBBB is selected in step S1. Next, it is determined whether or not there is a link whose end point is the current target node. In the specific example, as shown in step S2, since the link is present, 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 start_BBBB that is the start point of the link as the target node and setting_BBBB that is the end point as the parent node.

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

Next, it is determined whether 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 specific example) is designated at the top of the construction procedure tree. ..

Next, it is determined whether the current target node matches the selected node. In the specific example, as shown as step S8, the target node (start_BBBB) does not match the selected node (setting_BBBB), so 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 the node that called the target node (start_BBBB), is set to the target node.

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

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

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

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

Next, it is determined whether or not there is a link whose end point is the current target node. 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 the start point node of the link is then selected as the target node. In the 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 set at the end of the construction procedure tree. In the specific example, as shown as step S18, start_BBBB which is a symmetric node of stop_BBBB is added to the end.

Next, it is again determined whether or not there is a link whose end point is the current target node. In the specific example, as shown in step S19, there is no link with the current target node as the end point, so the determination is No, and as shown in step S20, the entire construction procedure tree is output.

Note that the above example is an example of changing the parameters 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.

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

1) Improvement of the accuracy of design documents In the conventional technology, efforts have been made to operate the design document creation, the operation of the construction procedure document, and reduce both of them individually. However, it was necessary to confirm whether the information described in the design document was set in the system actually built. Data extraction from the already created deliverables was limited to displaying the module relevance from the development code.

After the system is constructed, the list of parameters that "would be used" and the application modules that were "to be installed" are listed, so errors are likely to occur.

On the other hand, according to the technique according to the present embodiment, the design document (directed graph) is automatically generated from the automatic construction script, so that the design document with high accuracy can be obtained.

2) Easily grasping the impact range and dependency within a single server In the conventional technology, to confirm the system configuration, the dependency between modules, and the influence points when making changes, understand the design document itself, The system must be assumed from the design document. Design documents are often created with an emphasis on listability, and even if applications and IP addresses installed in a single server are listed, in order to infer their dependencies and the affected parts, , I needed some knowledge. If there is insufficient knowledge or experience to understand and understand the entire design document, it will not be possible to understand the configuration of a large system or a system using advanced technology, and overlook related systems and parameters. I will end up.

For example, if you can understand the parameter of the IP address of the NW device, but you do not know the netmask, you will not know 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, although the mount point and device name of a disk mounted in Linux (registered trademark) can be understood, in the case of iSCSI storage, the influence of the initiator name in iSCSI, the VENDOR name at the time of multipath, and the PRODUCT name cannot be understood. Also, a unique ID called uuid is generated by an IP address or MAC address, but if you do not know this generation as well, you may miss the relationship.

On the other hand, according to the technique according to the present embodiment, since the effective graph and the information indicating the relationship are automatically generated from the automatic construction script, the above-mentioned oversight of the relationship can be eliminated.

3) Easier grasp of the influence range and dependency of the whole system In the conventional technology, in order to grasp the influence of the whole system in which servers depend on each other in a complicated manner, not only a design document of one server but also I had to read all the design documents that seemed to be relevant. This is a difficult task for a low skill person. This is because design documents are often created with a focus on listability for a single server, and it is difficult to describe all the relationships to other servers. In particular, if the parameters of the setting of the own server are set for other servers, and the effect of the setting being deviated, the list will be destroyed and it cannot be marked.

For example, load balancing by a load balancer depends on the DMZ address of the Web server under the load balancer. This should be described as "Used by the load balancer" as the IP address information of the Web server, and the relevance must be specified on the load balancer side as well, such as "Set the IP address of the Web server". This is an example that makes it 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 of "10.0.0.129/28" is accessible. However, whether it is possible to change this ACL access control to 10.0.0.0/25 is difficult unless the knowledge of NW and the system are properly grasped.

On the other hand, according to the technique according to the present embodiment, since the effective graph and the information indicating the relationship are automatically generated from the automatic construction script, it is possible to easily grasp the relationship as described above.

4) Easy maintenance of consistency between design documents and actual environment in continuous development The parameters and configuration of the system will change due to subsequent specification changes, additional development, and workarounds to 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, the effective graph and the information (design document) indicating the relationship are automatically generated from the automatic construction script, so that 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 technical engineers with the same level as the builder and the developer to fully understand the design document. Operation is expected. However, this leads to an increase in operating costs.

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

(Summary of Embodiments)
In this embodiment, input means for inputting a script describing a system construction procedure and predetermined components included in the script are extracted as nodes, and links between the nodes are created based on the dependency between the nodes. Then, the analysis means for storing the information of the node and the information of the link in the data storage unit, the information of the node and the information of the link are read from the data storage unit, and the directed graph is created from the information of the node and the information of the link, A system management support apparatus is provided, which is provided with an output unit that outputs the directed graph.

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

The predetermined component is, for example, a block in which the system construction processing is grouped according to the construction processing type in the script. The analysis unit may determine the dependency relationship based on the information described in the block, and the analysis unit determines the dependency relationship based on the procedure information included in the script. It may be that.

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

The output means may further include a relevance detecting unit that detects a relevance between nodes or a relevance between servers including nodes based on the relevance information. It is also possible to output a directed graph to which the information shown is added.

When a certain node in the directed graph is a failure point, a cause search means for extracting a node at an end point of a link starting from the node of the failure point as a suspected point of the failure from the data storage unit is further provided. May be

When an instruction to change the parameter of one or more nodes in the directed graph is received, a construction procedure for changing the parameter is created based on the dependency between the one or more node and another node. A change procedure creating means may be further provided.
<Appendix>
(Item 1)
Input means for inputting a script that describes the system construction procedure,
An analysis unit that extracts a predetermined component included in the script as a node, creates a link between the nodes based on a dependency between the nodes, and stores the node information and the link information in a data storage unit,
An output unit that reads out 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;
A system management support apparatus comprising:
(Item 2)
The predetermined component is a block in which the system construction process is grouped by type of construction process in the script.
The system management support apparatus according to item 1, wherein
(Section 3)
The analyzing means determines the dependency based on the information described in the block.
The system management support device according to the second aspect.
(Section 4)
The analysis means determines the dependency based on the procedure information included in the script.
The system management support apparatus according to any one of the first to third aspects.
(Section 5)
The analyzing unit extracts parameters used in nodes, creates association information indicating association of parameters between nodes, and stores the association information in the data storage unit.
The system management support apparatus according to any one of the first to fourth aspects.
(Section 6)
Further comprising a relevance detecting means for detecting a relevance between the nodes or a relevance between the servers including the nodes based on the relevance information,
The output means outputs a directed graph to which information indicating the relevance is added.
The system management support apparatus according to item 5, wherein
(Section 7)
When a node in the directed graph is a failure point, as a suspected point of the cause of the failure, a cause searching unit that extracts a node at the end point of the link starting from the node at the failure point from the data storage unit.
The system management support apparatus according to any one of the first to sixth items, further comprising:
(Section 8)
When an instruction to change the parameter of one or more nodes in the directed graph is received, a construction procedure for changing the parameter is created based on the dependency between the one or more node and another node. Change procedure creation means
The system management support apparatus according to any one of items 1 to 7, further comprising:
(Section 9)
A system management support method executed by a system management support device, comprising:
An input step to enter a script that describes 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 between the nodes, and storing node information and link information in a data storage unit,
An output step of reading the node information and the link information from the data storage unit, creating a directed graph from the node information and the link information, and outputting the directed graph;
A system management support method comprising:
(Item 10)
A program for causing a computer to function as each unit in the system management support apparatus according to any one of items 1 to 8.

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

100 system management support apparatus 101 analysis unit 102 data storage unit 103 conversion unit 104 operation screen creation unit 105 related information search unit 106 fault location setting unit 107 cause search unit 108 change procedure creation unit

Claims (8)

Input means for inputting a script that describes the system construction procedure,
A plurality of predetermined components included in the script are extracted as a plurality of nodes, a link between the nodes is created based on the dependency between the nodes, and the node information and the link information are stored in the data storage unit. Analytical means,
An output unit that reads out 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.
When a certain node in the directed graph is a failure point, as a suspected point of the cause of the failure, a cause search means for extracting the node of the end point of the link starting from the node of the failure point from the data storage unit ,
Each of the plurality of predetermined components is a block in which the description of the system construction process is divided into blocks in the script, and the construction process includes software installation, setting of the installed software, and start of the set software. A system management support apparatus , which is any one of a plurality of construction processes including a . Input means for inputting a script that describes the system construction procedure,
A plurality of predetermined components included in the script are extracted as a plurality of nodes, a link between the nodes is created based on the dependency between the nodes, and the node information and the link information are stored in the data storage unit. Analytical means,
An output unit that reads out 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.
When an instruction to change the parameter of one or more nodes in the directed graph is received, a construction procedure for changing the parameter is created based on the dependency relationship between the one or more nodes and another node. And a change procedure creating means ,
Each of the plurality of predetermined components is a block in which the description of the system construction process is divided into blocks in the script, and the construction process includes software installation, setting of the installed software, and start of the set software. A system management support apparatus , which is any one of a plurality of construction processes including a . Said analyzing means, said block based on the information in the system management support apparatus according to claim 1 or 2, characterized in that determining the dependencies. The system management support apparatus according to any one of claims 1 to 3, wherein the analysis unit determines the dependency relationship based on procedure information included in the script. The analysis means extracts parameters used in the construction process corresponding to the nodes , and creates relevance information indicating whether the parameters between the nodes match, do not match, or have an inclusion relation. The system management support apparatus according to claim 1, wherein the relevance information is stored in the data storage unit. A system management support method executed by a system management support device, comprising:
An input step to enter a script that describes the system construction procedure,
A plurality of predetermined components included in the script are extracted as a plurality of nodes, a link between the nodes is created based on the dependency between the nodes, and the node information and the link information are stored in the data storage unit. Analysis step,
An output step of reading the information of the node and the information of the link from the data storage unit, creating a directed graph from the information of the node and the information of the link, and outputting the directed graph.
When a node in the directed graph is a failure point, as a suspected point of the cause of the failure, a cause search step of extracting the node of the end point of the link starting from the node of the failure point from the data storage unit ,
Each of the plurality of predetermined components is a block in which the description of the system construction process is divided into blocks in the script, and the construction process includes software installation, setting of the installed software, and start of the set software. A system management support method, wherein the system management support method is any one of a plurality of construction processes including . A system management support method executed by a system management support device, comprising:
An input step to enter a script that describes the system construction procedure,
A plurality of predetermined components included in the script are extracted as a plurality of nodes, a link between the nodes is created based on the dependency between the nodes, and the node information and the link information are stored in the data storage unit. Analysis step,
An output step of reading the information of the node and the information of the link from the data storage unit, creating a directed graph from the information of the node and the information of the link, and outputting the directed graph.
When an instruction to change the parameter of one or more nodes in the directed graph is received, a construction procedure for changing the parameter is created based on the dependency relationship between the one or more nodes and another node. And a change procedure creation step ,
Each of the plurality of predetermined components is a block in which the description of the system construction process is divided into blocks in the script, and the construction process includes software installation, setting of the installed software, and start of the set software. A system management support method, wherein the system management support method is any one of a plurality of construction processes including . A program for causing a computer to function as each unit in the system management support apparatus according to claim 1.

Images