JPWO2018225200A1 - Service template creation support apparatus and method - Google Patents

Abstract

With respect to the second service template created by sequentially arranging a plurality of first service templates in which processing contents for the target management resource are defined according to the execution order, the respective user confirmation parts are assigned to the second service template. The parts constituting the second service template are rearranged so that the configuration-changed parts are rearranged to the rear of the second service template. At this time, the second service template As for rearrangement of the configuration acquisition part included in and the configuration change part immediately before, the configuration acquisition part depends on the data of the configuration change part immediately before, or the management resource that is the target of the configuration acquisition part is the configuration change part It is not implemented when the managed resource can be affected by.

Description

  The present invention relates to a service template creation support apparatus and method, and is suitably applied to, for example, a management server computer in which an operation automation tool capable of automating operation / maintenance work of a computer system is installed.

  In recent years, in order to improve the efficiency of operation / maintenance operations of computer systems that include large-scale and diverse management resources such as data centers, a series of processing steps of operation / maintenance operations are defined as service templates. / Tools that can automate maintenance operations (IT operation automation tools) have been commercialized.

  In this type of IT operation automation tool, for each management resource such as a host device, storage device, network device, OS (Operating System), and application, a service template that defines the basic processing flow for that management resource is created. Furthermore, by combining service templates of a plurality of types of management resources, a service template that realizes a use case that crosses a plurality of types of management resources can be created.

  Each service template for each management resource includes parts such as a configuration acquisition part, a user confirmation part, and a configuration change part. A configuration acquisition component (hereinafter also referred to as G component as appropriate) acquires configuration information of the management resource by using an API (Application Programming Interface) from an external resource or a management tool of the target management resource. This is a part including processing for defining the contents of the configuration change based on the configuration. The user confirmation part (hereinafter, also referred to as a U part as appropriate) is a part including processing for requesting confirmation and a response from the user for the configuration change content defined by the configuration acquisition part. Furthermore, the configuration change component (hereinafter, also referred to as E component as appropriate) performs a process of changing configuration information for external resources or executing a change for each management resource management tool using an API. Including parts.

  Patent Document 1 below discloses an invention for creating a workflow that matches a deployment destination system when workflows are deployed on different systems, and Patent Document 2 can be used to create a workflow. A method of using resources more effectively is disclosed.

JP 2012-146089 A JP 2003-132187 A

  By the way, when creating a new service template by combining a plurality of existing service templates (hereinafter referred to as existing service templates), simply arranging the existing service templates in order confirms the user behind the new service template. When the system receives an instruction for interrupting the subsequent processing from the user at the time of execution of the component, it takes time and effort to roll back the configuration change processing executed so far.

  In addition, simply arranging existing service templates in order will cause user confirmation parts included in each existing service template to be scattered in the newly created service template, and the user has to perform confirmation processing many times. There is a problem that makes the user feel annoying.

  As a means for solving such a problem, for example, the order of the parts of each existing service template is changed so that the user confirmation part is shifted to the front of the new service template, and the user confirmation process in each existing service template is summarized. It is conceivable that a new service template is reconfigured so that the configuration is changed after the previous operation.

  However, according to this method, when a certain management resource (referred to as “resource A”) is affected by a configuration change component, the configuration change component and information on “resource A” behind the configuration change component Are rearranged with the configuration acquisition parts of other service templates that acquire the "resource A" information acquired by the configuration acquisition parts before the rearrangement and " Since the information of “resource A” may be different, the execution result may be unintended.

  The present invention has been made in view of the above points, and proposes a service template creation support apparatus and method that can solve the above-mentioned problems all at once and can further improve the efficiency of the operation / maintenance work of the computer system. It is what.

  In order to solve this problem, in the present invention, a plurality of first service templates in which processing contents for a target management resource are defined are sequentially arranged according to the execution order of the first service templates. In the service template creation support apparatus that supports creation of the second service template, the first service template is created by sequentially arranging a plurality of parts each having a defined processing content in accordance with an execution order of the parts. As the types of parts, a configuration acquisition part including a process for acquiring configuration information of the target management resource, a user confirmation part including a process for obtaining confirmation or a response from the user, and a configuration change of the target management resource. A configuration change component including a process to be executed, and at least the second A service template creation unit that provides the user with a service template creation platform, which is an environment for creating a service template, and the second service template created by the user using the service template creation platform, The second service template so that each of the user confirmation parts is shifted to the front of the execution order in the second service template, and the configuration change part is shifted to the rear of the execution order of the second service template A service template reconfiguration unit that rearranges the components that constitute the component, and the service template reconfiguration unit includes the configuration acquisition component included in the second service template, and the configuration acquisition component immediately before the configuration acquisition component. About rearrangement with the reconfigured parts Based on the definition information of the second service template, the configuration acquisition component depends on data immediately before the configuration change component, or the management resource that is the target of the configuration acquisition component is affected by the configuration change component. It is not implemented when it is a management resource that can be received.

  In the present invention, the second service template created by sequentially arranging a plurality of first service templates in which the processing contents for the target management resource are defined according to the execution order of the first service template. In the service template creation support method executed by the service template creation support apparatus that supports creation, the first service template is configured to sequentially arrange a plurality of parts, each of which has processing contents defined, in accordance with the execution order of the parts. A configuration acquisition component that includes a process for acquiring configuration information of the target management resource as a type of the component that is created, a user confirmation component that includes a process for obtaining confirmation or a response from the user, and the management resource that is the target Configuration change parts that include processing to execute configuration changes A first step of providing the user with a service template creation base, which is an environment for creating at least the second service template, and the user created by the user using the service template creation base For the second service template, the user confirmation parts are shifted to the front of the execution order in the second service template, and the configuration change parts are shifted to the rear of the execution order in the second service template. A second step of rearranging the parts constituting the second service template, wherein the service template creation support device is included in the second service template. The configuration acquisition part and immediately before the configuration acquisition part For rearrangement with configuration change parts, based on the definition information of the second service template, the configuration acquisition part depends on data immediately before the configuration change part, or is the target of the configuration acquisition part This is not performed when the management resource is a management resource that can be affected by the configuration change component.

  According to the service template creation apparatus and method of the present invention, it is possible to prevent an unexpected error caused by rearrangement of the parts of the created second service template from occurring when the second service template is executed. Thus, it is possible to effectively avoid the occurrence of a situation in which a rollback of the configuration change occurs during execution of the second service template or a situation in which the user has to frequently perform confirmation work.

  According to the present invention, it is possible to realize a service template creation support apparatus and method that can facilitate the creation and execution of a service template, and thereby further increase the efficiency of the operation / maintenance work of the computer system.

It is a block diagram which shows the whole structure of the computer system by this Embodiment. (A) And (B) is a figure where it uses for description of a service template. It is a figure with which it uses for description of rearrangement of the components in a service template. It is a figure which shows the structural example of a service template creation screen in a schematic line. FIG. 6 is a diagram schematically illustrating a configuration example of a property setting screen. It is a graph which shows the structural example of a service template management table. It is a chart showing an example of composition of a parts management table. It is a graph which shows the structural example of a property management table. It is a graph which shows the structural example of a step management table. It is a chart which shows the example of a structure of an execution flow management table. It is a chart showing an example of composition of a data flow management table. It is a chart which shows the example of a structure of a property GUI setting management table. It is a graph which shows the structural example of the dependence management table between management resources. It is a flowchart which shows the process sequence of a component rearrangement process. It is a flowchart which shows the process sequence of a service template reconstruction process. It is a flowchart which shows the process sequence of a structure change part arrangement | positioning process. It is a flowchart which shows the process sequence of a component movement process. It is a flowchart which shows the process sequence of the data dependence determination process between components. It is a flowchart which shows the process sequence of the dependency determination process between management resources. It is a flowchart which shows the process sequence of a related management resource estimation process. It is a flowchart which shows the process sequence of a user confirmation component grouping process. It is a flowchart which shows the process sequence of a user confirmation component aggregation process. It is a flowchart which shows the process sequence of an adjacent user confirmation component aggregation process. It is a flowchart which shows the process sequence of a parallel user confirmation component aggregation process. It is a flowchart which shows the process sequence of an aggregation user confirmation component division process. (A)-(C) is a schematic diagram with which it uses for description of a service template reconstruction process. It is a schematic diagram with which it uses for description of the data dependence relationship between components. It is a figure which shows the screen structure of a dependence inquiry screen. (A)-(C) are the schematic diagrams with which it uses for description of a user confirmation component aggregation process. It is a figure which shows the structural example of the confirmation screen with respect to the aggregation user confirmation component which consolidated the adjacent user confirmation component. It is a figure which shows the structural example of the confirmation screen with respect to the aggregation user confirmation component which consolidated the parallel user confirmation component.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(1) Configuration of Computer System According to this Embodiment FIG. 1 shows a computer system 1 according to this embodiment. This computer system 1 includes an IT system 2 provided in a data center or a company, a management computer group 3 composed of a plurality of management computers used by managers for each management resource type of the IT system 2, and a management system A management server computer 4 that performs operation and maintenance of the IT system 2 via a computer group 3 is provided, and these are connected via a network 5.

  The IT system 2 includes, for example, one or a plurality of server apparatuses 6, one or a plurality of storage apparatuses 7, and one or a plurality of network apparatuses 8, and the server apparatus 6, the storage apparatus 7, and the network apparatus 8 are included. They are connected to each other via a network 5.

  The server device 6 is composed of, for example, a general-purpose server device in which software corresponding to the user's business content is installed, and reads / writes data from / to the storage device 7. Virtualization software such as VMware (registered trademark) is installed in the server device 6 as necessary, and one or more virtual machines (VMs) are installed on the server device 6 based on the virtualization software. Is set.

  The storage device 7 is composed of, for example, a disk array device on which a plurality of hard disk devices are mounted, and provides a storage area for reading and writing data to the server device and the virtual machine. The network device 8 is composed of, for example, a network device such as a SAN (Storage Area Network) switch or an FC (Fibre Channel) switch that constitutes a network (not shown) that connects the server device 6 and the storage device 7.

  The management computer group 3 includes a server management computer 9, a storage management computer 10, and a network management computer 11. The server management computer 9 is a computer used by an administrator who manages the server device 6 in the IT system 2 or an administrator who manages a virtual machine set on each server device 6. However, a management computer used by an administrator who manages the virtual machine may be provided separately from the server management computer 9.

  The storage management computer 10 is a computer used by an administrator who manages the storage device 7 in the IT system 2. The network management computer 11 is a computer used by an administrator who manages the network device 8 in the IT system 2.

  The server management computer 9, the storage management computer 10 and the network management computer 11 each manage a command corresponding to an operation of an administrator or a command corresponding to an instruction given from the management server computer 4 as will be described later. By transmitting to the device 6, the storage device 7, or the network device 8, the instructed setting for the server device 6, the storage device 7, or the network device 8 is performed.

  The management server computer 4 is a general-purpose server device that is used by a system administrator who manages the entire computer system 1 to create a service template and execute the created service template. A CPU (Central Processing Unit) 20, The main storage device 21, the auxiliary storage device 22, the input device 23, the display device 24, and the communication device 25 are provided with hardware resources.

  The CPU 20 is a processor that controls operation of the entire management server computer 4. The main storage device 21 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 20. When the management server computer 4 is started or necessary, the operation automation software 26 stored in the auxiliary storage device 22 is read out to the main storage device 21, and the operation automation software 26 is executed by the CPU 20 to create a service template. In addition, various processes as described later regarding the execution are executed.

  The auxiliary storage device 22 is composed of a large-capacity storage device such as a hard disk device or an SSD (Solid State Drive), and is used to hold various programs and control data for a long period of time.

  The input device 23 is composed of, for example, a mouse and a keyboard, and is used when the user performs various inputs and the like on the management server computer 4. The display device 24 is composed of, for example, a liquid crystal display and is used for displaying a GUI (Graphical User Interface) and necessary information.

  The communication device 25 is composed of, for example, a NIC (Network Interface Card) or the like, and the management server computer 4 communicates with the server device 6, the storage device 7, or the network device 8 of the IT system 2 via the network 5. It performs protocol control when communicating with the server management computer 9, the storage management computer 10, or the network management computer 11 of the computer group 3.

