JP2021144602A - Setting device, method for setting, and program - Google Patents

Abstract

To efficiently prepare work flow definition information and structure setting information used to operate an application by an application execution device.SOLUTION: The setting device includes: a conversion unit for generating task execution procedure information describing the procedure for executing at least one task necessary to execute to operate the target application by an application execution device by using at least one unit information prepared on the basis of components of the target application and structure setting information of the target application; and an execution unit for executing the at least one task on the basis of the task execution procedure information.SELECTED DRAWING: Figure 2

Description

The present invention relates to a technique for properly operating a developed application in an application execution device.

When installing an application, users generally create software (code) in a development environment, test it in a test environment, and install and configure the software in a production environment (which may also be called a commercial environment). An application that provides services to is realized.

Japanese Unexamined Patent Publication No. 2018-133044

In recent years, cloud-native applications, which are applications developed and built using various cloud services, have become widespread.

In such a cloud-native application, in order to properly operate the developed application in the production environment, it is necessary to set the cloud and the container in addition to installing the software. Therefore, the workflow definition information (work procedure) and the configuration setting information created in order to properly operate the developed application in the production environment become complicated, and it takes a lot of time and effort to create the workflow definition information (work procedure) and the management becomes complicated. It should be noted that such a problem is a problem that can occur not only in cloud native applications.

The present invention has been made in view of the above points, and provides a technique capable of efficiently creating workflow definition information and configuration setting information used for operating an application in an application execution device. With the goal.

According to the disclosed technology, the execution procedure of one or more tasks that need to be executed in order to operate the target application in the application execution device by using one or more unit information created based on the components of the target application. The task execution procedure information that describes the above, the conversion unit that generates the configuration setting information of the target application, and
A setting device including an execution unit that executes one or more tasks based on the task execution procedure information is provided.

According to the disclosed technology, a technology that enables efficient creation of workflow definition information and configuration setting information used for operating an application in an application execution device is provided.

It is an overall block diagram of the system in Embodiment of this invention. It is a functional block diagram of the setting device. It is a figure which shows the hardware configuration example of the apparatus. It is a flowchart for demonstrating operation of a setting apparatus. It is a figure which shows the example of a design pattern. It is a figure which shows the example of the workflow definition information. It is a flowchart for demonstrating operation of a setting apparatus. It is a figure which shows the example of the configuration setting information. It is a figure which shows the example of a design pattern. It is a figure for demonstrating the generation example of workflow definition information. It is a figure for demonstrating the generation example of workflow definition information. It is a figure which shows the generation example of the configuration setting information. It is a figure which shows the generation example of the configuration setting information.

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

In the following description, an application is a set of software for providing a certain service. Software may be referred to as "program" or "code". Further, "parameter" means the name of the parameter, and the value is described as "parameter value". Further, the "workflow" may be referred to as a "pipeline".

(System configuration)
FIG. 1 shows a configuration example of the system according to the embodiment of the present invention. As shown in FIG. 1, the system of the present embodiment has a configuration in which the setting device 100 and the application execution device 200 are connected by a network.

The application execution device 200 corresponds to, for example, a production environment (may be referred to as a commercial environment) on a cloud or a container in which an application is operated. However, this is an example, and the application execution device 200 may be a physical PC or server, or may be a development environment or a test environment.

The setting device 100 may be a physical PC or server, or may be a function realized by a virtual machine or the like on the cloud. The function of the setting device 100 may be included in the application execution device 200.

In the present embodiment, each software constituting the application has already been created, and the purpose is to install each application in the application execution device 200 and make necessary settings so that the application operates properly. It is supposed to be.

In the present embodiment, the setting device 100 uses workflow definition information (pipeline information, task execution procedure information, work procedure, workflow definition, etc.) from a plurality of design patterns (may be one design pattern) created in advance. It automatically generates workflow definition file, etc.) and configuration setting information (may be referred to as configuration setting file, configuration information, configuration file, etc.).

The workflow definition information includes information on one or more tasks to be executed in order to properly operate the application on the application execution device 200.

