WO2019238136A1

WO2019238136A1 - Workflow modeling method and device and computer-readable storage medium

Info

Publication number: WO2019238136A1
Application number: PCT/CN2019/092336
Authority: WO
Inventors: 赵化冰; 孟照星; 徐代刚
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-06-14
Filing date: 2019-06-21
Publication date: 2019-12-19
Also published as: CN110609675B; CN110609675A

Abstract

Disclosed by the embodiments of the present invention is a workflow modeling method, comprising: parsing an acquired service template so as to obtain each node defined in the service template; generating a directed graph on the basis of the each node, the directed graph being used for indicating a relationship between each node in the service template; generating a high-level workflow template according to the directed graph, the high-level workflow template comprising: a workflow of each node in the service template; and generating a workflow execution script file according to the high-level workflow template, and establishing an association relationship between the workflow execution script file and the service template. Also disclosed by the embodiments of the present invention are a workflow modeling device and a computer-readable storage medium.

Description

Workflow modeling method, device and computer-readable storage medium

This application claims priority from Chinese patent application CN201810616144.8 entitled "A Workflow Modeling Method, Apparatus, and Computer-readable Storage Medium" filed on June 14, 2018, the entire contents of which are incorporated herein by reference. in.

Technical field

The invention relates to the field of Network Function Virtualization (NFV), in particular to a method, device and computer-readable storage medium for modeling workflow.

Background technique

In recent years, the rapid development of cloud computing and virtualization technologies has brought a lot of innovation, and at the same time, it has put a lot of pressure on operators. Operators are looking for new revenue growth points to offset the OTT (Over The Top) business belt. At the same time, in order to reduce the management expenditure of the enterprise OPEX (Operating Expense), through the decoupling of software and hardware and functional abstraction, the network equipment functions no longer depend on dedicated hardware, resources can be fully and flexibly shared, and rapid development of new services and Deploy and quickly deploy services based on actual business requirements such as automatic deployment, elastic scaling, fault isolation, and self-healing. Therefore, network function virtualization is required to solve these problems.

In order to enhance the portability of cloud applications on various cloud infrastructures, the Organization for the Advancement of Structured Information Standards (OASIS) for the Advancement of Structured Information Standards (TOSCA, Topology) and Orchestration Specification for Cloud Applications). TOSCA describes the components that make up the Cloud Application and the topological relationship between them through a service template. The Orchestrator analyzes the service template, applies for computing and network resources on the cloud infrastructure, and performs service processing. Instantiate and upgrade, reduce and expand, terminate and other life cycle management.

TOSCA not only formulated the basic specifications for cloud application orchestration, but also expanded based on this basic specification. With reference to the ETSI, NFV, MANO architecture and standards, it formulated the orchestration specifications in the NFV field. Currently, the TOSCA orchestration specification has been adopted by a number of mainstream operators and telecommunications equipment vendors, and is the mainstream orchestration standard in the NFV field. The workflow in the TOSCA service template is used to deploy, upgrade, and expand the life cycle management processes of NFV network services. It belongs to the important content of the template. When orchestrator performs network service lifecycle management, it needs to execute the lifecycle management workflow corresponding to the service template. TOSCA supports two methods for defining lifecycle management workflow: declarative workflow and imperative workflow.

For the declarative workflow, the definition workflow is not displayed in the service template. The orchestrator determines the order in which each component is created according to the dependencies between the nodes in the TOSCA service template when instantiating the network service. Assuming that the destination node depends on the source node, the orchestrator first creates the destination node instance during execution, and then creates the source node instance. The characteristic of declarative workflow is that the lifecycle management workflow is automatically generated by the orchestrator according to the topology of the service template when deploying the service template. There is no need to explicitly define the workflow file, but it lacks flexibility and cannot expand the workflow. For imperative workflows, since declarative workflows cannot express some complex lifecycle management processes, TOSCA also supports explicit definition workflows, that is, imperative workflows. The imperative workflow is very flexible. Users can define each step in the workflow according to their needs, but it is more tedious. The TOSCA specification includes a simple workflow definition domain specific language (DSL, Domain Specific Language), which can define a simple workflow in a service template, clearly indicating which node and which method is executed in each step.

At present, the two workflow modeling methods in the TOSCA specification have certain limitations, and they face the following problems when applied to NFV service template lifecycle management workflow modeling:

I. Declarative workflows cannot implement complex lifecycle management processes in the NFV field