(2) Function of Operation Automation Software (2-1) Component Rearrangement Function According to this Embodiment Next, the function of the operation automation software 26 installed in the management server computer 4 will be described. In the following, the user confirms the configuration acquisition part (G part) including the process of acquiring the configuration and defining the configuration change content based on the acquired configuration, and the configuration change content defined by the configuration acquisition part. For example, FIG. 2 (A) or FIG. 2 (A) or FIG. 2 (A) or FIG. It is assumed that a service template that defines a basic series of processes for each management resource as shown in B) has already been created and registered.

  FIG. 2A shows a service template 30 in which a series of processes for creating a logical volume having a capacity designated by the user in the storage apparatus 7 designated by the user is defined. A configuration acquisition component, a user confirmation component “U1”, and a configuration change component “E1”. In the service template 30, processing flows in accordance with the direction of the arrow connecting each part (configuration acquisition part, user confirmation part, configuration change part, etc.). The same applies to each service template below.

  In the configuration acquisition component “G1”, information about the designated storage device 7 is obtained from the storage management computer 10, and based on the obtained information, the specified capacity of the pool created in the storage device 7 is obtained. A process for automatically selecting the optimal pool for creating a logical volume is defined.

  In addition, the user confirmation component “U1” presents the user with information on the pool automatically selected by “G1” (displayed on the display device 24), thereby indicating to the user whether or not a logical volume can be created on the pool. The process to check is defined. Further, in the configuration change component “E1”, a logical volume having a specified capacity is created on the pool automatically selected by “G1”, and the specified server device 6 or a virtual machine in the server device 6 is transferred to this logical volume. A process to set the path is defined.

  FIG. 2B shows a service template 31 in which processing for setting an application that uses a specified logical volume in a specified server device 6 or virtual machine is defined. , A user confirmation part “U3” and a configuration change part “E3”.

  In the configuration acquisition component “G3”, a process of automatically selecting an optimum application corresponding to the OS installed in the designated server device 6 or virtual machine is defined. The user confirmation component “U3” defines a process for confirming to the user whether the server device 6 or the virtual machine can be mounted by presenting information related to the application automatically selected in “G3” to the user. ing.

  Furthermore, with the configuration change component “E3”, the process of mounting the application automatically selected in “G3” on the specified server device 6 or the virtual machine and further setting the application to use the specified logical volume. Is defined.

  In the present invention, a service template 32 as shown in the upper part of FIG. 3 is executed by executing a series of processes crossing a plurality of types of management resources by combining such basic service templates 30 and 31 for each management resource. This is an invention related to automatic rearrangement of parts such as configuration acquisition parts, user confirmation parts, and configuration change parts.

  The operation automation software 26 (FIG. 1) is an operation automation tool for automating and improving the operation of the IT system 2, and includes a service template creation base, which is an environment for creating a service template, and the created service template. Provides a service template execution platform that is an environment for executing.

  The service template mainly includes components such as a configuration acquisition component, a user confirmation component, and a configuration change component, and properties that store execution values of the components. The properties include an input property that sets an input value (data input source, value, etc.) to the part, and an output property that sets an output value (data output destination, etc.) to the part. However, in the following, input properties and output properties are collectively referred to as properties when it is not necessary to distinguish them.

  In the management server computer 4, based on the operation automation software 26, a service template creation screen for creating a service template and a property GUI screen for setting properties for each service template are displayed on the display device 24 by a predetermined operation. be able to.

  FIG. 4 shows a configuration example of the service template creation screen 40 among these screens. As is clear from FIG. 4, the service template creation screen 40 includes an existing service template list field 41, a flow editor field 42, a property display field 43, and the like.

  The existing service template list field 41 displays a list of basic service templates (existing service templates) already created for each management resource (more precisely, a list of icons 44 respectively associated with the existing service templates). The flow editor field 42 is an area for creating a new service template that combines these existing service templates.

  The user sequentially pastes the icon 44 corresponding to the desired existing service template from the icons 44 displayed in the existing service template list field 41 into the flow editor field 42 by drag and drop. It is possible to create a new service template 47 combining existing service templates by sequentially connecting the icons 45 of these existing service templates displayed in the flow editor field 42 with arrows 46 in accordance with the desired execution order. it can.

  At this time, in the flow editor field 42, in each existing service template icon 45, a component icon 48 representing each component such as a configuration acquisition component, a user confirmation component and a configuration change component constituting the existing service template is displayed. They are displayed in a state where they are arranged in the execution order of the components and are sequentially connected by arrows according to the execution order.

  In each component icon 48, a character string representing an identifier assigned to the corresponding component is displayed. In the example of FIG. 4, “G ○” (○ is a number unique to the configuration acquisition part) for the configuration acquisition part, “U ○” (○ is a number unique to the user confirmation part) for the user confirmation part, The text “E ○” (○ is a number unique to the configuration acquisition part) is displayed for the configuration change part, and the character string “X ○” (○ is a number unique to the part) is displayed for the other parts.

  Further, in the property display field 43, the entire existing service template corresponding to the icon 45 selected by clicking among the icons 45 corresponding to each existing service template displayed in the flow editor field 42, or the existing service template is displayed. The set value of each property set for each component is displayed.

  A confirmation step aggregation button 49 is displayed on the upper right of the service template creation screen 40. The user creates a new service template 47 in the flow editor field 42 as described above, and then clicks this confirmation step aggregation button 49, thereby making each of the new service templates 47 constituting the new service template 47 as described later. The management server computer 4 can execute the rearrangement of parts. Details of such a function related to component rearrangement (hereinafter referred to as a component rearrangement function) will be described later.

  FIG. 5 shows a configuration example of the property GUI screen. This property GUI screen 50 is a screen for the user to manually set the properties of existing service templates and components when executing the service template 47 using the service template execution platform function.

  The property GUI screen 50 shown in FIG. 5 is for an existing service template in which a process such as “setting a logical volume with a specified capacity in a storage device and setting a path between the logical volume and a specified host” is defined. The storage device 7 to create the logical volume, the pool in the storage device 7 to create the logical volume, the capacity of the logical volume, and the host (server device 6 or 3 is an example of a property GUI screen for a user to specify (virtual machine).

  In the example of FIG. 5, the property GUI screen 50 includes a host designation field 51, a storage device designation field 52, a pool designation field 53, and a capacity designation field (not shown).

  The user clicks a pull-down button 54 provided on the right side of the host designation field 51 to display a pull-down menu (not shown) in which identifiers of all server devices 6 and virtual machines existing in the system are posted. Can do. Also, the user can designate a server device 6 or a virtual machine corresponding to the identifier as a host to which the logical volume is connected by selecting a desired identifier from the identifiers displayed in this pull-down menu. . The identifier of the storage device 7 designated at this time is displayed in the storage device designation column 52.

  Further, the user can display a pull-down menu (not shown) in which identifiers of all storage devices 7 existing in the system are displayed by clicking a pull-down button 55 provided on the right side of the storage device designation column 52. . In addition, the user can specify the storage device 7 corresponding to the identifier as the storage device that is the creation destination of the logical volume by selecting a desired identifier from the identifiers displayed in this pull-down menu. The identifier of the storage device 7 designated at this time is displayed in the storage device designation column 52.

  Furthermore, the user clicks a pull-down button 56 provided on the right side of the pool designation column 53, and the identifiers of all pools existing in the storage device 7 whose identifiers are displayed in the storage device designation column 52 are posted. A pull-down menu 57 can be displayed. Further, the user can designate a pool corresponding to the identifier as a pool where the logical volume is created by selecting a desired identifier from the identifiers displayed in the pull-down menu 57. The identifier of the designated pool is displayed in the pool designation field 53.

  Further, the user can designate the capacity of the logical volume by inputting a desired capacity in a capacity designation field (not shown) via the input device 23 (FIG. 1).

  By the way, when creating and executing a new service template that combines existing service templates as described above, simply arranging existing service templates in order would result in existing services placed behind the created service template. When executing a user confirmation part included in the template, if the system receives an instruction from the user to suspend the subsequent processing, roll the configuration change made when executing the configuration change part in the existing service template prior to this There is an effort to back up.

  As is clear from the upper part of FIG. 3, simply arranging the existing service templates 30, 30 ′, 31 in order, each of the existing service templates 30, 30 ′, 31 in the created service template 32. The included user confirmation parts (“U1” to “U3”) are scattered, and the user feels annoyed that confirmation must be performed many times when the new service template 32 is executed.

  As a means for solving such a problem, for example, as shown in the lower part of FIG. 3, the order of the parts constituting each of the existing service templates 30, 30 ′ and 31 is changed, and the user confirmation parts are changed in the service template. A method of reconfiguring a new service template so that the configuration change ("E1" to "E3") is performed after the user confirmation based on these user confirmation parts is performed in advance, in the forward order of execution. Is also possible.

  However, there is often a relationship that is not explicitly defined between managed resources. For this reason, when a certain management resource (referred to as “resource A”) is affected by a configuration change component, the configuration change component and the information of “resource A” behind the configuration change component are acquired. If the configuration acquisition component of the service template is rearranged, the information of “resource A” acquired by the configuration acquisition component before rearrangement and the information of “resource A” acquired by the configuration acquisition component after rearrangement Since the information may be different, the execution result may be unintended.

  For example, it is assumed that the created new service template is as shown in the upper part of FIG. Here, the two existing service templates 30 and 30 ′ “volume provisioning 1” and “volume provisioning 2” both have the designated capacity in the designated storage apparatus 7 as described above with reference to FIG. A service template in which processing for creating a logical volume is defined. Further, the existing service template 31 of “application setting” is a service template in which processing for setting an application that uses a specified logical volume in the specified server device 6 is defined as described above with reference to FIG. It is.

  In this new service template 32, a setting is made to set a logical volume of “70 GB” in the property of the configuration change component “E1” of the existing service template 30 “Volume provisioning 1”. It is assumed that the setting of setting the logical volume of “70 GB” is made in the property of the reconfiguration component “E2” of the existing service template 30 ′.

  In this case, if the component parts are not rearranged, a pool with a remaining capacity of “100 GB” is selected when the configuration acquisition part “G1” of the existing service template 30 “Volume Provisioning 1” is executed. Since the logical volume of “70 GB” is set on the pool when executing the configuration change part “E1” of the existing service template 30, the remaining capacity of the pool becomes “30 GB”, The pool is not selected when the configuration acquisition component “G2” of the existing service template 30 ′ “provisioning 2” is executed.

  However, in this example, as shown in the lower part of FIG. 3, when the user confirmation part is shifted to the front of the service template 32 and the new service template 32 is reconfigured so that all configuration changes are made later, “Volume Provisioning 1 The same pool is selected both when the configuration acquisition component “G1” of the existing service template 30 named “G2” is executed and when the configuration acquisition component “G2” of the existing service template 30 ′ “volume provisioning 2” is executed. As a result, an error occurs when the configuration change component “E2” of the existing service template 30 ′ “Volume Provisioning 2” is executed.

  Such an error occurs when the management resource that is the target of the configuration acquisition component (that is, the management resource that is the target of information collection of the configuration acquisition component) is changed when the configuration change component and the configuration acquisition component behind it are rearranged. If the management resource is the same as the management resource that is the target of the configuration change part (that is, the management resource whose configuration is changed by the configuration change part), or the management resource that is the target of the configuration acquisition part is affected by the configuration change part Occurs when included in an acceptable management resource.

  Here, “a management resource that is subject to a configuration acquisition component can be affected by the configuration change component” means that the management resource that is the target of the configuration acquisition component is a configuration change component in front of it. The management resource that is the target of the configuration acquisition component (“pool” in the example of FIG. 3) is not the same as the management resource that is the target of the configuration, but the relationship between “E1” and “G2” described above with reference to FIG. In the case of being included in a management resource that can be influenced as a result of a change in the management resource ("logical volume" in the example of FIG. 3) that is the target of the configuration change component ahead of that ("pool" in the example of FIG. Is included in the management resource that is consequently affected by the change of the “logical volume”.

  Therefore, in the management server computer 4 of the present embodiment, when a new service template is created by combining a plurality of existing service templates, a user confirmation component is newly added within a range in which the above problem does not occur. A component rearrangement function for rearranging the components of the service template is mounted so that the components in the service template are shifted to the front of the execution order and the configuration change components are shifted to the rear of the execution order of the new service template as much as possible.

  In practice, when a new service template is created by combining a plurality of existing service templates, the management server computer 4 affects each of the configuration change parts included in these existing service templates. A management resource that can be received (hereinafter, this is appropriately referred to as a related management resource of the configuration change component) is estimated from the definition information of the new service template.

  Then, when the management server computer 4 rearranges the configuration change component and the configuration acquisition component behind it, the management resource that is the target of the configuration acquisition component is the configuration change component immediately before that based on the above estimation result. The configuration change parts and the configuration acquisition parts are rearranged only when they are not the same as the target management resources and are not included in the related management resources of the configuration change parts.

  As a method of “estimating the related management resource of the configuration change component from the definition information of the new service template”, the following methods can be used for each of the following two patterns.

(Pattern 1) When the input property data of a configuration change part is inherited from the output data of another part In this case, the configuration change is made to the management resource targeted by the configuration acquisition part immediately before the configuration change part. Estimated as a related management resource for parts.

  For example, in the upper example of FIG. 3, the input property data of the configuration change part (E part) “E1” of the existing service template 30 “Volume Provisioning 1” is the configuration acquisition part (G part) “G1”. Is inherited from the output data. Accordingly, in this case, it can be estimated that the “pool” is included in the related management resource of the configuration change component “E1”.

  On the other hand, the management resource from which the configuration acquisition component “G2” of the existing service template 30 ′ “volume provisioning 2” in the upper part of FIG. 3 acquires information is also “pool”. Therefore, since the management resource that is the target of the configuration acquisition component “G2” is included in the related management resource of the configuration change component “E1”, the configuration change component “E1”, the configuration acquisition component “G2” Sorting is not performed.

(Pattern 2) When the input property data of the configuration change component is input by the user In this case, the related management resource of the configuration change component is estimated based on the input property data of the configuration change component.

  For example, in the example of FIG. 3, the input property of the reconfiguration component “E1” of the existing service template 30 “Volume Provisioning 1” is manually defined by the user using the property GUI screen 50 as shown in FIG. Consider the case of the specification to be. In this example, the user designates from the pull-down the storage apparatus 7 from which configuration information is to be acquired (logical volume should be created) and the pool in the storage apparatus 7 when executing the configuration change component “E1”. At this time, it can be seen from the setting information on the property GUI screen 50 that the management resources for which each pull-down acquires information are “storage” and “pool”, respectively. Therefore, in this case, “storage” and “pool” are included in the related management resources of the configuration change component “E1”.

  On the other hand, the management resource from which the configuration acquisition component “G2” of the service template “Volume Provisioning 2” in the upper part of FIG. 3 acquires information is also “pool”. Therefore, also in this example, since the management resource that is the target of the configuration acquisition part “G2” is included in the related management resource of the configuration change part “E1”, the configuration change part “E1” and “G2 Is not rearranged with the configuration acquisition part.

  As means for realizing the component rearrangement function according to the present embodiment as described above, the operation automation software 26 includes a service template creation unit 60, a service template reconfiguration unit 61, and a service template as shown in FIG. An execution unit 64 is provided. The service template reconfiguration unit 61 includes a management resource dependency estimation unit 62 and a management resource dependency presentation unit 63. Further, in the auxiliary storage device 22 of the management server computer 4, as shown in FIG. 1, a service template management table 65, a parts management table 66, a property management table 67, a step management table 68, an execution flow management table 69, a data flow management. A table 70, a property GUI setting management table 71, and a management resource dependency management table 72 are stored.

  The service template creation unit 60 is a program having a function of providing a service template creation base that is an environment for creating a service template. The service template creation unit 60 displays the service template creation screen 40 described above with reference to FIG. 4 on the display device 24, and executes processing for supporting creation of a new service template using the service template creation screen 40.

  In addition, the service template reconfiguration unit 61 has a function of performing the above-described automatic component rearrangement (service template reconfiguration) for a new service template created using the service template creation screen 40 or the like. It is.

  The inter-management resource dependency estimation unit 62 constitutes a part of the service template reconfiguration unit 61, and when the service template reconfiguration unit 61 reconfigures the service template, the target of the configuration change component to be rearranged This is a program having a function of estimating the dependency between the management resource that becomes and the management resource that is the target of the configuration acquisition component behind it. Note that the “dependency between management resources” refers to a relationship in which the configuration change part and the management resource that is the target of the configuration acquisition part are the same, or the management resource of the configuration acquisition part is included in the related management resource of the configuration change part Point to.

  Further, the inter-management resource dependency presentation unit 63 constitutes a part of the service template reconfiguration unit 61, and the dependency inquiry screen 90 described later with reference to FIG. It is a program having a function of presenting it to the user as it is displayed and inquiring to the user whether or not these two parts can be rearranged.

  Furthermore, the service template execution unit 64 is a program having a function of providing a service template execution base that is an environment for executing a service template created using the service template creation screen 40 or the like. The service template execution unit 64 corresponds to a management computer (server management computer 9 (FIG. 1), storage management computer 10 (FIG. 1) or network management computer 11 ( By transmitting to FIG. 1)), a series of processes defined by the service template is executed.

  On the other hand, the service template management table 65 is a table used for managing service templates (existing service templates) that have already been created. As shown in FIG. 6, a number column 65A, a template ID column 65B, and a template A name field 65C is provided. In the service template management table 65 of FIG. 6, one record (row) corresponds to one existing service template.

  In the number column 65A, the number (serial number) assigned to the record (row) in the service template management table 65 is stored. The template ID column 65B stores an identifier (template ID (IDentification)) unique to the existing service template assigned to the corresponding existing service template. Further, the template name column 65C stores the name of the existing service template (service template name) arbitrarily set by the user for the corresponding existing service template.

  Therefore, in the example of FIG. 6, the existing service template corresponding to the record assigned the number “1” in the service template management table 65 is the template “App A environment construction” assigned the template ID “TEMPL1”. It is shown that the name is an existing service template.

  This service template management table 65 is displayed when the icons 44 and 45 (FIG. 4) of the existing service templates are displayed in the existing service template list field 41 and the flow editor field 42 of the service template creation screen 40. The template ID and the template name are referred to when the icons 44 and 45 are displayed.

  The part management table 66 is a table used for managing each part such as a configuration acquisition part, a user confirmation part, and a configuration change part used in any existing service template, as shown in FIG. Are provided with a number column 66A, a component ID column 66B, a processing type column 66C, and a target management resource type column 66D. In the component management table 66 of FIG. 7, one record (row) corresponds to one component.

  The number column 66A stores the number (serial number) assigned to the record in the component management table 66, and the component ID column 66B stores an identifier (component ID) unique to the component assigned to the corresponding component. Is stored. The processing type column 66C stores the type of processing (configuration acquisition, user confirmation, configuration change, etc.) performed by executing the corresponding component, and the target management resource type column 66D executes the corresponding component. Stores the type of the target resource.

  Therefore, in the example of FIG. 7, the part corresponding to the record assigned the number “2” in the part management table 66 has the part ID “PGL2”, the processing type “configuration acquisition”, and “Pool”. It is shown that it is a target part (configuration acquisition part).

  The component management table 66 includes characters (such as a configuration acquisition component, a user confirmation component, or a configuration change component) indicating the type of component corresponding to each component icon 48 displayed in the flow editor field 42 of the service template creation screen 40. “G1”, “U1”, “E1”, etc.) are displayed.

  The property management table 67 is a table used for managing each existing service template and properties (input property and output property) to be set for each component constituting the existing service template, as shown in FIG. Are provided with a number column 67A, a property ID column 67B, a belonging element column 67C, a property name column 67D, and a type column 67E. In the property management table 67 of FIG. 8, one record (row) corresponds to one property.

  The number column 67A stores the number (communication number) assigned to the record in the property management table 67, and the property ID column 67B stores an identifier (property ID) unique to the property assigned to the corresponding property. ) Is stored.

  The belonging element column 67C stores an identifier (template ID and component ID) of an existing service template (“TEMPL”) or component (“PLG”) in which the corresponding property is defined, and the property name column 67D. , The property name (property name) arbitrarily set by the user for the corresponding property is stored.

  Furthermore, the type column 67E stores the corresponding property type (input property or output property). In the present embodiment, “IN” is stored in the type column 67E when the corresponding property is an input property, and “OUT” is stored in the type column 67E when the corresponding property is an output property.

  Therefore, in the example of FIG. 8, for example, “PROP1” is “input property (“ IN ”)” whose property name is “host”, and “PROP2” is “input property (“ IN ”) whose property name is“ storage ”. ) ”,“ PROP3 ”and“ PROP4 ”are“ input properties (“IN”) ”whose property name is“ volume capacity ”, and each of these properties“ PROP1 ”to“ PROP4 ”is called“ TEMPL1 ”. It is shown that it is defined in an existing service template.

  The step management table 68 is a table used for managing each step constituting each existing service template. Here, “step” refers to a component of the existing service template. For example, when an existing service template is created by combining a plurality of existing service templates, each of these existing service templates becomes one step of the service template. In addition, when these existing service templates are created by combining a plurality of parts (configuration acquisition parts, user confirmation parts, configuration change parts, etc.), each of these parts corresponds to one step of the existing service template. Become.

  As shown in FIG. 9, the step management table 68 includes a number column 68A, a step ID column 68B, a parent template column 68C, and a step component column 68D. In the step management table 68 of FIG. 9, one record (row) corresponds to one step.

  In the number column 68A, the number (serial number) assigned to the record in the step management table 68 is stored, and in the step ID column 68B, an identifier unique to the step assigned to the corresponding step ( Step ID) is stored. The parent template column 68C stores the template ID of the existing service template in which the corresponding step is defined, and the step component column 68D stores the template ID or the template ID of another template that is the specific content of the corresponding step. The part ID of the part is stored.

  Therefore, in the example of FIG. 9, the steps “STEP4” to “STEP6” are defined by the existing service template “TEMPL2”, among which the step “STEP4” is composed of parts “PLG2” and “STEP5”. It is shown that the step “PLG1” is composed of a part “PLG1”, and the step “STEP6” is composed of a part “PLG3”.

  In FIG. 9, the steps “STEP1” to “STEP3” are defined by the service template “TEMPL1”, and among these steps, “STEP1” and “STEP2” are both configured from the existing service template “TEMPL2”. In addition, it is shown that the step “STEP3” is composed of an existing service template “TEMPL3” (see the upper part of FIG. 3).

  The execution flow management table 69 is a table used for managing the execution order of each step in each existing service template. As shown in FIG. 10, a number column 69A, an execution flow ID column 69B, and a parent template column 69C. , From column 69D and To column 69E. One record in the execution flow management table 69 of FIG. 10 represents a processing flow (execution flow) between two consecutive steps in the existing service template.

  The number column 69A stores a number (serial number) assigned to the record in the execution flow management table 69. The execution flow ID column 69B stores an identifier (execution flow ID) unique to the execution flow assigned to the corresponding execution flow, and the parent template column 69C stores the existing flow in which the execution flow is defined. Stores the template ID of the service template.

  Further, the From column 69D stores the step ID of the step executed before in the corresponding execution flow, and the To column 69E stores the step ID of the step executed after the step in the execution flow. .

  Therefore, in the example of FIG. 10, for example, an existing service template “TEMP1” defines execution flows “EF1” and “EF2”, and the execution flow “EF1” follows the step “STEP1”. It shows the flow of processing to execute the step "STEP2", and the execution flow "EF2" shows the flow of processing to execute the step "STEP3" following the step "STEP2" .

  By referring to the execution flow management table 69 and the step management table 68 described above with reference to FIG. 9, the components constituting the existing service template and the arrangement of these components in the existing service template can be recognized. An icon 45 as shown in FIG. 4 that represents an outline of the processing flow in the template can be generated. Accordingly, the step management table 68 and the execution flow management table 69 are referred to when the icon 45 related to the flow editor field 42 of the service template creation screen 40 is displayed.

  In the data flow management table 70, in each service template, data flow between properties such as which property output data at which step becomes input data at which property at which step (hereinafter referred to as data flow). As shown in FIG. 11, the table includes a number field 70A, a data flow ID field 70B, a parent template field 70C, a From field 70D, and a To field 70E. In the data flow management table 70 of FIG. 11, one record (row) corresponds to one data flow.

  In the number column 70A, the number (serial number) assigned to the record in the data flow management table 70 is stored. The data flow ID column 70B stores an identifier (data flow ID) unique to the data flow assigned to the corresponding data flow, and the parent template column 70C stores the existing data flow in which the data flow is defined. Stores the template ID of the service template.

  Further, the From column 70D is composed of a parent step column 70DA and a property column 70DB. The parent step column 70DA stores a step ID of a step (parent step) that is a data transmission source in the corresponding data flow. The property column 70DB stores the property ID of the property of the data transmitted from the parent step. In FIG. 11, the notation “SELF” stored in the parent step column 70DA of the From column 70D indicates that the property stored in the property column 70DB is a property defined in the parent template in which the data flow is defined. Indicates that

  Similarly, the To column 70E includes a parent step column 70EA and a property column 70EB, and the parent step column 70EA stores a step ID of a step (parent step) as a data transmission destination in the corresponding data flow. In the property column 70EB, the property ID of the property that is the data transmission destination of the parent step is stored.

  Therefore, in the example of FIG. 11, the data flow “DF1” is defined by the existing service template “TEMPL1”, and the data of the input property “PROP1” of the existing service template (“SELF”) is It is shown that it is given as input property data “PROP5” in the step “STEP1” of the existing service template.

  By referring to the data flow management table 70 and the property management table 67 described above with reference to FIG. 8, the data flow between the components in each existing service template or a new one created by combining the existing service templates is created. The flow of data between existing service templates in the service template can be recognized.

  Therefore, the data flow management table 70 and the property management table 67 execute the created service template when displaying the property setting value of the designated step in the property display field 43 of the service template creation screen 40. In this case, it is referred to when the server management computer 9, the storage management computer 10 and / or the network management computer 11 are instructed with respect to the data input source and the data output destination for each component.

  The property GUI setting management table 71 is a table used for managing definition information on a property GUI screen (see, for example, FIG. 5) used by a user to specify a property value when executing a service template. 12, a number column 71A, a property GUI definition ID column 71B, a property column 71C, a GUI type column 71D, and a management resource column 71E are configured. In the property GUI setting management table 71 in FIG. 12, one record (row) corresponds to one setting item (for example, “host”, “storage”, “pool”, or “capacity” in FIG. 5) on the property GUI screen. .

  The number column 71A stores a number (serial number) assigned to the record in the property GUI setting management table 71. The property GUI definition ID column 71B stores a unique identifier (property GUI definition ID) for the setting item assigned to the corresponding setting item, and the property column 71C is set by the corresponding setting item. Property ID of the property to be stored.

  In the GUI type column 71D, a type for acquiring information related to the corresponding property (hereinafter referred to as GUI type) is stored. For example, the GUI type of the property is an external resource such as the server management computer 9 (FIG. 1), the storage management computer 10 (FIG. 1), or the network management computer 11 (FIG. 1) using the property GUI screen 50 or the like. In the case of a type that is selected from the information acquired from, information “external resource reference” is stored, and the GUI type of the property is used by the user using the property GUI screen 50 or the like such as the capacity of the logical volume. If the type is defined, the information “direct input” is stored. Further, the management resource column 71E stores the resource type of the management resource that is the target of the corresponding setting item.

  Accordingly, in the example of FIG. 12, the setting item to which the property GUI definition ID “P-GUI1” is assigned corresponds to the property “PROP22”, and the GUI type for acquiring information from the outside (“reference to external resource”) It is indicated that the target management resource is “Host (server device 6 or virtual machine)”.

  The property GUI setting management table 71 also sets the data input source and data output destination for each component to the server management computer 9, the storage management computer 10, and / or the network management computer 11 when the created service template is executed. Referenced when giving instructions.

  The inter-management resource dependency management table 72 is a table used for managing the dependency relationship between the management resources inquired to the user by the management server computer 4 using the dependency inquiry screen 90 described later with reference to FIG. As shown in FIG. 13, the inter-management resource dependency management table 72 includes a number column 72A, a management resource dependency ID column 72B, a dependency source management resource column 72C, a dependency destination management resource column 72D, a user determination number column 72E, Yes ”is configured to include an answer count column 72F and an accuracy column 72G. In the inter-management resource dependency management table 72 shown in FIG. 13, one record (row) corresponds to a dependency relationship between one management resource.

  The number column 72A stores the number (serial number) assigned to the record in the inter-management resource dependency management table 72. The management resource dependency ID column 72B stores an identifier (management resource dependency ID) unique to the dependency relationship given to the dependency relationship between the corresponding management resources.

  The resource name of the management resource that becomes the dependency source in the corresponding dependency relationship is stored in the dependency source management resource column 72C, and the resource of the management resource that becomes the dependency destination in the corresponding dependency relationship is stored in the dependency destination management resource column 72D. The name is stored.

  Further, the user determination count column 72E shows the dependency relationship between the management resource whose resource name is stored in the dependency source management resource column 72C and the management resource whose resource name is stored in the dependency destination management resource column 72D. The number of times the user is inquired using the inquiry screen 90 (FIG. 28) (hereinafter referred to as the user determination number) is stored.

  In the “dependence” answer count column 72F, the number of times that the user has answered that there is a dependency between these two management resources in response to such a query (hereinafter referred to as “dependency” answer count). Stored.

  Further, the accuracy column 72G indicates the accuracy of the dependency between the management resource whose resource name is stored in the dependency source management resource column 72C and the management resource whose resource name is stored in the dependency destination management resource column 72D. Stored. Note that this accuracy is a percentage of the number of “depends on” responses to the number of user determinations.

  Accordingly, in the example of FIG. 13, the dependency relationship between the management resource (pool) “Pool” and the management resource (logical volume) “Volume” to which the management resource dependency ID “DEP1” is assigned has been described so far. It is shown that the number of times of user determination is “100”, the number of “depending” answers is “80”, and the accuracy calculated based on these is “80%”.

  This inter-management resource dependency management table 72 inquires the user of the dependency relationship between the management resource whose resource name is stored in the dependency source management resource column 72C and the management resource whose resource name is stored in the dependency destination management resource column 72D. When displaying the dependency inquiry screen 90 on the display device 24 (FIG. 1), as a reference when the user determines the dependency relationship between these two management resources, the number of user determinations so far and the number of “dependence” answers It is referred to when displaying the accuracy (see FIG. 28).