The configuration setting information indicates the configuration and settings of the application, and is composed of information indicating which software is operated with what setting in the application execution device 200.

Further, in the present embodiment, while the setting device 100 executes the workflow definition information, the configuration setting information is automatically generated, and the configuration setting information is used in the deployment task in the workflow definition information, which is necessary. Software is installed and configured.

(Outline of design pattern)
Each design pattern in the plurality of design patterns is information having a part of workflow definition information and a part of configuration setting information. The design pattern may be referred to as "unit information".

An application consists of a plurality of components. As an example, consider an application that accesses a database and provides a predetermined function to a user by API. The application realizes, for example, database software and its setting, software that provides a predetermined function and its setting, and API. It can be divided into three components: software for doing so and its settings.

In the present embodiment, each of the components divided as described above corresponds to one design pattern, but this is an example, how the application is divided, and in what unit. It is optional to configure the design pattern.

However, in the present embodiment, the design pattern is created so that it can be reused. Also, each design pattern is sized as small as possible for easy management. In other words, the design pattern is constructed by grouping various elements included in the application in the smallest reusable unit. By making the design pattern reusable, workflow definition information and configuration setting information can be generated quickly and efficiently.

Each design pattern has parameters, configuration setting information (required software, setting contents, etc.), and task groups (procedures for operating the components, etc.) for the components of the corresponding application. The task group may be called a pipeline or a workflow. The "task group" may be one task.

(Device configuration)
FIG. 2 shows an example of the functional configuration of the setting device 100. As shown in FIG. 2, the setting device 100 includes an input unit 110, a conversion unit 120, a workflow execution unit 130, and a data storage unit 140. The setting device 100 may be physically (or virtually) composed of one device (server or the like) or may be composed of a plurality of devices. For example, the conversion unit 120 may be realized by a device, and the workflow execution unit 130 may be realized by another device. When the devices are separated in this way, for example, the data storage unit 140 is configured by the storage means (memory or the like) of the device which becomes the conversion unit 120 and the storage means (memory or the like) of the device which becomes the workflow execution unit 130. ..

The input unit 110 inputs a design pattern, parameter values, and the like from the outside, and stores these in the data storage unit 140.

The conversion unit 120 reads a plurality of design patterns from the data storage unit 140 and generates workflow definition information from the plurality of design patterns. Further, the conversion unit 120 generates configuration setting information based on a plurality of design patterns and parameter values when executing the workflow definition information. The conversion unit 120 may be called a compiler.

The data storage unit 140 stores input information from the outside, information generated by the conversion unit 120, and the like. The details of the operations of the conversion unit 120 and the workflow execution unit 130 will be described later.

(Hardware configuration example)
The setting device 100 in the present embodiment can be realized by, for example, causing a computer to execute a program describing the processing contents described in the present embodiment. This "computer" may be a physical machine or a virtual machine on the cloud. When using a virtual machine, the "hardware" described here is virtual hardware.

Further, a program that realizes the processing of the conversion unit 120 and a program that realizes the processing of the workflow execution unit 130 may be provided separately. In this case, the conversion unit 120 can be realized as a stand-alone device by causing a computer to execute a program describing the processing contents of the conversion unit 120 described in the present embodiment. Further, the workflow execution unit 130 can be realized as a stand-alone device by causing a computer to execute a program describing the processing contents of the workflow execution unit 130 described in the present embodiment.

The program of the setting device 100, the program of the conversion unit 120, and the program of the workflow execution unit 130 can all be recorded on a computer-readable recording medium (portable memory, etc.) and stored or distributed. It is possible. It is also possible to provide the above program through a network such as the Internet or e-mail.

FIG. 3 is a diagram showing a hardware configuration example of the computer. The computer of FIG. 3 has a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, and the like, which are connected to each other by a bus BS.

The program that realizes the processing in the computer is provided by, for example, a recording medium 1001 such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed in the auxiliary storage device 1002 from the recording medium 1001 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, and may be downloaded from another computer via the network. The auxiliary storage device 1002 stores the installed program and also stores necessary files, data, and the like.