The intent of the TOSCA declarative workflow is to define a cloud software data model that is completely independent of the orchestrator and can seamlessly switch between orchestrator implementations. However, due to the complexity of the NFV field, it is currently impossible to achieve a model that is completely independent of the orchestrator. For example, the choice of data center location for virtual network functions (VNF, Virtual Network Function), the creation of underlying links across the WAN, and the specific orchestrator Technology implementation is related, so it is necessary to use the imperative workflow to orchestrate the life cycle process of network services.

Second, the syntax of the built-in workflow language has greater limitations

TOSCA's built-in workflow DSL language also has major limitations, which makes it unable to support the orchestration of network service lifecycle management processes in the NFV field. Its problems include, but are not limited to:

1. TOSCA's built-in workflow DSL can only call operations on nodes in the TOSCA service template, but cannot call services outside the template. For example, in the NFV orchestration, a resource selection service for calculating which data center a VNF should be created, and an EMS service for configuring network element data need to be called.

2. TOSCA's built-in workflow DSL does not support workflow nodes that need to interact with users. For example, at a certain step of the workflow, the user is required to input a parameter, such as manually selecting a virtual infrastructure resource manager (VIM, Virtual Infrastructure Manager).

Therefore, it can be seen that both TSOCA's declarative workflow and its built-in imperative workflow have certain limitations, resulting in the existing specification content cannot effectively support the orchestration of network service lifecycle management processes in the NFV field.

Summary of the Invention

In order to solve the existing technical problems, embodiments of the present invention provide a workflow modeling method, device, and computer-readable storage medium, which solves the problem that the TOSCA declarative workflow process is fixed, cannot be extended, and the built-in TOSCA workflow language cannot be used. Limitations such as calling external services.

To achieve the above object, the technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a workflow modeling method, including:

Parse the obtained service template to obtain each node defined in the service template;

Generating a directed graph based on the respective nodes, the directed graph used to represent a relationship between various nodes in the service template;

Generating a high-level workflow template according to the directed graph, where the high-level workflow template includes: a workflow of each node in the service template;

Generate a workflow execution script file according to the high-level workflow template, and establish an association relationship between the workflow execution script file and the service template.

An embodiment of the present invention further provides a workflow modeling device, including:

A parsing unit, configured to parse the obtained service template to obtain each node defined in the service template;

A generating unit, configured to generate a directed graph based on the respective nodes, the directed graph used to represent a relationship between various nodes in the service template; and used to generate a high-level workflow template based on the directed graph The high-level workflow template includes: a workflow of each node in the service template; and is further configured to generate a workflow execution script file according to the high-level workflow template, and establish the workflow execution script file and the service. Association of templates.

An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above tasks. The steps of an itemized workflow modeling method.

Embodiments of the present invention provide a workflow modeling method, device, and computer-readable storage medium, parse the obtained service template, and obtain each node defined in the service template; generate a directed graph based on the each node, The directed graph is used to represent the relationship between nodes in the service template; a high-level workflow template is generated according to the directed graph, and the high-level workflow template includes: the work of each node in the service template A process; generating a workflow execution script file according to the high-level workflow template, and establishing an association relationship between the workflow execution script file and the service template. The workflow modeling method, device and computer-readable storage medium provided by the embodiments of the present invention automatically generate an abstract high-level workflow template according to the topology relationship of each node in the service template, and then generate a specific high-level workflow template based on the high-level workflow template. The workflow execution script file expressed by the workflow execution language finally completes the modeling of the network service life cycle management workflow, while taking into account the convenience of the declarative workflow while introducing the flexibility of the imperative workflow, it can effectively support NFV The modeling of the network service lifecycle management process in the scenario solves the limitations of TOSCA's declarative workflow process, which cannot be extended, and TOSCA's built-in workflow language cannot call external services.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. Similar reference numerals with different letter suffixes may represent different examples of similar components. The drawings generally illustrate various embodiments discussed herein by way of example and not limitation.

FIG. 1 is a first schematic flowchart of a workflow modeling method according to an embodiment of the present invention; FIG.

FIG. 2 is an example diagram of a dependency relationship between core content of a blog application TOSCA service template and various nodes according to an embodiment of the present invention; FIG.

3 is a second schematic flowchart of a workflow modeling method according to an embodiment of the present invention;

4 is a directed graph generated according to a blog application TOSCA service template according to an embodiment of the present invention;

5 is a schematic diagram of a high-level workflow template generated according to a blog application TOSCA service template according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an association between a TOSCA service template and a generated workflow script file according to an embodiment of the present invention; FIG.

7 is a third schematic flowchart of a workflow modeling method according to an embodiment of the present invention;