(2-2) Various processes related to the component rearrangement function Next, the processing executed in the management server computer 4 of the present embodiment in relation to the component rearrangement function of the present embodiment (hereinafter referred to as the component rearrangement function). The specific processing content of the replacement processing will be described with reference to FIGS. In the following description, the processing subject of the component rearrangement process will be described as one of “programs”. However, in practice, the CPU 20 (FIG. 1) executes the process based on the “program”. Needless to say.

  In the following, it is assumed that a new service template to be subjected to such component rearrangement processing is as shown in FIG. The service template 80 creates a new first logical volume having a designated capacity in the designated first storage device 7 (FIG. 1), and designates the host (here) for the first logical volume. Then, after allocating the virtual machine), this information is set in the datastore (Datastore), and the second logical volume for remote copy (duplication) of the created first logical volume is designated as the second logical volume. This defines a series of processes that are created in the storage device 7 and the first and second logical volumes are set as copy pairs.

  Here, a step (existing service template) called “volume creation (p)” in the service template 80 is a flow of processing for creating a first logical volume having a designated capacity in the designated first storage device 7. It is defined and consists of a configuration acquisition part “G1”, a user confirmation part “U1”, and a configuration change part “E1”. In “G1”, the information of each pool in the first storage device 7 that is the creation destination of the first logical volume is acquired from the storage management computer 10 (FIG. 1) to create the first logical volume. The process of selecting the optimal pool is defined. In “E1”, a process for giving an instruction to the storage management computer 10 to create a first logical volume having a specified capacity on the pool selected in “G1” is defined.

  In addition, the step (existing service template) called “add host” makes the designated virtual machine to the first storage device 7 as a host that uses the first logical volume created in the step “volume creation (p)”. It defines the flow of processing to be registered, and includes a configuration acquisition component “G2”, a user confirmation component “U2”, and a configuration change component “E2”. “G2” defines a process of acquiring the network address of the server device 6 in which the virtual machine is created from the network management computer 11 (FIG. 1). In “E2”, a process for giving an instruction to the storage management computer 10 to register the network address in the first storage device 7 is defined.

  Further, the step “allocation of host” (existing service template) defines the flow of processing for setting a path from the virtual machine to the first storage device 7, and includes a configuration acquisition component “G3”, “ It consists of a user confirmation part “U3” and a configuration change part “E3”. In “G3”, processing for obtaining zoning information of a network (not shown) connecting the virtual machine and the first storage device 7 from the network management computer 11 and selecting the optimum zoning for creating such a path is performed. Is defined. In “E3”, a process for giving an instruction to the network management computer 11 to create a path from the virtual machine to the first storage device 7 in the zoning selected in “G3” is defined.

  The step of “Datastore setting” (existing service template) includes detailed parameters (for example, the capacity of the first logical volume) for creating the datastore (Datastore) from the user input value, and server management for managing the virtual machine. The flow of processing to be set in the computer 9 (FIG. 1) is defined, and includes a part “X1”, a user confirmation part “U4”, and a configuration change part “E4”. In “X1”, a process for determining detailed parameters for creating a data store from a user input value is defined. In “E4”, a process for instructing the server management computer 9 to set the detailed parameter determined in “X1” in the corresponding virtual machine is defined.

  Further, the step (existing service template) “volume creation (s)” defines the same processing as the step “volume creation (p)”. The configuration acquisition component “G4” and “U5” are defined. It consists of a user confirmation part and a configuration change part called “E5”. In “G4”, the optimum pool for creating the second logical volume by acquiring the information of each pool in the second storage device 7 where the second logical volume is created from the storage management computer 10 is obtained. The process of selecting is defined. In “E5”, a process for giving an instruction to the storage management computer 10 to create a second logical volume having a specified capacity on the pool selected in “G4” is defined.

  In addition, the step of “copy pair setting” (existing service template) includes the first logical volume created in the step “volume creation (p)” and the second logical volume created in the step “volume creation (s)”. It defines the flow of processing for setting a volume to a copy pair, and consists of a configuration acquisition component “X2”, a user confirmation component “U6”, and a configuration change component “E6”. In “X2”, processing for determining detailed parameters for creating such a copy pair from a user input value is defined. In “E6”, the first and second storage apparatuses 7 are instructed to the storage management computer 10 to set the first and second logical volumes to the copy pair according to the detailed parameters determined in “X2”. The processing to be given is defined.

  FIG. 27 shows the data dependency relationship between the components constituting the service template 80. Here, the “data dependency relationship between components” is a relationship in which there is a data path that traces the relationship from a certain component A and reaches the component B behind it. For example, when there is a part B having an output property of a part A as an input property, or when an input property of a part B is affected by an output property of a part A ahead of the part A, the part A and the part It can be said that there is a “data dependency” between B.

  As is clear from FIG. 27, in each existing template, the user confirmation parts (“U1” to “U6”) are parts (“G1” to “G4”, “X1”, “ X2 ") is displayed and the user's confirmation is requested, so there is a" data dependency "between the user confirmation part and the configuration acquisition part immediately before that. In addition, the configuration change parts ("E1" to "E6") change the configuration based on the user confirmation result by the user confirmation parts ("U1" to "U6") immediately before the configuration change parts. And there is also a “data dependency” between the user confirmation part immediately before that.

  Further, in the “host allocation” step, in order to set the path from the first storage device 7 that created the first logical volume in the “volume creation (p)” step to the server device 6, “volume creation (p There is also a “data dependency” between the configuration change component (“E1”) at the step “)” and the configuration acquisition component (“G3”) at the step “host allocation”.

  Further, in the “copy pair setting” step, a copy pair between the first logical volume created in the “volume creation (p)” step and the second logical volume created in the “volume creation (s)” step. In the step “copy pair setting”, the component “X2” in the step “volume creation (p)” and the component setting step (“E1”) in the step “volume creation (s)” There is a “data dependency” with both configuration setting parts (“E5”).

(2-2-1) Component Rearrangement Processing FIG. 14 shows that the new service template 80 described above with reference to FIG. 26A is created by the user in the flow editor field 42 of the service template creation screen 40 described above with reference to FIG. Then, the specific processing content of the component rearrangement processing executed when the confirmation step aggregation button 49 (FIG. 4) provided in the upper right of the service template creation screen 40 is clicked is shown.

  In practice, when the confirmation step aggregation button 49 is clicked in such a state, the service template reconfiguration unit 61 (FIG. 1) is activated. First, the service template created at that time (hereinafter referred to as the target service template). Call) 80, each configuration change part ("E1" to "E6") included in the target service template 80 is shifted as far as possible to the rear of the target service template 80 (shifted to the right in FIG. 26A). A service template reconfiguration process is executed (S1).

  Subsequently, the service template reconfiguration unit 61 performs U component aggregation processing for aggregating user confirmation components (“U1” to “U6”) that can be aggregated for the target service template 80 subjected to the service template reconfiguration processing. This is executed (S2), and then the component rearrangement process is terminated.