The memory device 1003 reads and stores the program from the auxiliary storage device 1002 when the program is instructed to start. The CPU 1004 realizes the function related to the setting device 100 (or the conversion unit 120, the workflow execution unit 130) according to the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network. The display device 1006 displays a programmatic GUI (Graphical User Interface) or the like. The input device 1007 is composed of a keyboard, a mouse, buttons, a touch panel, and the like, and is used for inputting various operation instructions.

(Operation example of setting device 100)
Hereinafter, an operation example of the setting device 100 will be described according to the procedure of the flowcharts of FIGS. 4 and 7. First, the generation of workflow definition information will be described with reference to the flowchart of FIG.

<S101>
In S101, a plurality of design patterns are input from the input unit 110.

As a premise of this operation, a plurality of design patterns corresponding to the application (referred to as the target application) to be operated by the application execution device 200 are created. If the design pattern was created in the past and can be used for the target application, it may be reused.

FIG. 5 shows a design pattern 1, a design pattern 2, and a design pattern 3 as examples of a plurality of design patterns. Here, it is assumed that the target application has components 1 to 3, the design pattern 1 corresponds to the component 1, the design pattern 2 corresponds to the component 2, and the design pattern 3 corresponds to the component 3. do.

Each design pattern has a data format as shown in FIG. That is, the design pattern describes a block that describes the parameters required for the relevant component, a block that describes the configuration information required for the relevant component, and a workflow (task group) required for the relevant component. Has a block.

For example, the design pattern 1 requires parameters 1 and 2 for the component 1, and software A in which the parameter 1 is set is required as the configuration of the component 1, and the component 1 is operated. Indicates that it is necessary to execute task 1 and task 2 (using parameter 2). The same applies to design patterns 2 and 3.

The task for operating the component 1 may be deployment, pre-deployment processing, processing for installed or started software, and others. It may be the process of.

Since deployment is a task that is always executed in the present embodiment, it may be automatically generated by the conversion unit 120 and included in the workflow definition information without being included in the design pattern.

As shown in FIG. 5, identification information (name or ID) is added to the configuration information in a predetermined unit. In the example of FIG. 5, the configuration information of the design pattern 1 and the design pattern 2 is named "configuration ABC", and the configuration information of the design pattern 3 is named "configuration DEF".

The unit for giving the identification information is arbitrary, but for example, the name may be given in the unit of the main software constituting the application. Further, in different design patterns, the same identification information is given to the configuration information corresponding to the same target. For example, the database of the design pattern 2 in FIG. 5 is a database used by the software A of the design pattern 1, and since the target is the software A, "configuration ABC" is assigned to both of them.

In the example of FIG. 5, there is one identification information in the block of the configuration information of each design pattern, but this is an example, and a plurality of identification information is attached according to the contents included in the configuration information. There is also.

As will be described later, the conversion unit 120 uses this identification information as a key to perform a process of synthesizing the configuration information in the plurality of design patterns.

Further, as shown in FIG. 5, identification information (name or ID) is also given to the workflow in a predetermined unit. In the example of FIG. 5, the workflow of the design pattern 1 and the design pattern 2 is named "task GHI", and the workflow of the design pattern 3 is named "task JKL".

The unit for giving the identification information is arbitrary, but for example, the name may be given in the unit of the main software constituting the application. Further, in different design patterns, the same identification information is given to workflows corresponding to the same target. For example, task 1 of design pattern 2 in FIG. 5 is a task related to software A of design pattern 1, and since the target is software A, "task GHI" is given.

As will be described later, the conversion unit 120 uses this identification information as a key to perform a process of synthesizing workflows in a plurality of design patterns.

Further, in the design pattern, the dependency between tasks may be described in the workflow block. For example, in the example of FIG. 5, when task 1 must be performed after task 3, it may be described in each design pattern that "task 1 is performed after task 3".

In the example of FIG. 5, there is one identification information in the workflow block of each design pattern, but this is an example, and a plurality of identification informations are attached according to the contents of the workflow included in the workflow. There is also.