8 is a schematic diagram of a high-level workflow template for a blog application deployment after adjusting a node execution order according to an embodiment of the present invention;

9 is a fourth schematic flowchart of a workflow modeling method according to an embodiment of the present invention;

10 is a schematic diagram of a high-level workflow template for a blog application deployment after adding a custom node according to an embodiment of the present invention;

11 is a first schematic structural diagram of a workflow modeling device according to an embodiment of the present invention;

FIG. 12 is a second schematic structural diagram of a workflow modeling device according to an embodiment of the present invention; FIG.

FIG. 13 is a third schematic structural diagram of a workflow modeling device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.

An embodiment of the present invention provides a workflow modeling method. As shown in the schematic flow chart shown in FIG. 1, the method may include the following steps:

Step 101: Parse the obtained service template to obtain each node defined in the service template.

Specifically, the execution subject of the workflow modeling method provided by the embodiment of the present invention may be a workflow modeling device, that is, the workflow modeling device obtains a service template, parses the service template, and obtains each node defined in the service template. It can also be understood as obtaining all nodes defined in the service template.

Exemplarily, the obtained service template is a TOSCA service template as an input, and the TOSCA service template as an input is parsed to obtain all nodes defined in the TOSCA service template.

Step 102: Generate a directed graph based on the nodes.

The directed graph is used to represent a relationship between nodes in the service template.

Specifically, the workflow modeling device traverses all the nodes of the obtained service template and analyzes the relationships between the nodes in the service template. The relationships between nodes include, but are not limited to, dependencies (tosca.relationships.DependsOn), and the dependencies include, but are not limited to: connection relationships (tosca.relationships.ConnectsTo), host relationships (tosca.relationships.HostOn), and so on.

Among them, in the service template, the relationship has two endpoints, namely the provider and the demander, so a directional line segment can be generated according to the node relationship. The provider of the relationship is the end point pointed by the line segment, and the demander of the relationship is the The edge points to the starting point. Combining the line segments generated by all the relationships together produces a directed graph that represents the dependencies between all nodes in the service template. An example of a directed graph is shown in Figure 4.

Step 103: Generate a high-level workflow template according to the directed graph.

The high-level workflow template includes a workflow of each node in the service template.

Specifically, a high-level workflow template for life cycle management is generated according to the directed graph, and the high-level workflow template uses a high-level abstract language (information model) that is independent of the specific workflow language to represent the workflow. The information model contains basic elements representing actions, execution sequences, branch judgments, etc. in the workflow, but uses an abstract high-level model, which has nothing to do with the specific workflow language. Each of these action nodes comes from the operations defined by the nodes in the TOSCA service template, such as create, start, stop, delete, etc. Because this high-level workflow template defines an information model that is independent of the specific workflow language, it can be converted to any workflow language as needed.

After the generating a high-level workflow template according to the directed graph, the method further includes:

Obtain business requirements, adjust the high-level workflow template according to the business requirements, and obtain an adjusted high-level workflow template.

Specifically, the business requirements are read, and the execution order of each node in the high-level workflow template is adjusted according to the business requirements, or a new workflow node is added.

Step 104: Generate a workflow execution script file according to the high-level workflow template, and establish an association relationship between the workflow execution script file and the service template.

Specifically, according to the information model of the high-level workflow template, a workflow execution script file expressed in a specific workflow execution language is generated. The script may be a business process model and notation (BPMN, Business Process Model and Notation). Business process execution language (BPEL, Business Process Execution Language), OpenStack Mistral and any workflow execution language. Among them, OpenStack is an open source cloud computing management platform project, and Mistral provides workflow service components for OpenStack.

Associate the TOSCA service template with the generated workflow script file, and generate the association between the service template and the script file. The purpose is that the orchestrator can find and execute the corresponding workflow script according to the association when performing lifecycle management on the cloud service described by the service template. For example, when deploying the cloud service, a deployment workflow corresponding to the cloud service template can be found according to the association relationship.

The method provided by the embodiment of the present invention automatically generates an abstract high-level workflow template according to the topology relationship of each node in the TOSCA service template, which can be extended based on the workflow template, adjust the node order, or add a custom action node, and then according to The high-level workflow template generates a workflow execution script file expressed in a specific workflow execution language, and finally completes the network service lifecycle management workflow modeling, thereby introducing the imperative work while taking the convenience of declarative workflow into consideration. The flexibility of the flow can effectively support the modeling of the network service lifecycle management process in the NFV scenario.