(2-2-1-1) Service Template Reconfiguration Process FIG. 15 is a specific example of the service template reconfiguration process executed by the service template reconfiguration unit 61 in step S1 of the component rearrangement process described above with reference to FIG. Indicates the processing contents.

  When the service template reconfiguration unit 61 proceeds to step S1 of the component rearrangement process, the service template reconfiguration unit 61 starts the service template reconfiguration process illustrated in FIG. 15. First, each configuration change component (E component) included in the target service template 80. The configuration change component aligning process is performed to align the rear of the target service template 80 as far as possible (S10). As a result of this configuration change component grouping process, for example, the arrangement order of the components in the target service template 80 described above with reference to FIG. 26A is as shown in FIG.

  In addition, the service template reconfiguration unit 61 can thereafter make the user confirmation parts (U parts) scattered in the target service template 81 of FIG. 26B obtained by rearranging the parts of the target service template 80. As far as possible, a user confirmation component aligning process is performed in which the components are grouped immediately before the configuration change component behind the target service template 81 (S11). As a result of the user-confirmed component grouping process, the arrangement order of the components in the target service template 81 in FIG. 26B is as shown in FIG. Then, the service template reconfiguration unit 61 ends this service template reconfiguration process and returns to the component rearrangement process of FIG.

(2-2-1-1) Configuration Change Component Misalignment Processing FIG. 16 shows configuration change component misalignment executed by the service template reconfiguration unit 61 in step S10 of the service template reconfiguration processing described above with reference to FIG. Specific processing contents of the processing are shown.

  This configuration change component grouping process results in a configuration change by moving each component component other than the configuration change component in the target service template 80 to the front of the target service template 80 (left side in FIG. 26A). This is a process of shifting parts to the back of the process. By moving each component part other than the configuration change part in this way and not moving the configuration change part, it is ensured that the execution order of the configuration change parts is not changed before and after the target service template 80 is reconfigured. The

  In practice, when the service template reconfiguration unit 61 proceeds to step S10 of the service template reconfiguration process, the service template reconfiguration unit 61 starts the configuration change component grouping process shown in FIG. Among them, one unprocessed part located in front of the target service template 80 is selected (S20).

  Subsequently, the service template reconfiguration unit 61 determines whether or not the part selected in step S20 (hereinafter referred to as “selected part”) is a configuration change part (E part). The determination is made with reference to the definition information of the target service template 80 created in the field 42 (hereinafter referred to as target service template definition information) (S21).

  In practice, the service template reconfiguration unit 61 internally holds the target service template definition information. This target service template definition information is stored in the service template management table 65 (FIG. 1) by the service template creation unit 60 (FIG. 1) in the process in which the user creates the target service template 80 in the flow editor field 42 of the service template creation screen 40. All the information related to the target service template 80, such as existing service templates and parts constituting the target service template 80, their connection relation and arrangement order, and setting values of these properties, collected from each management table. .

  In step S21, the service template reconfiguration unit 61 refers to the target service template definition information and determines whether the selected component is a configuration change component. If the service template reconfiguration unit 61 obtains a positive result in this determination, it proceeds to step S23.

  On the other hand, if the service template reconfiguration unit 61 obtains a negative result in the determination at step S21, the service template reconfiguration unit 61 executes component movement processing for moving the selected component as far as possible in front of the target service template 80 (S22). Thereafter, the service template reconfiguration unit 61 determines whether or not the processing of step S20 to step S22 has been executed for all the parts constituting the target service template 80 (S23).

  If the service template reconfiguration unit 61 obtains this determination negative result, it returns to step S20, and then repeats the processing of step S20 to step S23 while sequentially switching the component selected in step S20 to another component not yet processed.

  Then, when the service template reconfiguration unit 61 eventually obtains a positive result in step S23 by completing the processing of step S20 to step S23 for all the parts constituting the target service template 80, this configuration change part grouping process To return to the service template reconfiguration process (FIG. 15).