FIG. 9 shows an example of a more specific design pattern. Note that, in FIGS. 9 to 13, a format similar to yaml, in which information is hierarchically expressed in the form of keys and values, is used, but this is only an example. The design pattern may be described in any format. Further, FIGS. 9 to 13 do not show the design pattern or the like actually used, but abstract the one actually used.

Also in the example of FIG. 9, as described above, the design pattern has a block of parameters, a block of configuration information, and a block of workflow (pipeline), and in the configuration information and workflow, identification information (ID, name, etc.) is provided. Has been granted.

<S102, S103>
In S102 of FIG. 4, the conversion unit 120 reads out a plurality of design patterns input in S101 from the data storage unit 140, and executes the target application from the plurality of design patterns in order to operate the target application in the application execution device 200. Generate workflow definition information that shows the required tasks and their execution order. In S103, the conversion unit 120 outputs the workflow definition information. Specifically, the following processes (1) to (4) are performed.

(1) The conversion unit 120 scans all the identification information and its contents in the "workflow" block of the plurality of design patterns, and synthesizes the tasks (task group) of the same identification information among the plurality of design patterns. If the identification information is different, the tasks of each identification information are arranged in the execution order according to the dependency between the tasks.

Combining means that if there is the same task among a plurality of design patterns, it is regarded as one task, and if it is a different task, the tasks are arranged in the execution order according to the dependency between the tasks.

Further, when the conversion unit 120 detects that a contradiction has occurred in the processing contents in the synthesis, the conversion unit 120 outputs a conflict error and ends the processing.

For example, suppose that the task 1 in the task group identified by the "task XYZ" in the design pattern X is executed before the task 2, and the task group identified by the "task XYZ" in the design pattern Y is executed. If task 1 is supposed to be executed after task 2, there is a conflict and a conflict error occurs.

(2) The conversion unit 120 may determine the execution order of the tasks according to the dependency information (declaration) described in the design pattern, or the data storage unit 140 may determine the dependency information (software A is started). It may be decided by storing the information (such as performed before the installation of the software B) in advance and referring to the information.

(3) The conversion unit 120 acquires all the parameters required in the plurality of design patterns and describes them in the workflow definition information.

(4) The conversion unit 120 generates a "task for generating configuration setting information", and outputs a workflow definition information that describes the task, a list of tasks obtained by the above processing, and a list of parameters. The output workflow definition information is stored in the data storage unit 140.

An example of the workflow definition information generated from the design patterns 1 to 3 in FIG. 5 is shown in FIG. As shown in FIG. 6, in the workflow definition information, parameters 1 to 4 acquired from design patterns 1 to 3 are described, and each task is described in an order according to an execution order. Note that "deployment" in the example of FIG. 6 is a task of installing and setting software according to the configuration setting information, and in the present embodiment, is a task generated by the conversion unit 120.

FIG. 10 shows an example of three more specific design patterns. These three design patterns correspond to applications that access a database and provide a predetermined function to a user by API. Specifically, the DB pattern is a design pattern for database software and its settings, the Base pattern is a design pattern for software that provides a predetermined function and its settings, and the API pattern is software for realizing API. And the design pattern for its settings.

"Myapp" in Base pattern is software that provides a predetermined function. In the DB pattern, the configuration information (connection destination address, ID, etc.) for myapp to connect to the database is described as the configuration information of the same name "appDeployment" as the name "appDeployment" in the Base pattern.

In the API pattern, information on the port for publishing the base software described in the Base pattern, information on the probe for monitoring the life and death of whether or not the port is functioning, and the like are described.

In the generation of the configuration setting information, the conversion unit 120 scans the frame portion of FIG. 9, and the configuration setting information as shown in FIG. 11 is generated by the procedure described above. In FIG. 11, the “compleConfig” corresponds to the “configuration setting information generation task” in FIG. Further, in FIG. 11, it is shown that the portion surrounded by the frame is the information acquired from the three design patterns.

Next, the process related to the generation of the configuration setting information will be described with reference to the flowchart of FIG. 7. It is assumed that the value of each parameter described in the workflow definition information is stored in the data storage unit 140 by input from the user or the like.