The following uses a TOSCA service template as an input to illustrate three specific implementations of the workflow modeling method provided by the embodiment of the present invention. The service template describes the composition and topology of a blog application. The blog application runs on a web server and uses a MySql database. Both the MySql database and the web server run on the same compute node. The core content of the TOSCA service template and the dependencies between various nodes are shown in Figure 2.

A workflow modeling method provided by an embodiment of the present invention can generate a deployed workflow according to a service template, and the automatically generated template meets deployment requirements without adjustment. As shown in the schematic diagram of the workflow modeling method shown in FIG. 3, the method may include the following steps:

Step 201: Parse the obtained service template to obtain each node defined in the service template.

Specifically, the workflow modeling device parses the TOSCA service template as an input, and obtains all nodes defined in the TOSCA service template. The TOSCA service template is a formatted text file that defines each node included in the cloud application, which can specifically include: server nodes, database system nodes, database instance nodes, application server nodes, and blog application nodes. Specifically, a text processing program can read the formatted text file, parse out all nodes, and save it into a memory data structure.

Step 202: traverse each node to obtain the relationship between each node in the service template; and generate a directed graph according to the relationship between each node in the service template.

Specifically, the workflow modeling device traverses all the nodes of the TOSCA service template, analyzes the relationships between the nodes in the TOSCA service template, and generates a directed graph. The endpoints of the directed graph represent the nodes in the service template. The connections between the nodes are directed. The direction represents the dependencies between the nodes. The nodes at the starting point of the arrows depend on the nodes pointed by the arrows.

In this embodiment, the dependency relationship between nodes includes a connection relationship (ConnectsTo) and a host relationship (HostOn). When a directed graph is generated, the algorithm is a dependency relationship. The source node of the connection relationship depends on the destination node of the connection relationship. The host The source node of the relationship depends on the destination node of the host relationship, and the generated directed graph is shown in Figure 4.

Step 203: Acquire a node in the directed graph according to the execution order of each node, and acquire an operation defined by the node in the service template.

Specifically, the first node in the directed graph is obtained according to the execution order of each node, and the operation defined by the first node in the service template is obtained, where the first node is the one started in the work execution order. node.

Specifically, one node of the directed graph, that is, the first node, is obtained according to the execution order of each node, and operations defined by the node are obtained from the TOSCA service template, such as operations such as creating, starting, stopping, and deleting.

Step 204: Add a workflow node to the preset high-level workflow template according to the type of the preset life cycle management process, and the workflow node represents the operation of the directed graph node.

Specifically, a first workflow node is added to a preset high-level workflow template according to a type of a preset life cycle management process, where the first workflow node is used to indicate an operation defined by the first node.

Specifically, according to the type of the preset life cycle management process, the corresponding operation of the first node is added to the high-level workflow template, that is, the first high-level workflow template is added to indicate the operation defined by the first node. Workflow node.

Here, the process steps in generating the high-level workflow template in step 204 are related to the type of lifecycle management corresponding to the workflow. For example, the deployed workflow template needs to call the creation, startup, configuration operation of the node, and the deleted template needs to be called. Stop and destroy nodes. Since a deployment workflow is created in this embodiment, it is necessary to create, start, and configure node operations corresponding to this node into the high-level workflow template.

Step 205: It is determined whether there are more nodes in the directed graph, and if there are more nodes, step 203 is performed, otherwise step 206 is performed.

Specifically, it is determined whether there are nodes other than the first node in the directed graph. When the directed graph includes nodes other than the first node, step 203 is performed, otherwise step 206 is performed.

Specifically, when the directed graph includes nodes other than the first node, the second node in the directed graph is repeatedly obtained according to the execution order of each node, and the service template is obtained. The operation defined by the second node adds a second workflow node to a preset high-level workflow template according to the type of the preset life cycle management process, until each node in the directed graph is added to the In the preset high-level workflow template, a preset high-level workflow template for each node in the directed graph is added as the high-level workflow template.

The second node is a node that is executed after the first node, and the second workflow node is used to indicate an operation defined by the second node.

Step 206: Convert the high-level workflow template into a preset workflow execution script file, and establish a path association relationship between the service template and the preset workflow execution script file.

Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template, and the resulting high-level workflow template is shown in FIG. 5. Step 206 converts the high-level workflow template into a business process model and notation (BPMN, Business Model and Notation) workflow script file according to the syntax of BPMN and DSL. The workflow script file can be executed by any workflow engine that complies with the BPMN specification.