(2-2-1-1-2) Component Movement Processing FIG. 17 is a specific example of the component movement processing executed by the service template reconfiguration unit 61 in step S22 of the configuration change component alignment processing described above with reference to FIG. Indicates the processing contents.

  When the service template reconfiguration unit 61 proceeds to step S22 of the configuration change component grouping process, the service template reconfiguration unit 61 starts the component movement process shown in FIG. 17, and first refers to the target service template definition information described above, and sets the target service template It is determined whether or not any part (hereinafter referred to as the immediately preceding part) exists immediately before the selected part in 80 (immediately to the left of the selected part in FIG. 26A) (S30). If the service template reconfiguration unit 61 obtains a negative result in this determination, it ends this component movement processing and returns to the configuration change component alignment processing (FIG. 16).

  In contrast, when the service template reconfiguration unit 61 obtains a positive result in the determination in step S30, the service template reconfiguration unit 61 refers to the target service template definition information and determines whether or not the immediately preceding component is a branched component (FIG. 26). In (A), it is determined whether or not the immediately preceding part is connected to a plurality of rear parts by arrows (S31). If the service template reconfiguration unit 61 obtains an affirmative result in this determination, it ends this component movement processing and returns to the configuration change component alignment processing (FIG. 16).

  On the other hand, if the service template reconfiguration unit 61 obtains a negative result in the determination at step S31, it determines whether there is a data dependency between the selected component and the immediately preceding component. Is executed (S32).

  After that, the service template reconfiguration unit 61 determines whether or not it is determined that there is a data dependency between the selected component and the immediately preceding component by the inter-component data dependency determination processing in step S32 (S33). If the service template reconfiguration unit 61 obtains an affirmative result in this determination, it ends this component movement processing and returns to the configuration change component alignment processing (FIG. 16).

  On the other hand, if the service template reconfiguration unit 61 obtains a negative result in the determination at step S33, the order of the selected component and the immediately preceding component is changed (S34). Further, the service template reconfiguration unit 61 returns to step S30, and thereafter repeats the processing of step S30 to step S34.

  Then, the service template reconfiguration unit 61 obtains a negative result in step S30 by moving the selected part to the front of the process until there is no more immediately preceding part, or obtains a positive result in step S31 or step S33. The movement process is terminated and the process returns to the configuration change grouping process (FIG. 16).

(2-2-1-1-1) Inter-component data dependency determination processing FIG. 18 illustrates inter-component data dependency determination executed by the service template reconfiguration unit 61 in step S32 of the component movement processing described above with reference to FIG. Specific processing contents of the processing are shown.

  When the service template reconfiguration unit 61 proceeds to step S32 of the component movement process, the service template reconfiguration unit 61 starts the inter-component data dependency determination process shown in FIG. 18, and first refers to the target service template definition information described above to select the selected component. Is determined whether data depends on the immediately preceding part (S40).

  Here, “the selected component is data-dependent on the immediately preceding component” means that the selected component has input the output data of the immediately preceding component. For example, the relationship between parts connected by arrows in FIG. 27 corresponds to this. Therefore, in step S40, the service template reconfiguration unit 61 refers to the output property of the immediately preceding component and the input property of the selected component in the target service template definition information described above, and the output data of the immediately preceding component is the selected component. It is determined whether or not the input data is.

  When the service template reconfiguration unit 61 obtains a positive result in this determination, it determines that the selected component is data-dependent on the immediately preceding component (S43), and thereafter ends the inter-component data dependency determination processing. Then, the process returns to the parts movement process (FIG. 17).

  On the other hand, when the service template reconfiguration unit 61 obtains a negative result in the determination at step S40, the service template reconfiguration unit 61 calls the inter-management resource dependency estimation unit 62 (FIG. 1), and selects the management resource that is the target of the selected component, The management resource dependency determination process for determining whether or not there is a dependency relationship with the management resource to be managed is executed (S41).

  Here, “the dependency between the management resource related to the selected part and the management resource related to the immediately preceding part” means that the management resource that is the target of the selected part is the previous part as described above with reference to FIG. Refers to the relationship included in the related management resource. For example, in the example of FIG. 27, the relationship between “E1” and “G4” corresponds to this. Such a relationship occurs when the selected part is a configuration acquisition part and the immediately preceding part is a configuration change part.

  Therefore, the inter-management resource dependency estimation unit 62 called by the service template reconfiguration unit 61 first determines in step S41 whether the selected component is a configuration acquisition component and the immediately preceding component is a configuration change component. Then, the inter-management resource dependency estimation unit 62 determines whether or not the management resource targeted by the selected part is included in the related management resource of the immediately preceding part when the selected part and the immediately preceding part are such a combination. By estimating from the target service template definition information, it is determined whether or not there is a dependency relationship between the management resource related to the immediately preceding component and the management resource related to the selected component.

  As described above, as the method for estimating whether or not the management resource targeted by the selected part is included in the related management resource of the immediately preceding part, the input property data of the immediately preceding part (configuration changed part) is other If the output data of the part is inherited (pattern 1), the management resource that is the target of the configuration acquisition part (G part) immediately before the part immediately before that part is estimated as the related management resource of the configuration change part. To do. Further, when the input property data of the immediately preceding component is input by the user (pattern 2), the related management resource of the immediately preceding component is estimated based on the target service template definition information.

  The service template reconfiguration unit 61 then obtains a determination result that there is a dependency between the management resource of the selected component and the management resource of the immediately preceding component by the dependency determination processing between management resources in step S41. (S42: YES), it is determined that there is a data dependency between the selected component and the immediately preceding component (S43). Thereafter, the inter-component data dependency determination processing is terminated and the component movement processing (FIG. 17). Return to.

  On the other hand, the service template reconfiguration unit 61 obtains a processing result indicating that there is no dependency between the management resource of the selected component and the management resource of the immediately preceding component by the dependency determination processing between management resources in step S41. If it is determined (S42: NO), it is determined that there is no data dependency between the selected component and the immediately preceding component (S44). Thereafter, the inter-component data dependency determination processing is terminated and the component movement processing is performed. Returning to FIG.