<S201>
The workflow execution unit 130 reads the workflow definition information and the value of the parameter from the data storage unit 140, and starts executing the workflow definition information. Executing the workflow definition information means executing each task described in the workflow definition information in the order described (from the top in the example of FIG. 6).

When the workflow execution unit 130 executes the "configuration setting information generation task" in the workflow definition information, the workflow execution unit 130 instructs the conversion unit 120 (compiler) to generate the configuration setting information.

<S202>
In S202, the conversion unit 120 that has received the instruction to generate the configuration setting information acquires the values of a plurality of design patterns and parameters corresponding to the target application from the data storage unit 140.

<S203, S204>
In S203, the conversion unit 120 generates configuration setting information for operating the target application in the application execution device 200 from a plurality of design patterns and parameter values. In S204, the conversion unit 120 outputs the configuration setting information. Specifically, it is as follows (1) to (2).

(1) The conversion unit 120 scans all the identification information and its contents in the "configuration information" block of the plurality of design patterns, and synthesizes the configuration information of the same identification information among the plurality of design patterns. If the identification information is different, the configuration information of each identification information is arranged.

Combining means that if there is the same configuration information among a plurality of design patterns, it is regarded as one configuration information, and if it is different configuration information, they are arranged.

In addition, when it is detected that a contradiction has occurred in the contents of the configuration information in the composition, the process is terminated as a conflict error.

For example, suppose that the software 1 in the configuration information identified by the "configuration XYZ" in the design pattern X requires parameter 1, and the software 1 in the configuration information identified by the "configuration XYZ" in the design pattern Y requires parameter 2. If so, there is a contradiction and a conflict error occurs.

(2) The conversion unit 120 outputs the configuration setting information having a list of the configuration information. The output configuration setting information is stored in the data storage unit 140.

An example of the configuration setting information generated from the design patterns 1 to 3 in FIG. 5 is shown in FIG. As shown in FIG. 8, the configuration information acquired from each design pattern is described in a form in which the parameter values are embedded.

As a more specific example, FIG. 12 shows the same three design patterns shown in FIG. In FIG. 12, the portion (the portion of the configuration information) scanned by the conversion unit 120 in the generation of the configuration setting information is surrounded by a frame. From these configuration information, the configuration setting information shown in FIG. 13 is generated. The values of the parameters are also shown in FIG. In FIG. 13, it is shown that the portion surrounded by the frame (all in this example) is the information acquired from the three design patterns. FIG. 13 describes that software called myapp is installed, settings are made for myapp to connect to the database, and life-and-death monitoring is set for API port monitoring.

<S205>
In S205 of FIG. 7, the workflow execution unit 130 reads the configuration setting information generated by the conversion unit 120 from the data storage unit 140, and when executing the deployment which is one of the tasks in the workflow definition information, the configuration setting By instructing the application execution device 200 according to the information, software installation, setting, startup, and the like are executed. When the execution of the workflow definition information is completed, the target application is in the state of operating in the application execution device 200.

In the above example, the configuration setting information is generated when the workflow definition information is executed, but this is an example. Before executing the workflow definition information, the configuration setting information may be generated together with the workflow definition information by receiving the input of the parameter values.

(Effects of embodiments, etc.)
As described above, the technique according to the present embodiment can efficiently create the workflow definition information and the configuration setting information used to operate the application in the application execution device.

In addition, instead of managing workflow definition information and configuration setting information separately, we decided to create and manage unit information (design patterns) for each use case and operation model, so a consistent operation model / policy is also possible. Information can be managed with and, and effective life cycle management from application development to operation becomes possible.

In addition, by configuring the design pattern with the smallest reusable unit, it is possible to share unit information about workflow definition information and configuration setting information that were previously created and managed for each project across projects. By standardizing infrastructure design, testing, and operation models, system development can be performed quickly and safely.

When synthesizing multiple design patterns and automatically generating workflow definition and configuration setting files, the design patterns can be safely extended by inspecting the requirements of each design pattern according to the format, and the application can be scaled. It becomes possible to manage the operation model.