Specifically, the created BPMN workflow script file is associated with the TOSCA service template. You can point the deployment lifecycle management workflow of the service template in the TOSCA service template to an external file plan / deploy.bpmn. deploy.bpmn is the BPMN workflow script file generated in the previous step. This file is saved in the relative directory plan of the TOSCA service template. The specific association method is shown in Figure 6.

The method provided by the embodiment of the present invention automatically generates an abstract high-level workflow template according to the topology relationship of each node in the TOSCA service template, and then generates a workflow execution script file expressed in a specific workflow execution language according to the high-level workflow template. , Finally complete the network service lifecycle management workflow modeling, thereby taking into account the convenience of the declarative workflow while introducing the flexibility of the imperative workflow, can effectively support the network service lifecycle management process in the NFV scenario Modeling.

A workflow modeling method provided by an embodiment of the present invention can generate a deployed workflow according to the service template, and the workflow node order of the automatically generated template needs to be adjusted. As shown in the flowchart of the workflow modeling method shown in FIG. 7, the method may include the following steps:

Step 301: Parse the obtained service template to obtain each node defined in the service template.

Step 302: traverse each node to obtain the relationship between the nodes in the service template; and generate a directed graph according to the relationship between the nodes in the service template.

Specifically, the workflow modeling device traverses all the nodes in the TOSCA service template, analyzes the relationships between the nodes in the TOSCA service template, and generates a directed graph. The endpoints of the directed graph represent the nodes in the service template. The connections between the nodes are directed. The direction represents the dependencies between the nodes. The nodes at the starting point of the arrows depend on the nodes pointed by the arrows. In this embodiment, the dependency relationship between nodes includes a connection relationship (ConnectsTo) and a host relationship (HostOn). When a directed graph is generated, the algorithm is a dependency relationship. The source node of the connection relationship depends on the destination node of the connection relationship, and the host relationship. The source node depends on the destination node of the host relationship. The generated directed graph is shown in Figure 4.

Step 303: Acquire a node in the directed graph according to the execution order of each node, and acquire an operation defined by the node in the service template.

Specifically, one node of the directed graph, that is, the first node, is taken out according to the execution order of each node, and operations defined by the node are obtained from the TOSCA service template, such as create, start, stop, and delete operations.

Step 304: Add a workflow node to the preset high-level workflow template according to the type of the preset life cycle management process, and the workflow node represents the operation of the directed graph node.

Specifically, according to the type of the preset life cycle management process, the corresponding operation of the first node is added to the high-level workflow template, that is, the first high-level workflow template is added to indicate the operation defined by the first node. As the workflow node is created in this embodiment as a deployment workflow, it is necessary to create, start, and configure node operations corresponding to this node into the high-level workflow template.

Step 305: It is determined whether there are more nodes in the directed graph, and if there are more nodes, step 303 is performed, otherwise step 306 is performed.

Specifically, it is determined whether there are nodes other than the first node in the directed graph. When the directed graph includes nodes other than the first node, step 303 is performed, otherwise step 306 is performed. .

Step 306: Obtain business requirements, adjust the execution order of each node in the high-level workflow template according to the business requirements, and obtain an adjusted high-level workflow template.

Specifically, the business requirements can be obtained according to the actual business needs of the user, and the execution order of each node in the automatically generated high-level workflow template is adjusted. In order to avoid operating system global resource locks (such as the apt and yum tools that require global locks and do not support concurrency), each operation node in the automatically generated default high-level workflow template is executed serially, but if the deployment operation does not involve Global resource locks can be executed concurrently to speed up execution efficiency. In this embodiment, assuming that the operation of each node does not depend on the global resources of the operating system, the deployment process of the database and the web server can be adjusted and executed serially, for example, as shown in FIG. 8.

Step 307: Convert the adjusted high-level workflow template into a preset workflow execution script file, and establish a path association relationship between the service template and the preset workflow execution script file.

Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template. The resulting high-level workflow template is shown in FIG. 8. This step converts the high-level workflow template into a BPEL workflow script file according to the syntax of BPEL DSL. The workflow script file can be executed by any workflow engine that complies with the BPEL specification.

Associate the created BPEL workflow script file to the TOSCA service template. You can point the deployment lifecycle management workflow of the service template in the TOSCA service template to an external file plan / deploy.bpel. deploy.bpel is the BPEL workflow script file generated in the previous step, which is saved in the relative directory plan of the TOSCA service template.

The method provided by the embodiment of the present invention automatically generates an abstract high-level workflow template based on the topology relationship of each node in the TOSCA service template, which can be extended based on the workflow template, adjust the node order, and then generate an application based on the high-level workflow template. The workflow execution script file expressed by the specific workflow execution language finally completes the network service lifecycle management workflow modeling, thereby taking into account the convenience of declarative workflow while introducing the flexibility of imperative workflow, which can be effective To support the modeling of network service lifecycle management processes in NFV scenarios.