(2-2-1-1-4) Management Resource Dependency Determination Processing FIG. 19 shows a management resource dependency estimation unit 62 (FIG. 1) in step S41 of the inter-component data dependency determination processing described above with reference to FIG. The specific processing contents of the dependency determination processing between management resources executed by the above are shown.

  When called by the service template reconfiguration unit 61 in step S41 of the inter-component data dependency determination process, the inter-management resource dependency estimation unit 62 starts the inter-management resource dependency determination process shown in FIG. Referring to the target service template definition information, it is determined whether or not the selected component is a configuration acquisition component (G component) (S50).

  Then, if a negative result is obtained in this determination, the inter-management-resource dependency estimation unit 62 determines that there is no dependency between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component (S58). ) After notifying the service template reconfiguration unit 61 of the determination result, the inter-management resource dependency determination process is terminated.

  On the other hand, if the inter-management resource dependency estimation unit 62 obtains an affirmative result in the determination in step S50, it refers to the target service template definition information and determines whether the immediately preceding component is a configuration change component (E component). Is determined (S51).

  If a negative result is obtained in this determination, the inter-management-resource dependency estimation unit 62 determines that there is no dependency between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component (S58). ) After notifying the determination result to the service template reconfiguration unit, the inter-management resource dependency determining process is terminated.

  On the other hand, if the inter-management resource dependency estimation unit 62 obtains a positive result in the determination of step S51, the management resource targeted by the selected component (G component) with reference to the target service template definition information, It is determined whether or not the management resource targeted by the immediately preceding component (E component) is the same (S52).

  Then, when the management resource dependency estimation unit 62 obtains a positive result in this determination, it determines that there is a dependency between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component (S59). ) After notifying the service template reconfiguration unit 61 of the determination result, the inter-management resource dependency determination process is terminated.

  On the other hand, if the inter-management resource dependency estimation unit 62 obtains a negative result in the determination at step S52, it executes related management resource estimation processing for estimating the related management lease of the immediately preceding part (S53).

  Subsequently, the inter-management resource dependency estimation unit 62 determines whether or not the management resource targeted by the selected component is included in the management resources specified in step S53 (select among the several management resources specified in step S53). It is determined whether there is a management resource targeted by the component (S54).

  If the result of this determination is negative, the inter-management resource dependency estimation unit 62 determines that there is no dependency between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component (S58). ) After notifying the service template reconfiguration unit 61 of the determination result, the inter-management resource dependency determination process is terminated.

  On the other hand, if the inter-management-resource dependency estimation unit 62 obtains a positive result in the determination in step S54, the inter-management-resource dependency presentation unit 63 (FIG. 1) is called, A dependency inquiry screen 90 as shown in FIG. 28 is displayed on the display device 24 (shown in FIG. 28) to inquire the user about the dependency relationship with the management resource targeted by the component (more precisely, whether the selected component can be rearranged with the immediately preceding component). An instruction is given to the inter-management resource dependency presentation unit 63 so as to be displayed in FIG. 1) (S55).

  The dependency relation inquiry screen 90 includes a service template configuration display field 91, a target resource detail display field 92, an actual result display field 93, a rearrangement execution button 94 and a rearrangement suppression button 95.

  In the service template configuration display field 91, the icons 91B representing the components constituting the target service template 80 are processed in the order of the processing of the target service template 80 arranged in the order reflecting the rearrangement of the components performed in the processing so far. A schematic diagram 91A schematically showing the flow (execution flow) is displayed. In this schematic diagram 91A, adjacent icons 91B are connected by arrows representing the flow of processing. In this schematic diagram 91A, the icon 91B corresponding to the selected part and the icon 91B corresponding to the immediately preceding part are highlighted with a predetermined color, or the icons 91B are highlighted with a light predetermined color. The

  In the target resource detail display field 92, the processing type, the management resource to be processed, and the identifier of the configuration acquisition component immediately before in the schematic diagram 91A displayed in the service template configuration display field 91 for the selected component and the previous component. Detailed information such as the type of management resource targeted by the immediately previous configuration acquisition component is displayed.

  Further, in the result display field 93, the number of times the user has been inquired about the dependency relationship between the management resource that is the target of the selected part and the management resource that is the target of the immediately preceding part (the above-mentioned user determination number is shown in FIG. 13). , “The number of times of user determination”), the number of times that the user replied “dependence” (the above-mentioned “there is a dependency” reply count, “dependence” in FIG. 13), “Dependency” is displayed as the accuracy (“dependence determination result” in FIG. 13), which is calculated from the number of responses, and that there is a dependency relationship between the two management resources.

  Thus, referring to the information displayed on the dependency inquiry screen 90, the user determines whether there is a dependency between the management resource targeted for the selected component and the management resource targeted for the immediately preceding component. Judging.

  When the user determines that there is no dependency between the two management resources and the selected part and the previous part may be rearranged, the user clicks the rearrangement execution button 94, and these two management resources. If it is determined that it is better to suppress the rearrangement of the selected part and the immediately preceding part, the rearrangement suppression button 95 is clicked.

  When the rearrangement execution button 94 or the rearrangement suppression button 95 is clicked, the inter-management resource dependency estimation unit 62 updates the inter-management resource dependency management table 72 (FIG. 13) accordingly (S56).

  For example, if the data dependency relationship between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component is not registered in the inter-management resource dependency management table 72, the inter-management resource dependency estimation unit 62 newly registers the data dependency relationship between these two management resources in the inter-management resource dependency management table 72.

  More specifically, the inter-management resource dependency estimation unit 62 secures one unused row in the inter-management resource dependency management table 72, and then assigns the management resource dependency ID assigned to the data dependency relationship to that row. Are stored in the management resource dependency ID column 72B, the management resource type targeted by the immediately preceding component is stored in the dependency source management resource column 72C, and the management resource type targeted by the selected component is stored in the dependency destination management resource column 72D. To do. Further, the inter-management resource dependency estimation unit 62 stores “1” in the user determination number column 72E of the row, and “1” when the user replies that there is a data dependency, there is no data dependency. When the answer is made, “0” is stored in the “dependence” answer count column 72F. Further, the inter-management resource dependency estimation unit 62 stores the accuracy calculated from the user confirmation count and the “dependence” response count in the accuracy column 72G.

  In addition, the inter-management resource dependency estimation unit 62 is configured such that the data dependency relationship between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component is already registered in the inter-management resource dependency management table 72. Update the record corresponding to the data dependency.

  More specifically, the inter-management resource dependency estimation unit 62 increments the numerical value stored in the user determination number column 72E of the record by “1” and stores it in the “dependence” answer count column 72F of the record. If the user responds that there is a data dependency relationship (when the sort execution button 94 is clicked), the value is “1”, and if the user responds that there is no data dependency relationship (inhibition of sorting) When the button 95 is clicked), it is increased by “0”. Further, the inter-management resource dependency estimation unit 62 sets the user confirmation count stored in the user determination count column 72E updated in this way and the “dependence” response count stored in the “dependence” response count column 72F. Based on this, the accuracy of the data dependency between these management resources is calculated, and the calculation result is stored in the accuracy column 72G.

  Subsequently, the inter-management resource dependency estimation unit 62 determines that the response from the user to the inquiry using the dependency inquiry screen 90 is between the management resource targeted by the selected component and the management resource targeted by the immediately preceding component. It is determined whether or not there is a dependency relationship (that is, whether or not the rearrangement execution button 94 on the dependency relationship inquiry screen 90 has been clicked) (S57).

  Then, if the inter-management resource dependency estimation unit 62 obtains a negative result in this determination, it determines that there is no dependency between the management resource targeted for the selected component and the management resource targeted for the immediately preceding component ( S58) After the determination result is notified to the service template reconfiguration unit 61, the inter-management resource dependency determination process is terminated.

  On the other hand, if the inter-management resource dependency estimation unit 62 obtains an affirmative result in step S57, there is a dependency between the management resource targeted for the selected component and the management resource targeted for the immediately preceding component. After making a determination (S59) and notifying the determination result to the service template reconfiguration unit 61, the inter-management resource dependency determination process is terminated.

(2-2-1-1-5) Related Management Resource Estimation Process FIG. 20 shows related management resources executed by the management resource dependence estimation unit 62 in step S53 of the dependence judgment process between management resources described above with reference to FIG. Specific processing contents of the estimation processing are shown.

  When the process advances to step S53 of the inter-management resource dependency determination process, the inter-management resource dependence estimation unit 62 starts the inter-management resource dependency determination process shown in FIG. One input property is selected (S60).

  Subsequently, the inter-management resource dependency estimation unit 62 determines that the data input source of the input property selected in step S60 (hereinafter referred to as “selected input property”) is a component other than the configuration acquisition component and the configuration change component (that is, the user confirmation component). Or other parts) is determined (S61).

  If the inter-management resource dependency estimation unit 62 obtains an affirmative result in this determination, by executing the related management resource estimation process shown in FIG. 20 for the data input source component of the selected input property, the data input source component Related management resources are estimated (S62).

  Then, the inter-management resource dependency estimation unit 62 estimates (determines) each related management resource estimated in step S61 as a related management resource related to the selected input property of the immediately preceding part (S63), and then proceeds to step S71. .

  On the other hand, if a negative result is obtained in step S61, the inter-management resource dependency estimation unit 62 determines whether the data input source of the selected input property is a configuration acquisition component (G component) (S64). ). When the inter-management-resource dependency estimation unit 62 obtains a positive result in this determination, it estimates (determines) the management source that is the target of the configuration acquisition component as the related management resource of the immediately preceding component (S65), and then performs step S71. Proceed to

  Further, if the inter-management resource dependency estimation unit 62 obtains a negative result in the determination at step S64, it determines whether or not the data input source of the selected input property is a configuration change component (E component) (S66). If the inter-management resource dependency estimation unit 62 obtains a positive result in this determination, it determines that there is no related management resource related to the selected input property in the immediately preceding component (S69), and then proceeds to step S71.

  On the other hand, obtaining a negative result in the determination in step S66 means that the input source of the selected input property data is the user (that is, the user sets the selected input property using the property GUI screen 50 or the like in FIG. 5). means. Thus, at this time, the inter-management resource dependency estimation unit 62 acquires the definition information of the selected input property from the property GUI setting management table 71 (S67).

  Subsequently, the inter-management resource dependency estimation unit 62, for example, based on the acquired content of the selected input property, for example, the server management computer 9 (FIG. 1), the storage management computer 10 (FIG. 1), or the network management computer 11 (FIG. 1). It is determined whether or not it includes processing for acquiring information related to management resources from an external device (S68).

  Then, if the inter-management resource dependency estimation unit 62 obtains a negative result in this determination, it determines that there is no related management resource related to the selected input property in the immediately preceding part (S69), and then proceeds to step S71. If the inter-management resource dependency estimation unit 62 obtains a positive result in the determination at step S68, the management resource for the selected input property is determined in the property GUI setting management table 71 based on the content of the selected input property acquired at step S67. If defined, the management resource is estimated (determined) as a related management resource related to the selected input property in the immediately preceding part (S70), and the process proceeds to step S71.

  Further, when the process proceeds to step S71, the inter-management resource dependency estimation unit 62 determines whether or not the processes after step S61 have been executed for all the input properties of the immediately preceding part (S71). Then, if the inter-management resource dependency estimation unit 62 obtains a negative result in this determination, the process returns to step S60. After that, the input property selected in step S60 is sequentially switched to another input property that has not been processed. Repeat the process.

  Then, if the management resource dependency estimation unit 62 eventually obtains an affirmative result in step S71 by completing the processing after step S61 for all the input properties of the immediately preceding part, it ends the related management resource estimation processing. Returning to the inter-management resource dependency determination process (FIG. 19).