In particular, in cloud native applications, function additions / changes are performed in a short cycle (agile), but the technology related to this embodiment can automate the work of function additions / changes, and with the addition of application functions. Since it is possible to flexibly change the work / setting contents, it is possible to safely and scalablely add / change functions in a short cycle.

(Summary of embodiments)
This specification describes at least the setting devices, setting methods, and programs described in the following items.
(Section 1)
Task execution procedure information that describes the execution procedure of one or more tasks that need to be executed in order to operate the target application in the application execution device using one or more unit information created based on the components of the target application. And a conversion unit that generates the configuration setting information of the target application,
A setting device including an execution unit that executes one or more tasks based on the task execution procedure information.
(Section 2)
The setting device according to item 1, wherein each unit information in the one or more unit information has a block of parameters, a block of configuration information, and a block indicating one or more tasks.
(Section 3)
The block of configuration information includes identification information for identifying one or more configuration information.
The setting device according to item 2, wherein the conversion unit synthesizes configuration information having the same identification information among a plurality of unit information in the generation of the configuration setting information.
(Section 4)
The block indicating one or more tasks includes identification information for identifying one or more tasks.
The setting device according to item 2 or 3, wherein the conversion unit synthesizes one or more tasks having the same identification information among a plurality of unit information in the generation of the task execution procedure information.
(Section 5)
The setting device according to any one of items 1 to 4, wherein the conversion unit outputs an error when a conflict occurs between a plurality of unit information.
(Section 6)
The conversion unit generates a task for generating the configuration setting information as one task in the task execution procedure information, and the execution unit executes the task. The setting device according to any one of items 1 to 5 that generates configuration setting information.
(Section 7)
It is a setting method executed by the setting device.
Task execution procedure information that describes the execution procedure of one or more tasks that need to be executed in order to operate the target application in the application execution device using one or more unit information created based on the components of the target application. And the conversion step to generate the configuration setting information of the target application.
A setting method including an execution step for executing one or more tasks based on the task execution procedure information.
(Section 8)
A program for causing a computer to function as each part in the setting device according to any one of items 1 to 6.

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

100 Setting information 110 Input unit 120 Conversion unit 130 Workflow execution unit 140 Data storage unit 200 Application execution environment 1000 Drive device 1001 Recording medium 1002 Auxiliary storage device 1003 Memory device 1004 CPU
1005 Interface device 1006 Display device 1007 Input device

Claims (8)

Task execution procedure information that describes the execution procedure of one or more tasks that need to be executed in order to operate the target application in the application execution device using one or more unit information created based on the components of the target application. And a conversion unit that generates the configuration setting information of the target application,
A setting device including an execution unit that executes one or more tasks based on the task execution procedure information. The setting device according to claim 1, wherein each unit information in the one or more unit information includes a block of parameters, a block of configuration information, and a block indicating one or more tasks. The block of configuration information includes identification information for identifying one or more configuration information.
The setting device according to claim 2, wherein the conversion unit synthesizes configuration information having the same identification information among a plurality of unit information in the generation of the configuration setting information. The block indicating one or more tasks includes identification information for identifying one or more tasks.
The setting device according to claim 2 or 3, wherein the conversion unit synthesizes one or more tasks having the same identification information among a plurality of unit information in the generation of the task execution procedure information. The setting device according to any one of claims 1 to 4, wherein the conversion unit outputs an error when a conflict occurs between a plurality of unit information. The conversion unit generates a task for generating the configuration setting information as one task in the task execution procedure information, and the execution unit executes the task. The setting device according to any one of claims 1 to 5, which generates configuration setting information. It is a setting method executed by the setting device.
Task execution procedure information that describes the execution procedure of one or more tasks that need to be executed in order to operate the target application in the application execution device using one or more unit information created based on the components of the target application. And the conversion step to generate the configuration setting information of the target application.
A setting method including an execution step for executing one or more tasks based on the task execution procedure information. A program for causing a computer to function as each part in the setting device according to any one of claims 1 to 6.

Images