An embodiment of the present invention provides a workflow modeling method, and a deployed workflow is generated according to the service template, and a custom workflow node needs to be added. As shown in the schematic diagram of the workflow modeling method shown in FIG. 9, the method may include the following steps:

Step 401: Parse the obtained service template to obtain each node defined in the service template.

Step 402: traverse each node to obtain the relationship between the nodes in the service template; and generate a directed graph according to the relationship between the nodes in the service template.

In this embodiment, the relationship between the nodes includes a connection relationship (ConnectsTo) and a host relationship (HostOn). When a directed graph is generated, the algorithm is a dependency relationship. The source node of the connection relationship depends on the destination node of the connection relationship. The source node depends on the destination node of the host relationship. The generated directed graph is shown in Figure 4.

Step 403: Acquire a node in the directed graph according to the execution order of each node, and acquire the operation defined by the node in the service template.

Specifically, the first node in the directed graph is acquired according to the execution order of each node, and the operation defined by the first node in the service template is acquired. The first node is a node that starts in the work execution sequence.

Specifically, one node of the directed graph, that is, the first node, is taken out according to the execution order of each node, and the operations defined by the node, such as create, start, stop, and delete operations, are obtained from the TOSCA service template.

Step 404: Add a workflow node to the preset high-level workflow template according to the type of the preset life cycle management process, and the workflow node represents the operation of the directed graph node.

Specifically, a first workflow node is added to a preset high-level workflow template according to a type of a preset life cycle management process. The first workflow node is used to indicate an operation defined by the first node.

Specifically, according to the type of the preset life cycle management process, the corresponding operation of the node is added to the high-level workflow template. Since a deployment workflow is created in this embodiment, the node needs to be created and started correspondingly. The configuration node operation is added to the high-level workflow template.

Step 405: It is determined whether there are more nodes in the directed graph, and if there are more nodes, step 403 is performed, otherwise step 406 is performed.

Specifically, it is determined whether there are nodes other than the first node in the directed graph. When the directed graph includes nodes other than the first node, step 403 is performed, otherwise step 406 is performed. .

Step 406: Obtain business requirements, and add at least one workflow node to the high-level workflow template according to the business requirements to obtain an adjusted high-level workflow template.

As an example, the business requirement is to import data from another blog site when deploying the service. Because this part of the logic cannot be expressed in the TOSCA service template, a custom workflow node needs to be added for processing. A workflow node for importing data is added to the high-level workflow template generated in the previous step. A shell script to import data from another blog site into the newly created blog application, as shown in Figure 10.

Step 407: Convert the adjusted high-level workflow template into a preset workflow execution script file, and establish a path association relationship between the service template and the preset workflow execution script file.

Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template, and the resulting high-level workflow template is shown in FIG. 10. In this step, the high-level workflow template is converted into a yaml workflow script file (the Mistral workflow is defined as a yaml format) according to the syntax of the OpenStack Mistral workflow. This workflow script file can be executed by any OpenStack Mistral workflow engine.

Associate the created Mistral workflow script file to the TOSCA service template. You can point the deployment lifecycle management workflow of the service template in the TOSCA service template to an external file plan / deploy.yaml. deploy.yaml is the Mistral workflow script file generated in the previous step, which is saved in the relative directory plan of the TOSCA service template.

The method provided by the embodiment of the present invention automatically generates an abstract high-level workflow template according to the topology relationship of each node in the TOSCA service template, which can be extended based on the workflow template, adding a custom action node, and then according to the high-level workflow template Generate a workflow execution script file expressed in a specific workflow execution language, and finally complete the modeling of the web service lifecycle management workflow, thereby taking into account the convenience of a declarative workflow while introducing the flexibility of an imperative workflow Can effectively support the modeling of network service lifecycle management processes in NFV scenarios.

An embodiment of the present invention further provides a workflow modeling device 50, as shown in FIG. 11, including:

A parsing unit 501, configured to parse the obtained service template to obtain each node defined in the service template;

A generating unit 502 is configured to generate a directed graph based on the respective nodes, and the directed graph is used to represent a relationship between various nodes in the service template; and is further configured to generate a high-level workflow according to the directed graph. A template, the high-level workflow template includes: a workflow of each node in the service template; and is further configured to generate a workflow execution script file according to the high-level workflow template, and establish the workflow execution script file and the Association of service templates.