(2-2-1-2) User Confirmation Component Cleaving Process On the other hand, FIG. 21 shows a user confirmation component misalignment process executed by the service template reconstruction unit 61 in step S11 of the service template reconstruction process described above with reference to FIG. Specific processing contents of the processing are shown. In accordance with the processing procedure shown in FIG. 21, the service template reconfiguring unit 61 uses as many user confirmation parts (U parts) scattered in the target service template 81 that the parts have been moved as shown in FIG. It is put together in the state put together just before the rear configuration change part.

  In the present embodiment, each user is required on the condition that the user confirmation component does not straddle the configuration change component in order to “align the user confirmation component as much as possible immediately before the configuration change component”. It is assumed that the confirmation component is shifted to the rear of the target service template as much as possible (to the right of FIG. 26A).

  In practice, when the service template reconfiguration unit 61 proceeds to step S11 of the service template reconfiguration process, the service template reconfiguration unit 61 starts the user confirmation component alignment process shown in FIG. 21, and first, the configuration change described above with reference to FIGS. One unprocessed component that is a rear component of the target service template 81 (FIG. 26B) after the component grouping process is selected (S80).

  Subsequently, the service template reconfiguration unit 61 determines whether or not the component selected in step S80 is a user confirmation component (S81). If the service template reconfiguration unit 61 obtains a negative result in this determination, it proceeds to step S86.

  On the other hand, if the service template reconfiguration unit 61 obtains a positive result in the determination at step S81, the service template reconfiguration unit 61 immediately after the part selected at step S80 (one of the parts selected at step S80 in FIG. 26B). It is determined whether or not there is a right part (hereinafter referred to as a right part) (S82). If the service template reconfiguration unit 61 obtains a negative result in this determination, it proceeds to step S86.

  On the other hand, when the service template reconfiguration unit 61 obtains a positive result in the determination in step S82, it immediately determines whether the component is a configuration change component (E component) (S83). If the service template reconfiguration unit 61 obtains a positive result in this determination, it proceeds to step S86.

  In contrast, when the service template reconfiguration unit 61 obtains a negative result in the determination in step S83, the service template reconfiguration unit 61 determines whether the immediately following component is data-dependent on the component selected in step S80 (here, the user confirmation component). (S84). Specifically, the service template reconfiguration unit 61 refers to the target service template definition information described above, and determines whether or not the component immediately after the output data of any component selected in step S80 is input. If the service template reconfiguration unit 61 obtains a positive result in this determination, it proceeds to step S86.

  On the other hand, if the service template reconfiguration unit 61 obtains a negative result in the determination at step S84, the service template reconfiguration unit 61 switches the order of the part (user confirmation part) selected at step S80 in the target service template 81 and the immediately following part ( S85). Then, the service template reconfiguration unit 61 returns to step S82, and thereafter repeats the processing of step S82 to step S85 until a negative result is obtained in step S82 or a positive result is obtained in step S83 or step S84.

  At this time, if the execution flow is branched behind the part selected in step S80 of the target service template 81, the service template reconfiguration unit 61 selects any one of them and performs steps S82 to S82. The process of step S85 is repeated. Even in this way, since the user confirmation parts between the branches are collected by the parallel user confirmation part aggregation process described later with reference to FIG. 24, there is no problem if the system follows a specific path for each branch.

  Thereafter, when the service template reconfiguration unit 61 obtains a negative result in step S82 for the part selected in step S80 or obtains a positive result in step S83 or step S84, the service template reconfiguration unit 61 performs a step for all parts of the target service template 81. It is determined whether or not the processing after S81 has been executed (S86).

  If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S80, and thereafter, in step S81, the part selected in step S80 is sequentially switched to another unprocessed part. Steps S81 and after are repeated until

  Then, when the service template reconfiguration unit 61 eventually obtains a positive result in step S81 by completing the processes in and after step S81 for all the parts of the target service template 81, the service confirmation reconfiguration unit 61 ends the user confirmation part grouping process. Returning to the service template reconfiguration process (FIG. 15).