The generating unit 502 is specifically configured to:

Traverse each node to obtain the relationship between each node in the service template;

Generating the directed graph according to a relationship between each node in the service template.

The generating unit 502 is specifically configured to:

Obtaining the first node in the directed graph according to the execution order of each node, obtaining the operation defined by the first node in the service template, and according to the type of the preset life cycle management process in the preset high-level workflow template Adding a first workflow node, wherein the first node is a node started in the work execution sequence, and the first workflow node is used to indicate an operation defined by the first node;

When the directed graph includes nodes other than the first node, the second node in the directed graph is repeatedly obtained according to the execution order of each node, and the first node in the service template is obtained. Operations defined by two nodes, adding a second workflow node to a preset high-level workflow template according to the type of the preset life cycle management process, until each node in the directed graph is added to the preset high-level In the workflow template, a preset high-level workflow template for each node in the directed graph is added as the high-level workflow template, wherein the second node is a node executed after the first node, and the The second workflow node is used to indicate an operation defined by the second node.

As shown in FIG. 12, the apparatus further includes an adjustment unit 503 configured to obtain a service requirement, adjust the high-level workflow template according to the service requirement, and obtain an adjusted high-level workflow template.

As shown in FIG. 12, the apparatus further includes an adjustment unit 503 configured to adjust an execution order of each node in the high-level workflow template according to a service requirement.

As shown in FIG. 12, the apparatus further includes an adjustment unit 503 configured to add at least one workflow node to the high-level workflow template according to a service requirement.

The generating unit 502 is specifically configured to:

Converting the high-level workflow template or the adjusted high-level workflow template into a preset workflow execution script file, and establishing a path association between the service template and the preset workflow execution script file.

Specifically, for the understanding of the workflow modeling apparatus provided in the embodiment of the present invention, reference may be made to the description of the foregoing embodiment of the workflow modeling method, which is not repeatedly described in this embodiment of the present invention.

The workflow modeling device provided by the embodiment of the present invention automatically generates an abstract high-level workflow template according to the topology relationship of each node in the TOSCA service template, which can be expanded based on the workflow template, adjust the node order, or add custom actions. Node, and then generate a workflow execution script file expressed in a specific workflow execution language according to the high-level workflow template, and finally complete the network service lifecycle management workflow modeling, thereby introducing the convenience of declarative workflow while taking into account The flexibility of the imperative workflow can effectively support the modeling of the network service lifecycle management process in the NFV scenario.

An embodiment of the present invention further provides a workflow modeling device 60. As shown in FIG. 13, the workflow modeling device 60 includes a processor 601 and a memory 602. Among them,

The memory 602 is configured to store a computer program capable of running on the processor;

The processor 601 is configured to execute the steps of the workflow modeling method described above when running the computer program.

It can be understood that the memory 602 may be a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), or an erasable programmable read-only memory (EPROM, Erasable Programmable Read- Only Memory), Electrically Erasable and Programmable Read-Only Memory (EEPROM), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , Compact disc, or read-only compact disc (CD-ROM, Compact Disc-Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory may be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Static Random Access, Memory), Dynamic Random Access DRAM (Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Double Data Rate Rate Synchronous Dynamic Access Random Access Memory, Enhanced Type Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Access Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Access Memory) ). The memory 602 described in the embodiments of the present invention is intended to include, but not limited to, these and any other suitable types of memory.

The method disclosed in the foregoing embodiment of the present invention may be applied to the processor 601, or implemented by the processor 601. The processor 601 may be an integrated circuit chip and has a signal processing capability. More specifically, it has a workflow modeling algorithm built in, that is, it has a workflow modeling capability. In the implementation process, each step of the above method may be completed by using an integrated logic circuit of hardware in the processor 601 or an instruction in the form of software. The above processor 601 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor 601 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium. The storage medium is located in the memory 602. The processor 601 reads information in the memory 602 and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the workflow modeling device may be implemented by one or more application-specific integrated circuits (ASICs, Application Specific Integrated Circuits), DSPs, Programmable Logic Devices (PLDs), and complex programmable logic devices. (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or Other electronic component implementations for performing the aforementioned method.

In an exemplary embodiment, an embodiment of the present invention further provides a storage medium, which may specifically be a computer-readable storage medium, for example, a memory including a computer program, and the computer program may be executed by a processor of a workflow modeling device to Complete the steps described in the previous method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

An embodiment of the present invention provides a computer-readable storage medium. The computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any one of the foregoing. Steps of the workflow modeling method described in item.

Those skilled in the art should understand that the embodiments of the present invention may be provided as a method, a system, or a computer program product. Therefore, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, optical memory, etc.) containing computer-usable program code.

The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, so that the instructions generated by the processor of the computer or other programmable data processing device are used to generate instructions Means for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a specific manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions The device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

The above description is only the preferred embodiments of the present invention, and is not intended to limit the protection scope of the present invention.

Claims

A workflow modeling method, including:

Parse the obtained service template to obtain each node defined in the service template;

Generating a directed graph based on the respective nodes, the directed graph used to represent a relationship between various nodes in the service template;

Generating a high-level workflow template according to the directed graph, where the high-level workflow template includes: a workflow of each node in the service template;

Generate a workflow execution script file according to the high-level workflow template, and establish an association relationship between the workflow execution script file and the service template.
The method according to claim 1, wherein the generating a directed graph based on the respective nodes comprises:

Traverse each node to obtain the relationship between each node in the service template;

Generating the directed graph according to a relationship between each node in the service template.
The method according to claim 1, wherein the generating a high-level workflow template based on the directed graph comprises:

Obtaining the first node in the directed graph according to the execution order of each node, obtaining the operation defined by the first node in the service template, and according to the type of the preset life cycle management process in the preset high-level workflow template Adding a first workflow node, wherein the first node is a node started in the work execution sequence, and the first workflow node is used to indicate an operation defined by the first node;

When the directed graph includes nodes other than the first node, the second node in the directed graph is repeatedly obtained according to the execution order of each node, and the first node in the service template is obtained. Operations defined by two nodes, adding a second workflow node to a preset high-level workflow template according to the type of the preset life cycle management process, until each node in the directed graph is added to the preset high-level In the workflow template, a preset high-level workflow template for each node in the directed graph is added as the high-level workflow template, wherein the second node is a node executed after the first node, and the The second workflow node is used to indicate an operation defined by the second node.
The method according to claim 1, wherein after the generating a high-level workflow template from the directed graph, the method further comprises:

Obtain business requirements, adjust the high-level workflow template according to the business requirements, and obtain an adjusted high-level workflow template.
The method according to claim 4, wherein said adjusting the high-level workflow template according to the business requirements comprises:

Adjust the execution order of each node in the high-level workflow template according to the business requirements.
The method according to claim 4, wherein said adjusting the high-level workflow template according to the business requirements comprises:

Adding at least one workflow node to the high-level workflow template according to the business requirement.
The method according to any one of claims 3 to 6, wherein the generating a workflow execution script file according to the high-level workflow template and establishing an association relationship between the workflow execution script file and the service template includes: :

Converting the high-level workflow template or the adjusted high-level workflow template into a preset workflow execution script file, and establishing a path association between the service template and the preset workflow execution script file.
A workflow modeling device, including:

A parsing unit, configured to parse the obtained service template to obtain each node defined in the service template;

A generating unit, configured to generate a directed graph based on the respective nodes, the directed graph used to represent a relationship between various nodes in the service template; and used to generate a high-level workflow template based on the directed graph The high-level workflow template includes: a workflow of each node in the service template; and is further configured to generate a workflow execution script file according to the high-level workflow template, and establish the workflow execution script file and the service. Association of templates.
The apparatus according to claim 8, wherein the generating unit is specifically configured to:

Obtaining the first node in the directed graph according to the execution order of each node, obtaining the operation defined by the first node in the service template, and according to the type of the preset life cycle management process in the preset high-level workflow template Adding a first workflow node, wherein the first node is a node started in the work execution sequence, and the first workflow node is used to indicate an operation defined by the first node;

When the directed graph includes nodes other than the first node, the second node in the directed graph is repeatedly obtained according to the execution order of each node, and the first node in the service template is obtained. Operations defined by two nodes, adding a second workflow node to a preset high-level workflow template according to the type of the preset life cycle management process, until each node in the directed graph is added to the preset high-level In the workflow template, a preset high-level workflow template for each node in the directed graph is added as the high-level workflow template, wherein the second node is a node executed after the first node, and the The second workflow node is used to indicate an operation defined by the second node.
The apparatus according to claim 8 or 9, wherein the apparatus further comprises an adjustment unit configured to adjust an execution order of each node in the high-level workflow template according to a service requirement.
The apparatus according to claim 8 or 9, wherein the apparatus further comprises an adjustment unit configured to add at least one workflow node to the high-level workflow template according to a business requirement.
A computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs are executable by one or more processors to implement claims 1 to 7 The steps of the workflow modeling method of any one of the preceding.