(2-2-2) User Confirmation Component Aggregation Processing FIG. 22 shows specific processing contents of the user confirmation component aggregation processing executed by the service template reconfiguration unit 61 in step S2 of the component rearrangement processing described above with reference to FIG. Indicates. The service template reconfiguration unit 61 collects user confirmation parts that can be aggregated with respect to the target service template 82 in which the parts are rearranged as shown in FIG. 26C by the service template reconfiguration process described above with reference to FIGS. (U parts) are aggregated as much as possible according to the processing procedure shown in FIG.

  In practice, when the service template reconfiguration unit 61 proceeds to step S2 of the component rearrangement process, the service template reconfiguration unit 61 starts the user confirmation component aggregation process shown in FIG. 22, and first selects all the user confirmation components adjacent to each other. Next, the adjacent user confirmation component aggregation process to be aggregated is executed (S90). As shown in FIG. 29A, for example, the user confirmation parts “U1”, “U2”, “U4”, and “U5” in the target service template of FIG. Are grouped into one user confirmation part “UA” (hereinafter referred to as an aggregate user confirmation part).

  Subsequently, the service template reconfiguration unit 61 executes parallel user confirmation component aggregation processing for collecting user confirmation components included in each of the branched processing (each processing executed in parallel) in FIG. (S91). By this parallel user confirmation component aggregation processing, the user confirmation component “U3” and the user confirmation component “U6” included in each of the processes after branching at “E1” in the target service template 83 in FIG. As shown in FIG. 29B, they are collected into one aggregated user confirmation part “UB”.

  Next, the service template reconstruction unit 61 disassembles each aggregated user confirmation part obtained by aggregating the user confirmation parts in Step S90 and Step S91 into user confirmation parts for each management domain as shown in FIG. (S92).

  Note that the “management domain” refers to a categorization type for managing these resources in an environment (such as a large-scale data center operating environment) that collectively manages a large amount of various resources. For example, in the case of “management resource type”, “storage device”, “server device”, “network”, “virtual machine (VM)”, and the like are listed as types of “management domain”. In the case of “site”, a geographical location is listed as a type of “management domain”.

  In addition, since the user confirmation parts collected in step S90 and step S91 are decomposed for each management domain in step S92, it is expected that an administrator is set for each management domain. This is because the management domain managed by the client can be confirmed in parallel.

  For example, in the example of FIGS. 29B and 29C, the aggregated user confirmation component “UA” is a component “U-A1” (aggregated user confirmation component) and a component “U-A2” ( The user confirmation part (UB) is divided and the aggregated user confirmation part “UB” is disassembled into a part (U-B1) (user confirmation part) and a part (U-B2) (user confirmation part) . Then, the service template reconstruction unit 61 thereafter ends this user confirmation component aggregation processing.

(2-2-2-1) Adjacent User Confirmation Component Aggregation Processing FIG. 23 shows the adjacent user confirmation component aggregation processing executed by the service template reconfiguration unit 61 in step S90 of the user confirmation component aggregation processing described above with reference to FIG. Specific processing contents are shown.

  When the process proceeds to step S90 of the user confirmation component aggregation process, the service template reconstruction unit 61 starts the adjacent user confirmation component aggregation process shown in FIG. 23. First, the service template reconstruction process described above with reference to FIGS. For example, with respect to the target service template 82 in FIG. 26C in which the parts have been rearranged, all locations where two or more user confirmation parts are adjacent are specified on the target service template 82 (S100).

  This processing is performed by, for example, sequentially checking the processing type of each part by referring to the target service template definition information while tracing the parts in order from the top of the target service template 82 in FIG. This can be done by specifying each location where parts whose processing type is “user confirmation” in 82 appear in succession (hereinafter referred to as “adjacent user confirmation component collection location”).

  Subsequently, the service template reconfiguration unit 61 selects one adjacent user confirmation component collection location from the adjacent user confirmation component collection locations identified in step S100 (S101), and positions the selected adjacent user confirmation component collection location. A new user confirmation part (hereinafter referred to as an aggregated user confirmation part) in which all the user confirmation parts are collected is created (S102).

  Next, the service template reconfiguration unit 61 removes all the user confirmation parts located at the adjacent user confirmation part collection location selected in step S101 from the target service template 82, and replaces them with the aggregate user confirmation parts created in step S102. (S103).

  Thereafter, the service template reconfiguration unit 61 determines whether or not the processing of Step S101 to Step S102 has been executed for all the adjacent user confirmation part collection locations specified in Step S100 (S104).

  If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S101, and thereafter, the adjacent user confirmation part collection location selected in step S101 is sequentially changed to another unprocessed adjacent user confirmation component collection location. While switching, the processing from step S101 to step S104 is repeated.

  When the service template reconfiguring unit 61 finally obtains a positive result in step S104 by completing the processing of step S101 to step S103 for all the adjacent user confirmation part assembly locations specified in step S100, The component aggregation process is terminated, and the process returns to the user confirmation component aggregation process (FIG. 22).

(2-2-2-2) Parallel User Confirmation Component Aggregation Processing On the other hand, FIG. 24 illustrates parallel user confirmation component aggregation executed by the service template reconfiguration unit 61 in step S91 of the user confirmation component aggregation processing described above with reference to FIG. Specific processing contents of the processing are shown.

  When the process proceeds to step S91 of the user confirmation component aggregation process, the service template reconfiguration unit 61 starts the parallel user confirmation component aggregation process shown in FIG. For the target service template 84 in which the user confirmation parts are aggregated as in FIG. 29A, the flow related only to the user confirmation parts with reference to the above-described target service template definition information (hereinafter referred to as the user confirmation part flow). Is extracted (S110).

  Subsequently, the service template reconfiguration unit 61 refers to the target service template definition information for each user confirmation component flow extracted in step S110, and includes the user included in the user confirmation component flow from the top of the target service template 84. The number of branches until the confirmation component is reached is counted, and the number of branches is set as the “depth” of the user confirmation component flow, and the user confirmation component flow existing in the target service template 84 of FIG. (Not including the aggregated user confirmation parts) is classified for each user confirmation part flow of the same “depth” (S111).

  Next, the service template reconstruction unit 61 selects one “depth” that has not been processed from the “depth” classified in step S111 (S112), and each user classified into the selected “depth”. An aggregated user confirmation part is created by aggregating each user confirmation part corresponding to the confirmation part flow (S113).

  Next, the service template reconstruction unit 61 removes all the user confirmation parts corresponding to the user confirmation part flows classified as “depth” selected in step S112 from the target service template 84, and created them in step S113. Replacement with the aggregated user confirmation part (S114).

  Thereafter, the service template reconfiguration unit 61 determines whether or not the processing of step S113 and step S114 has been completed for all “depths” obtained in the classification of step S111 (S115).

  If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S112, and then, while sequentially switching the “depth” selected in step S112 to another “depth” that has not been processed, The process from S112 to S115 is repeated.

  When the service template reconfiguring unit 61 finally obtains a positive result in step S115 by completing the processing of step S113 and step S114 for all the “depths” obtained by the classification in step S111, the parallel user The confirmation component aggregation process is terminated, and the process returns to the user confirmation component aggregation process (FIG. 22).

(2-2-2-3) Aggregated User Confirmation Component Division Processing FIG. 25 shows the aggregation user confirmation component division processing executed by the service template reconfiguration unit 61 in step S92 of the user confirmation component aggregation processing described above with reference to FIG. Specific processing contents are shown.

  When the process proceeds to step S92 of the user confirmation part aggregation process, the service template reconfiguration unit 61 starts the aggregation user confirmation part division process shown in FIG. 25, and first refers to the target service template definition information described above, and the user One unprocessed user confirmation part is selected from the parts constituting the target service template 80 (FIG. 26A) before rearranging the created parts (S120).

  Subsequently, the service template reconfiguration unit 61 determines the management domain of the user management component selected in step S120 (hereinafter referred to as the selected user confirmation component) (S121). Specifically, for example, when a management resource type is used as the management domain, the service template reconfiguration unit 61 acquires the resource type targeted by the latest configuration change component on which the selected user confirmation component depends on data from the target service template definition information. Then, the management domain corresponding to the acquired resource type is determined as the management domain of the selected user confirmation part.

  Next, the service template reconfiguration unit 61 determines whether or not the management domain has been determined for all the user confirmation components constituting the target service template 80 before rearranging the components (S122).

  If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S120, and then sequentially switches the user confirmation part to be selected in step S120 to another unprocessed user confirmation part, step S120 to step S120. The process of S122 is repeated.

  Then, when the service template reconfiguration unit 61 finishes determining the management domain for all the user confirmation components constituting the target service template 80 before rearranging the components, the service template reconfiguration unit 61 obtains a positive result in step S122. One unprocessed component is selected from the components constituting the target service template 85 (FIG. 29B) obtained as a result of the parallel user confirmation component aggregation processing (S123).

  Subsequently, the service template reconfiguration unit 61 determines whether or not the component selected in step S123 is an aggregated user confirmation component (“U-A”, “U-B”) (S124). If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S123, and thereafter repeats the processing of step S123 and step S124.

  Then, when the service template reconfiguration unit 61 eventually selects an aggregated user confirmation part in step S123 to obtain a positive result in the determination in step S124, all of the aggregated user confirmation parts that constitute the aggregated user confirmation part based on the target service template definition information The user confirmation parts are identified, and these user confirmation parts are classified for each management domain based on the management domains determined in step S121 of the identified user confirmation parts (S125).

  Subsequently, the service template reconfiguration unit 61 selects one management domain from the management domains classified in step S125 (S126). Then, the service template reconfiguration unit refers to the target service template definition information, and the management domain determined in step S121 among the user confirmation parts constituting the aggregate user confirmation part selected in step S126 is determined in step S126. All the user confirmation parts that are the selected management domain are extracted, and a new aggregated user confirmation part in which these are aggregated is generated (S127).

  Next, the service template reconfiguration unit 61 determines whether or not the processing in step S127 has been executed for all the management domains classified in step S125 (S128). If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S126, and thereafter repeats the processing of step S126 to step S128.

  When the service template reconfiguration unit 61 obtains an affirmative result in step S128 by completing the process of step S127 for all the management domains classified in step S125, the component selected in step S123 (here, the aggregate user confirmation) (Component) is replaced with the aggregated user confirmation component for each management domain generated in step S127 (S129).

  Subsequently, the service template reconfiguration unit 61 determines whether or not the processing after step S124 has been executed for all the parts constituting the target service template 85 (FIG. 29B) (S130). If the service template reconfiguration unit 61 obtains a negative result in this determination, it returns to step S123, and then sequentially switches the parts selected in step S123 to other unprocessed parts, and then proceeds to steps S123 to S130. Repeat the process.

  Then, when the service template reconfiguration unit 61 eventually obtains the configuration result in step S130 by completing the processes in and after step S124 for all the parts constituting the target service template 85 (FIG. 29B), The aggregated user confirmation part dividing process is terminated.

  As described above, the target service template shown in FIG. 29B is converted into the target service template 86 shown in FIG.

  For example, before replacing the component selected in step S123 (aggregated user confirmation component) with the aggregated user management component for each management domain in step S129, for example, the target service template after replacement as shown in FIG. 30 or FIG. Confirmation screens 100 and 110 displaying schematic diagrams 101 and 111 representing the arrangement of parts are displayed, and after confirmation by the user, the part (aggregated user confirmation part) selected in step S123 is an aggregated user for each management domain. It may be replaced with a management component.

  Here, FIG. 30 is a configuration example of the confirmation screen 100 when disassembling the collective user confirmation part (“UA” in FIG. 29B) in which adjacent user confirmation parts are collected, and an OK button 102 and a cancel button. 103. In the confirmation screen 100, if the confirmation button 102 is clicked, the replacement in step S123 is executed, and if the cancel button 103 is clicked, the replacement in step S123 may be stopped.

  FIG. 31 is a configuration example of the confirmation screen 110 when disassembling the collective user confirmation part (“UB” in FIG. 29B) in which user confirmation parts arranged in parallel are disassembled, and an OK button 112 and a cancel button 113 are Prepare. In the confirmation screen 110, the replacement in step S123 is executed when the confirmation button 112 is clicked, and the replacement in step S123 is stopped when the cancel button 113 is clicked.

(3) Effect of the present embodiment As described above, in the computer system 1 of the present embodiment, the management server computer 4 separates each user confirmation component included in the target service template 80 in front of the target service template 80. The parts of the target service template 80 are rearranged so that the configuration change parts included in the target service template 80 are rearranged behind the target service template 80.

  At this time, regarding the rearrangement of the configuration change component and the configuration acquisition component immediately after the configuration change component, the management server computer 4 determines whether the management resource that is the target of the configuration acquisition component is based on the definition information of the target service template. This is performed only when the configuration change component is not the same as the target management resource and is not a management resource that can be affected by the configuration change component.

  Therefore, according to the management server computer 4, execution of the target service template 80 can be performed while preventing an unexpected error due to the rearrangement of parts of the target service template 80 from occurring when the target service template 80 is executed. It is possible to effectively avoid occasional rollback of configuration changes and frequent confirmation work by the user. In this way, according to the present management server computer 4, the creation and execution of a service template can be facilitated, and thus the operation / maintenance work of the computer system 1 can be made more efficient.

(4) Other Embodiments In the above-described embodiments, the case where the present invention is applied to the computer system 1 configured as shown in FIG. 1 has been described. However, the present invention is not limited to this. In addition, the present invention can be widely applied to computer systems having various configurations.

  In the above-described embodiment, when the user is inquired about whether the configuration change part and the configuration acquisition part can be rearranged, the user's response to the inquiry about whether the configuration change part and the configuration acquisition part can be rearranged. Although the case where the determination result is displayed in the result display field 93 of the dependency inquiry screen 90 described above with reference to FIG. 28 has been described, the present invention is not limited to this, and the determination result is presented to the user by voice or the like. It may be.

  The present invention can be widely applied to computer systems having various configurations.

DESCRIPTION OF SYMBOLS 1 ... Computer system, 2 ... IT system, 3 ... Management computer group, 4 ... Management server computer, 6 ... Server apparatus, 7 ... Storage apparatus, 8 ... Network apparatus, 9 ... Server management computer DESCRIPTION OF SYMBOLS 10 ... Storage management computer, 11 ... Network management computer, 20 ... CPU, 24 ... Display apparatus, 26 ... Operation automation software, 30, 31, 32, 47, 80-86 ... Service template, 40 …… Service template creation screen, 44, 45, 48 …… Icon, 50 …… Property GUI screen, 60 …… Service template creation unit, 61 …… Service template reconstruction unit, 62 …… Management resource dependency estimation unit, 63 …… Management resource interdependence presentation unit, 64 …… Service template execution unit, 65 …… Service template Management table 66... Component management table 67. Property management table 68... Step management table 69... Execution flow management table 70 70 Data flow management table 71 71 Property GUI setting management table 72 ... Management resource dependency management table, 90... Dependency inquiry screen, 100, 110.

Claims (14)

A service template that supports creation of a second service template that is created by sequentially arranging a plurality of first service templates that define processing contents for a target management resource in accordance with the execution order of the first service template. In the creation support device,
The first service template is:
Created by sequentially arranging multiple parts with defined processing contents according to the execution order of the parts,
As the types of the parts,
Including a configuration acquisition component including processing for acquiring configuration information of the target management resource, a user confirmation component including processing for requesting confirmation or a response from the user, and processing for executing configuration change of the target management resource Reconfiguration parts,
A service template creation unit that provides the user with a service template creation base that is an environment for creating at least the second service template;
For the second service template created by the user using the service template creation base, each user confirmation part is shifted forward in the execution order in the second service template, and the configuration change part is A service template reconfiguration unit that rearranges the parts constituting the second service template so as to be shifted to the rear of the execution order in the second service template,
The service template reconfiguration unit
Regarding the rearrangement of the configuration acquisition component included in the second service template and the configuration change component immediately before the configuration acquisition component, the configuration acquisition component is based on the definition information of the second service template. Is not implemented when the data depends on the immediately preceding configuration change part or the management resource that is the target of the configuration acquisition part is a management resource that can be influenced by the configuration change part. Template creation support device. When the management resource that is the target of the configuration acquisition component is a management resource that can be affected by the configuration change component,
When the management resource that is the target of the configuration acquisition part is the same as the management resource that is the target of the configuration change part immediately before, or the management resource that is the target of the configuration acquisition part is the configuration change The management resource that is not the same as the management resource that is a target of a part, but is included in a management resource that can be influenced as a result of the change of the management resource that is the target of the configuration change part. The service template creation support apparatus according to 1. The service template reconfiguration unit
When the input property data of the configuration change part is inherited from the output data of another part, the management resource targeted by the configuration acquisition part immediately before the configuration change part is the target of the configuration change part. The service template creation support apparatus according to claim 2, wherein the management resource is estimated to be the management resource. The service template reconfiguration unit
When the input property data of the configuration change component is input by a user, the management resource targeted by the configuration change component is estimated based on the input property data of the configuration change component. The service template creation support apparatus according to claim 2. The service template reconfiguration unit
The management resource that is the target of the configuration acquisition component is not the same as the management resource that is the target of the configuration change component, but is eventually affected by the change of the management resource that is the target of the configuration change component. The service template creation support apparatus according to claim 2, wherein, when included in the obtained management resource, the user is inquired about whether or not the configuration change part and the configuration acquisition part can be rearranged. The service template reconfiguration unit
When inquiring to the user whether or not the configuration change part and the configuration acquisition part can be rearranged, present the determination results of the user to the current inquiry about whether or not the configuration change part and the configuration acquisition part can be rearranged. The service template creation support apparatus according to claim 5. The service template reconfiguration unit
The service template creation support apparatus according to claim 1, wherein the user confirmation parts that can be aggregated are aggregated among the user confirmation parts that are shifted to the front of the execution order in the second service template. . A service template that supports creation of a second service template that is created by sequentially arranging a plurality of first service templates that define processing contents for a target management resource in accordance with the execution order of the first service template. In the service template creation support method executed by the creation support device,
The first service template is:
Created by sequentially arranging multiple parts with defined processing contents according to the execution order of the parts,
As the types of the parts,
A configuration acquisition component including a process for acquiring configuration information of the target management resource, a user confirmation component including a process for requesting confirmation or a response from the user, and a process for executing a configuration change of the target management resource With change parts,
A first step of providing a service template creation infrastructure, which is an environment for creating at least the second service template, to the user;
For the second service template created by the user using the service template creation base, each user confirmation part is shifted forward in the execution order in the second service template, and the configuration change part is A second step of rearranging the parts constituting the second service template so as to be shifted to the rear of the execution order in the second service template,
In the second step, the service template creation support device
Regarding the rearrangement of the configuration acquisition component included in the second service template and the configuration change component immediately before the configuration acquisition component, the configuration acquisition component is based on the definition information of the second service template. Is not implemented when the data depends on the immediately preceding configuration change part or the management resource that is the target of the configuration acquisition part is a management resource that can be influenced by the configuration change part. Template creation support method. When the management resource that is the target of the configuration acquisition component is a management resource that can be affected by the configuration change component,
When the management resource that is the target of the configuration acquisition part is the same as the management resource that is the target of the configuration change part immediately before, or the management resource that is the target of the configuration acquisition part is the configuration change The management resource that is not the same as the management resource that is a target of a part, but is included in a management resource that can be influenced as a result of the change of the management resource that is the target of the configuration change part. 8. A service template creation support method according to 8. In the second step, the service template creation support device
When the input property data of the configuration change part is inherited from the output data of another part, the management resource targeted by the configuration acquisition part immediately before the configuration change part is the target of the configuration change part. The service template creation support method according to claim 9, wherein the management resource is estimated. In the second step, the service template creation support device
When the input property data of the configuration change component is input by a user, the management resource targeted by the configuration change component is estimated based on the input property data of the configuration change component. The service template creation support method according to claim 9. In the second step, the service template creation support device
The management resource that is the target of the configuration acquisition component is not the same as the management resource that is the target of the configuration change component, but is eventually affected by the change of the management resource that is the target of the configuration change component. 10. The service template creation support method according to claim 9, further comprising: inquiring the user whether or not the configuration change part and the configuration acquisition part can be rearranged when included in the obtained management resource. The service template creation support device includes:
When inquiring to the user whether or not the configuration change part and the configuration acquisition part can be rearranged, present the determination results of the user to the current inquiry about whether or not the configuration change part and the configuration acquisition part can be rearranged. The service template creation support method according to claim 12. The service template creation support apparatus includes a third step of aggregating the user confirmation parts that can be aggregated among the user confirmation parts that are shifted to the front in the execution order in the second service template. The service template creation support method according to claim 8, wherein the service template creation support method is provided.

Images