CN110609675A - Workflow modeling method and device and computer readable storage medium - Google Patents
Workflow modeling method and device and computer readable storage medium Download PDFInfo
- Publication number
- CN110609675A CN110609675A CN201810616144.8A CN201810616144A CN110609675A CN 110609675 A CN110609675 A CN 110609675A CN 201810616144 A CN201810616144 A CN 201810616144A CN 110609675 A CN110609675 A CN 110609675A
- Authority
- CN
- China
- Prior art keywords
- node
- workflow
- template
- service
- directed graph
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
Abstract
The embodiment of the invention discloses a workflow modeling method, which comprises the following steps: analyzing the obtained service template to obtain each node defined in the service template; generating a directed graph based on the nodes, wherein the directed graph is used for representing the relationship among the nodes in the service template; generating a high-level workflow template according to the directed graph, wherein the high-level workflow template comprises: the workflow of each node in the service template; and generating a workflow execution script file according to the high-level workflow template, and establishing the association relationship between the workflow execution script file and the service template. The embodiment of the invention also discloses a workflow modeling device and a computer readable storage medium.
Description
Technical Field
The present invention relates to the field of Network Function Virtualization (NFV), and in particular, to a workflow modeling method, apparatus, and computer-readable storage medium.
Background
In recent years, cloud computing and virtualization technologies have been rapidly developed, so that many innovations are brought, and at The same time, great pressure is brought to operators, operators are faced with finding new revenue growth points to offset The influence caused by ott (over The top) services, and meanwhile, in order to reduce management expenses of enterprises, opex (operating expense), network equipment functions are not dependent on special hardware any more through software and hardware decoupling and function abstraction, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, services such as automatic deployment, elastic expansion, fault isolation and self-healing are rapidly developed based on actual service requirements, and therefore, The problems need to be solved through network function virtualization.
To enhance the portability of Cloud Applications (Cloud Applications) across various Cloud infrastructures, the Organization for Advancement of Structured Information Standards (OASIS) has formulated Cloud Application Topology and Orchestration Specifications (TOSCA). TOSCA describes each component and topological relation among the components forming Cloud Application through a service template (ServiceTemplate), and an Orchestrator (Orchester) analyzes the service template, applies for calculation and network resources on Cloud infrastructure, instantiates and upgrades the service, expands and contracts, terminates and other life cycle management.
The TOSC not only establishes a basic specification of cloud application arrangement, but also expands based on the basic specification, and establishes an arrangement specification in the NFV field by referring to an ETSI NFV MANO architecture and standard. Currently, the TOSCA orchestration specification is adopted by many mainstream operators and telecommunication equipment manufacturers, and is a mainstream orchestration standard in the NFV field. The workflow in the TOSCA service template is used for the life cycle management processes of deployment, upgrade, capacity expansion and the like of the NFV network service, and belongs to important contents in the template. When the orchestrator performs the network service lifecycle management, it needs to execute a lifecycle management workflow corresponding to the service template. The TOSCA supports two life cycle management workflow definition methods: declarative (declarative) workflows and imperative (proactive) workflows.
For declarative workflows, defining workflows are not displayed in the service template, and the orchestrator determines the sequence of creation of each component according to the dependency relationship between each node in the TOSCA service template when instantiating the network service. Assuming that the destination node is dependent on the source node, the orchestrator, when executed, creates the destination node instance first, and then the source node instance. The declarative workflow is characterized in that the lifecycle management workflow is automatically generated by the orchestrator according to the topology of the service template when the service template is deployed, a definition workflow file is not required to be displayed, but the flexibility is lacked, and the workflow cannot be expanded. For imperative workflows, TOSCA also supports display definition workflows, i.e., imperative workflows, since declarative workflows cannot express some of the complex lifecycle management flows. The commanded workflow is characterized by being very flexible, and the user can define each step in the workflow as desired, but it is cumbersome. The TOSCA specification includes a simple workflow definition Domain Specific Language (DSL) that defines simple workflows in the service template, specifying which method of which node is executed in each step.
At present, two workflow modeling methods in TOSC specifications have certain limitations, and the following problems are faced when the two workflow modeling methods are applied to the NFV service template life cycle management workflow modeling:
firstly, the declaration workflow can not realize the complex life cycle management process in the NFV field
The intent of the TOSCA declarative workflow is to define a cloud software data model that is completely orchestrator independent, and that can be seamlessly switched between various orchestrator implementations. However, due to the complexity of the NFV field, at present, it is impossible to implement a model completely independent of an orchestrator, for example, data center position selection of a Virtual Network Function (VNF), creation of a bottom link across a WAN, and the like are all related to implementation of a specific orchestrator technology, and thus a lifecycle process of a Network service needs to be orchestrated by using a command workflow display.
Grammar of built-in workflow language has great limitation
The workflow DSL language built in the TOSCA also has great limitations, which results in that it cannot support network service lifecycle management process orchestration in the NFV domain, and the problems include but are not limited to:
1. the TOSCA built-in workflow DSL can only invoke the operation of a node in the TOSCA service template, but cannot invoke a service outside the template. For example, in the NFV arrangement, a resource selection service for calculating which data center the VNF should create, an EMS service for configuring network element data, and the like need to be invoked.
2. The TOSCA built-in workflow DSL does not support workflow nodes that need to interact with the user. For example, at a certain step of the workflow, the user is required to enter a parameter, such as manually selecting a Virtual Infrastructure Manager (VIM).
Therefore, it can be seen that both the declarative workflow of the TSOCA and the built-in imperative workflow thereof have certain limitations, so that the existing canonical content cannot effectively support the network service lifecycle management flow arrangement in the NFV field.
Disclosure of Invention
In order to solve the existing technical problem, embodiments of the present invention provide a workflow modeling method, a workflow modeling device, and a computer-readable storage medium, which solve the problems of limitations that a TOSCA declarative workflow process is fixed and cannot be extended, and a TOSCA built-in workflow language cannot invoke external services.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
the embodiment of the invention provides a workflow modeling method, which comprises the following steps:
analyzing the obtained service template to obtain each node defined in the service template;
generating a directed graph based on the nodes, wherein the directed graph is used for representing the relationship among the nodes in the service template;
generating a high-level workflow template according to the directed graph, wherein the high-level workflow template comprises: the workflow of each node in the service template;
and generating a workflow execution script file according to the high-level workflow template, and establishing the association relationship between the workflow execution script file and the service template.
Optionally, the generating a directed graph based on the nodes includes:
traversing each node to obtain the relationship among the nodes in the service template;
and generating the directed graph according to the relationship among the nodes in the service template.
Optionally, the generating a high-level workflow template according to the directed graph includes:
acquiring a first node in the directed graph according to the execution sequence of each node, acquiring an operation defined by the first node in the service template, and adding a first workflow node in a preset high-level workflow template according to the type of a preset life cycle management process, wherein the first node is a node started in the work execution sequence, and the first workflow node is used for indicating the operation defined by the first node;
when the directed graph comprises nodes except the first node, repeatedly obtaining a second node in the directed graph according to the execution sequence of each node, obtaining the operation defined by the second node in the service template, and adding a second workflow node in 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 into the preset high-level workflow template, wherein the preset high-level workflow template added to each node in the directed graph is the high-level workflow template, the second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
Optionally, after the generating a high-level workflow template according to the directed graph, the method further includes:
and acquiring a service demand, and adjusting the high-level workflow template according to the service demand to obtain the adjusted high-level workflow template.
Optionally, the adjusting the high-level workflow template according to the service requirement includes:
and adjusting the execution sequence of each node in the high-level workflow template according to the service requirement.
Optionally, the adjusting the high-level workflow template according to the service requirement includes:
and adding at least one workflow node in the high-level workflow template according to the service requirement.
Optionally, 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 include:
and 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 relation for searching the preset workflow execution script file by the service template.
An embodiment of the present invention further provides a workflow modeling apparatus, including:
the analysis unit is used for analyzing the acquired service template to acquire each node defined in the service template;
a generating unit, configured to generate a directed graph based on the nodes, where the directed graph is used to represent a relationship between the nodes in the service template; and the high-level workflow template is also used for generating a high-level workflow template according to the directed graph, and the high-level workflow template comprises: the workflow of each node in the service template; and the workflow execution script file is generated according to the high-level workflow template, and the association relation between the workflow execution script file and the service template is established.
Optionally, the generating unit is specifically configured to:
acquiring a first node in the directed graph according to the execution sequence of each node, acquiring an operation defined by the first node in the service template, and adding a first workflow node in a preset high-level workflow template according to the type of a preset life cycle management process, wherein the first node is a node started in the work execution sequence, and the first workflow node is used for indicating the operation defined by the first node;
when the directed graph comprises nodes except the first node, repeatedly obtaining a second node in the directed graph according to the execution sequence of each node, obtaining the operation defined by the second node in the service template, and adding a second workflow node in 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 into the preset high-level workflow template, wherein the preset high-level workflow template added to each node in the directed graph is the high-level workflow template, the second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
Optionally, the apparatus further includes an adjusting unit, configured to adjust an execution sequence of each node in the high-level workflow template according to a service requirement.
Optionally, the apparatus further includes an adjusting unit, configured to add at least one workflow node in the high-level workflow template according to a service requirement.
Embodiments of the present invention also provide a computer readable storage medium storing one or more programs, which are executable by one or more processors to implement the steps of the workflow modeling method as described in any one of the above.
The embodiment of the invention provides a workflow modeling method, a workflow modeling device and a computer readable storage medium, wherein the workflow modeling device analyzes an acquired service template to acquire each node defined in the service template; generating a directed graph based on the nodes, wherein the directed graph is used for representing the relationship among the nodes in the service template; generating a high-level workflow template according to the directed graph, wherein the high-level workflow template comprises: the workflow of each node in the service template; and generating a workflow execution script file according to the high-level workflow template, and establishing the association relationship between the workflow execution script file and the service template. According to the workflow modeling method, the workflow modeling device and the computer readable storage medium, an abstract high-level workflow template is automatically generated according to the topological relation of each node in the service template, then a workflow execution script file expressed by a specific workflow execution language is generated according to the high-level workflow template, and finally the modeling of the network service life cycle management workflow is completed.
Drawings
In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals having different letter suffixes may represent different examples of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.
Fig. 1 is a first flowchart of a workflow modeling method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating an example of the dependency between the core content of a blog application TOSCA service template and each node according to an embodiment of the present invention;
FIG. 3 is a second flowchart of a workflow modeling method according to an embodiment of the present invention;
FIG. 4 is a directed graph generated according to a blog application TOSCA service template, as provided by an embodiment of the present invention;
FIG. 5 is a diagram illustrating a high-level workflow template generated from a blog application TOSCA service template, according to an embodiment of the present invention;
FIG. 6 is a schematic diagram illustrating the 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;
fig. 8 is a schematic diagram of a blog application deployment high-level workflow template after adjusting the execution order of nodes according to an embodiment of the present invention;
fig. 9 is a schematic flow chart of a workflow modeling method provided by the embodiment of the present invention;
fig. 10 is a schematic diagram of a high-level workflow template for blog application deployment after adding a custom node according to an embodiment of the present invention;
FIG. 11 is a first schematic structural diagram of a workflow modeling apparatus according to an embodiment of the present invention;
FIG. 12 is a schematic structural diagram of a workflow modeling apparatus according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of a workflow modeling apparatus provided in the embodiment of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.
An embodiment of the present invention provides a workflow modeling method, such as the flowchart shown in fig. 1, where the method may include the following steps:
step 101, analyzing the obtained service template to obtain each node defined in the service template.
Specifically, the execution subject of the workflow modeling method provided in the embodiment of the present invention may be a workflow modeling apparatus, that is, the workflow modeling apparatus obtains a service template, and analyzes the service template to obtain each node defined in the service template, or may be understood as obtaining all nodes defined in the service template.
For example, if the obtained service template is the TOSCA service template as an input, the TOSCA service template as an input is analyzed to obtain all nodes defined in the TOSCA service template.
And 102, generating a directed graph based on the nodes.
Wherein the directed graph is used for representing the relationship among the nodes in the service template.
Specifically, the workflow modeling apparatus traverses all the nodes of the obtained service template, and analyzes the relationship between each node in the service template. Relationships between nodes include, but are not limited to, dependencies (dependents), which include, but are not limited to: relationship of connections (tosca. relationships. connectitsto), host relationship (tosca. relationships. hoston), and the like.
In the service template, two end points are related, namely a provider and a demander, so that a directional line segment can be generated according to the node relationship, the provider of the relationship is an end point pointed by the line segment, and the demander of the relationship is a starting point pointed by the edge. Combining the segments generated by all the relations together generates a directed graph which represents the dependency relations among all the nodes in the service template. An example of a directed graph is shown in fig. 4.
And 103, generating a high-level workflow template according to the directed graph.
Wherein, the high-level workflow template comprises: and the work flow of each node in the service template.
Specifically, a lifecycle management high-level workflow template is generated from the directed graph, the high-level workflow template representing a workflow using a high-level abstract language (information model) that is independent of a concrete workflow language. The information model contains basic elements representing actions, execution order, branch judgment, etc. in the workflow, but adopts an abstract high-level model independent of the concrete workflow language. Each action node therein is from an operation defined by the node in the TOSCA service template, e.g., create, start, stop, delete, etc. Since the high-level workflow template defines an information model independent of a specific workflow language, the high-level workflow template can be converted into any workflow language according to needs.
Optionally, after the generating a high-level workflow template according to the directed graph, the method further includes:
and acquiring a service demand, and adjusting the high-level workflow template according to the service demand to obtain the adjusted high-level workflow template.
Specifically, the service requirement is read, and the execution sequence of each node in the high-level workflow template is adjusted or a new workflow node is added according to the service requirement.
And 104, generating a workflow execution script file according to the high-level workflow template, and establishing the association relationship between the workflow execution script file and the service template.
Specifically, a workflow execution script file expressed by a specific workflow execution language is generated according to the information Model of the high-level workflow template, and the script can be any workflow execution language such as a Business Process Model and Notation (BPMN), a Business Process Execution Language (BPEL), openstack architecture, and the like. The OpenStack is an open-source cloud computing management platform project, and the Mistral is a workflow service component provided by the OpenStack.
Further, the TOSCA service template and the generated workflow script file are correlated, and the correlation between the service template and the script file is generated. The method aims to enable the orchestrator to find and execute the corresponding workflow script according to the association relation when the life cycle management is carried out on the cloud service described by the service template. For example, when the cloud service is deployed, the deployment workflow corresponding to the cloud service template may be found according to the association relationship.
According to the method provided by the embodiment of the invention, an abstract high-level workflow template is automatically generated according to the topological relation of each node in the TOSC service template, the workflow template can be expanded based on the workflow template, the node sequence is adjusted or a user-defined action node is added, then a workflow execution script file expressed by a specific workflow execution language is generated according to the high-level workflow template, and finally the modeling of the network service life cycle management workflow is completed, so that the flexibility of the command workflow is introduced while the convenience of the declarative workflow is taken into account, and the modeling of the network service life cycle management flow under the NFV scene can be effectively supported.
Three specific implementations of the workflow modeling method provided by the embodiment of the invention are illustrated below with a TOSCA service template as an input. The service template describes the composition and topology of a blog application. The blog application runs in a web server and uses a MySql database, both running on the same computing node. The core contents of the TOSCA service template and the dependencies between the various nodes are shown in figure 2.
According to the workflow modeling method provided by the embodiment of the invention, the deployed workflow can be generated according to the service template, and the automatically generated template meets the deployment requirement without adjustment. The workflow modeling method shown in fig. 3 is a flow diagram, and may include the following steps:
step 201, analyzing the obtained service template to obtain each node defined in the service template.
Specifically, the workflow modeling apparatus analyzes the TOSCA service template as an input to obtain all nodes defined in the TOSCA service template. The TOSCA service template is a formatted text file, and each node included in the cloud application is defined in the text file, and specifically may include: the system comprises a server node, a database system node, a database instance node, an application server node and a blog application node. Specifically, the formatted text file can be read in through a text processing program, all nodes are analyzed out, and the nodes are stored in a memory data structure.
Step 202, traversing each node to obtain the relationship among the nodes in the service template; and generating a directed graph according to the relationship among the nodes in the service template.
Specifically, the workflow modeling device traverses all nodes of the TOSCA service template, analyzes the relationship among all nodes in the TOSCA service template, and generates a directed graph. The end points of the directed graph represent nodes in the service template, connecting lines between the nodes are directional, the direction represents the dependency relationship between the nodes, and the node at the starting point of the arrow depends on the node pointed by the arrow.
In this embodiment, the dependency relationship between nodes includes: when the directed graph is generated based on the connection relation (connectitsto) and the host relation (HostOn), the algorithm is a dependency relation, the source node of the connection relation depends on the destination node of the connection relation, the source node of the host relation depends on the destination node of the host relation, and the generated directed graph is specifically shown in fig. 4.
Step 203, acquiring a node in the directed graph according to the execution sequence of each node, and acquiring the operation defined by the node in the service template.
Specifically, a first node in the directed graph is obtained according to an execution sequence of each node, and an operation defined by the first node in the service template is obtained, where the first node is a node starting in the work execution sequence.
Specifically, a node of the directed graph, i.e. the first node, is fetched according to the execution order of each node, and the operations defined by the node, such as creating, starting, stopping, deleting, etc., are obtained from the TOSCA service template.
And step 204, adding a workflow node in a preset high-level workflow template according to the type of the preset life cycle management process, wherein 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 the type of a preset lifecycle management process, wherein the first workflow node is used for indicating the operation defined by the first node.
Specifically, according to the type of the preset lifecycle management process, the corresponding operation of the first node is added to the high-level workflow template, that is, the first workflow node indicating the operation defined by the first node is added to the preset high-level workflow template.
Here, the process steps in the generation of the high-level workflow template in step 204 are related to the lifecycle management type corresponding to the workflow, for example, the deployed workflow template needs to call the creation, start, and configuration operations of the node, and the deleted template needs to call the stop, destroy, and other operations of the node. Since a deployment workflow is created in this embodiment, the corresponding creation, start, and configuration node operations of the node need to be added to the high-level workflow template.
Step 205, judging whether there are more nodes in the directed graph, if so, executing step 203, otherwise, executing step 206.
Specifically, it is determined whether there is a node other than the first node in the directed graph, and if the directed graph includes the node other than the first node, step 203 is executed, otherwise step 206 is executed.
Specifically, when the directed graph includes nodes other than the first node, the operation of obtaining the second node in the directed graph according to the execution sequence of each node is repeated, the operation defined by the second node in the service template is obtained, and the second workflow node is added to a preset high-level workflow template according to the type of the preset lifecycle management process until each node in the directed graph is added to the preset high-level workflow template, and the preset high-level workflow template added to each node in the directed graph is the high-level workflow template.
The second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
Step 206, converting the high-level workflow template into a preset workflow execution script file, and establishing a path association relationship for finding the preset workflow execution script file by the service template.
Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template, and the finally obtained high-level workflow template is as shown in fig. 5. Step 206 converts the high-level workflow template into a Business Process Model and markup (BPMN) workflow script file according to the syntax of the BPMN DSL. The workflow script file may be executed by any workflow engine that complies with the BPMN specification.
Specifically, the created BPMN workflow script file is associated to the TOSCA service template. The deployment lifecycle management workflow of the service template can be directed to an external file plan/deployment. bpmn in the TOSCA service template. BPMN is the BPMN workflow script file generated in the previous step, and the file is stored in the relative directory plan of the TOSCA service template, as shown in fig. 6.
According to the method provided by the embodiment of the invention, an abstract high-level workflow template is automatically generated according to the topological relation of each node in the TOSC service template, then a workflow execution script file expressed by a specific workflow execution language is generated according to the high-level workflow template, and finally the modeling of the network service life cycle management workflow is completed, so that the flexibility of the command workflow is introduced while the convenience of the declarative workflow is considered, and the modeling of the network service life cycle management flow under the NFV scene can be effectively supported.
According to the workflow modeling method provided by the embodiment of the invention, the deployed workflow can be generated according to the service template, and the workflow node sequence of the automatically generated template needs to be adjusted. The workflow modeling method shown in fig. 7 is a flow diagram, and may include the following steps:
step 301, analyzing the obtained service template to obtain each node defined in the service template.
Specifically, the workflow modeling apparatus analyzes the TOSCA service template as an input to obtain all nodes defined in the TOSCA service template. The TOSCA service template is a formatted text file, and each node included in the cloud application is defined in the text file, and specifically may include: the system comprises a server node, a database system node, a database instance node, an application server node and a blog application node. Specifically, the formatted text file can be read in through a text processing program, all nodes are analyzed out, and the nodes are stored in a memory data structure.
Step 302, traversing each node to obtain the relationship among the nodes in the service template; and generating a directed graph according to the relationship among the nodes in the service template.
Specifically, the workflow modeling device traverses all nodes in the TOSCA service template, analyzes the relationship among all nodes in the TOSCA service template, and generates a directed graph. The end points of the directed graph represent nodes in the service template, connecting lines between the nodes are directional, the direction represents the dependency relationship between the nodes, and the node at the starting point of the arrow depends on the node pointed by the arrow. In this embodiment, the dependency relationship between the nodes includes a connection relationship (connectitsto) and a host relationship (HostOn), when the directed graph is generated, the algorithm is the dependency relationship, the source node of the connection relationship depends on the destination node of the connection relationship, the source node of the host relationship depends on the destination node of the host relationship, and the generated directed graph is specifically shown in fig. 4.
Step 303, acquiring a node in the directed graph according to the execution sequence of each node, and acquiring the operation defined by the node in the service template.
Specifically, a first node in the directed graph is obtained according to an execution sequence of each node, and an operation defined by the first node in the service template is obtained, where the first node is a node starting in the work execution sequence.
Specifically, a node of the directed graph, i.e. the first node, is fetched according to the execution order of each node, and the operations defined by the node, such as creating, starting, stopping, deleting, etc., are obtained from the TOSCA service template.
And step 304, adding a workflow node in a preset high-level workflow template according to the type of the preset life cycle management process, wherein 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 the type of a preset lifecycle management process, wherein the first workflow node is used for indicating the operation defined by the first node.
Specifically, according to the type of the preset lifecycle management flow, the corresponding operation of the first node is added to the high-level workflow template, that is, the first workflow node indicating the operation defined by the first node is added to the preset high-level workflow template.
And 305, judging whether more nodes exist in the directed graph, if so, executing the step 303, otherwise, executing the step 306.
Specifically, it is determined whether there is a node other than the first node in the directed graph, and if the directed graph includes the node other than the first node, step 303 is executed, otherwise step 306 is executed.
Specifically, when the directed graph includes nodes other than the first node, the operation of obtaining the second node in the directed graph according to the execution sequence of each node is repeated, the operation defined by the second node in the service template is obtained, and the second workflow node is added to a preset high-level workflow template according to the type of the preset lifecycle management process until each node in the directed graph is added to the preset high-level workflow template, and the preset high-level workflow template added to each node in the directed graph is the high-level workflow template.
The second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
And step 306, acquiring a service requirement, and adjusting the execution sequence of each node in the high-level workflow template according to the service requirement to obtain an adjusted high-level workflow template.
Specifically, the service requirement may be known according to the actual service requirement of the user, and the execution sequence of each node in the automatically generated high-level workflow template is adjusted. To avoid operating system global resource locks (e.g., the apt and yum tools require global locks and do not support concurrency), the various operational nodes in the automatically generated default high-level workflow template are executed serially, but may be executed concurrently if the deployment operation does not involve a global resource lock to speed up execution efficiency. In this embodiment, assuming that the operations of the nodes do not depend on the global resources of the operating system, the deployment flows of the database and the web server may be adjusted to be executed serially, for example, as shown in fig. 8.
Step 307, converting the adjusted high-level workflow template into a preset workflow execution script file, and establishing a path association relationship for finding the preset workflow execution script file by the service template.
Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template, and the finally obtained high-level workflow template is as shown in fig. 8. This step converts the high-level workflow template into a BPEL workflow script file according to the syntax of BPELDSL. The workflow script file can be executed by any workflow engine that complies with the BPEL specification.
Further, the created BPEL workflow script file is associated to the TOSCA service template. The deployment lifecycle management workflow of the service template can be directed to an external file plan/deployment. 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.
According to the method provided by the embodiment of the invention, an abstract high-level workflow template is automatically generated according to the topological relation of each node in the TOSC service template, the workflow template can be expanded based on the workflow template, the node sequence is adjusted, then a workflow execution script file expressed by a specific workflow execution language is generated according to the high-level workflow template, and finally the modeling of the network service life cycle management workflow is completed, so that the flexibility of the command workflow is introduced while the convenience of the declarative workflow is considered, and the modeling of the network service life cycle management flow under the NFV scene can be effectively supported.
The embodiment of the invention provides a workflow modeling method, which generates a deployed workflow according to a service template and needs to add a user-defined workflow node. The workflow modeling method shown in fig. 9 is a flow diagram, and may include the following steps:
step 401, analyzing the obtained service template to obtain each node defined in the service template.
Specifically, the workflow modeling apparatus analyzes the TOSCA service template as an input to obtain all nodes defined in the TOSCA service template. The TOSCA service template is a formatted text file, and each node included in the cloud application is defined in the text file, and specifically may include: the system comprises a server node, a database system node, a database instance node, an application server node and a blog application node. Specifically, the formatted text file can be read in through a text processing program, all nodes are analyzed out, and the nodes are stored in a memory data structure.
Step 402, traversing each node to obtain the relationship among each node in the service template; and generating a directed graph according to the relationship among the nodes in the service template.
Specifically, the workflow modeling device traverses all nodes of the TOSCA service template, analyzes the relationship among all nodes in the TOSCA service template, and generates a directed graph. The end points of the directed graph represent nodes in the service template, the connecting lines between the nodes are directional, the directions represent the dependency relationships between the nodes, and the node at the starting point of the arrow depends on the node pointed by the arrow.
In this embodiment, the relationship between nodes includes: when the directed graph is generated by using the connection relation (connectitsto) and the host relation (HostOn), the algorithm is a dependency relation, the source node of the connection relation depends on the destination node of the connection relation, the source node of the host relation depends on the destination node of the host relation, and the generated directed graph is as shown in fig. 4.
Step 403, acquiring a node in the directed graph according to the execution sequence of each node, and acquiring the operation defined by the node in the service template.
Specifically, the first node in the directed graph is obtained according to the execution sequence of each node, and the operation defined by the first node in the service template is obtained. Wherein the first node is a node starting in the work execution sequence.
Specifically, a node of the directed graph, i.e., the first node, is taken out according to the execution sequence of each node, and the operations defined by the node, such as creating, starting, stopping, deleting and the like, are obtained from the TOSCA service template.
And step 404, adding a workflow node in a preset high-level workflow template according to the type of the preset life cycle management process, wherein the workflow node represents the operation of the directed graph node.
Specifically, a first workflow node is added into a preset high-level workflow template according to the type of a preset life cycle management process. Wherein the first workflow node is to indicate operations defined by the first node.
Specifically, according to the type of the preset lifecycle management process, the corresponding operation of the node is added to the high-level workflow template, and since the deployment workflow is created in this embodiment, the corresponding creation, starting, and configuration of the node operation are required to be added to the high-level workflow template.
And 405, judging whether the directed graph has more nodes, if so, executing the step 403, and otherwise, executing the step 406.
Specifically, it is determined whether there is a node other than the first node in the directed graph, and if the directed graph includes the node other than the first node, step 403 is executed, otherwise step 406 is executed.
Specifically, when the directed graph includes nodes other than the first node, the operation of obtaining the second node in the directed graph according to the execution sequence of each node is repeated, the operation defined by the second node in the service template is obtained, and the second workflow node is added to a preset high-level workflow template according to the type of the preset lifecycle management process until each node in the directed graph is added to the preset high-level workflow template, and the preset high-level workflow template added to each node in the directed graph is the high-level workflow template.
The second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
And 406, acquiring a service requirement, and adding at least one workflow node in the high-level workflow template according to the service requirement to obtain an adjusted high-level workflow template.
Illustratively, the business requirement is a requirement to import data from another blog site when deploying the service. Since the logic cannot be represented in the TOSCA service template, a custom workflow node needs to be added for processing, a workflow node for importing data is added in the high-level workflow template generated in the previous step, and the newly added workflow node calls a shell script to import data from another blog website to a newly created blog application, as shown in fig. 10.
Step 407, converting the adjusted high-level workflow template into a preset workflow execution script file, and establishing a path association relationship for finding the preset workflow execution script file by the service template.
Specifically, the above steps generate a high-level workflow template for deploying the service template according to the TOSCA service template, and the final high-level workflow template is as shown in fig. 10. This step converts the high level workflow template into a yaml workflow script file (the OpenStack workflow is defined in yaml format) according to the syntax of the OpenStack workflow. The workflow script file can be executed by any OpenStack Mistral compliant workflow engine.
Further, the created Mistral workflow script file is associated to a TOSCA service template. The default lifecycle management workflow of the service template can be directed to an external file plan/default.yaml in the TOSCA service template. Yaml is the misreal workflow script file generated in the previous step, which is stored in the opposite directory plan of the TOSCA service template.
According to the method provided by the embodiment of the invention, an abstract high-level workflow template is automatically generated according to the topological relation of each node in the TOSC service template, the template can be expanded based on the workflow template, a user-defined action node is added, then a workflow execution script file expressed by a specific workflow execution language is generated according to the high-level workflow template, and finally the modeling of the network service life cycle management workflow is completed, so that the flexibility of the command workflow is introduced while the convenience of the declarative workflow is considered, and the modeling of the network service life cycle management flow under the NFV scene can be effectively supported.
An embodiment of the present invention further provides a workflow modeling apparatus 50, as shown in fig. 11, including:
an analyzing unit 501, configured to analyze the obtained service template to obtain each node defined in the service template;
a generating unit 502, configured to generate a directed graph based on the nodes, where the directed graph is used to represent a relationship between the nodes in the service template; and the high-level workflow template is also used for generating a high-level workflow template according to the directed graph, and the high-level workflow template comprises: the workflow of each node in the service template; and the workflow execution script file is generated according to the high-level workflow template, and the association relation between the workflow execution script file and the service template is established.
Optionally, the generating unit 502 is specifically configured to:
traversing each node to obtain the relationship among the nodes in the service template;
and generating the directed graph according to the relationship among the nodes in the service template.
Optionally, the generating unit 502 is specifically configured to:
acquiring a first node in the directed graph according to the execution sequence of each node, acquiring an operation defined by the first node in the service template, and adding a first workflow node in a preset high-level workflow template according to the type of a preset life cycle management process, wherein the first node is a node started in the work execution sequence, and the first workflow node is used for indicating the operation defined by the first node;
when the directed graph comprises nodes except the first node, repeatedly obtaining a second node in the directed graph according to the execution sequence of each node, obtaining the operation defined by the second node in the service template, and adding a second workflow node in 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 into the preset high-level workflow template, wherein the preset high-level workflow template added to each node in the directed graph is the high-level workflow template, the second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
Optionally, as shown in fig. 12, the apparatus further includes an adjusting unit 503, configured to obtain a service requirement, adjust the high-level workflow template according to the service requirement, and obtain the adjusted high-level workflow template.
Optionally, as shown in fig. 12, the apparatus further includes an adjusting unit 503, configured to adjust an execution sequence of each node in the high-level workflow template according to a service requirement.
Optionally, as shown in fig. 12, the apparatus further includes an adjusting unit 503, configured to add at least one workflow node in the higher layer workflow template according to a service requirement.
Optionally, the generating unit 502 is specifically configured to:
and 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 relation for searching the preset workflow execution script file by the service template.
Specifically, for understanding of the workflow modeling apparatus provided in the embodiment of the present invention, reference may be made to the description of the workflow modeling method embodiment described above, and details of the embodiment of the present invention are not described herein again.
The workflow modeling device provided by the embodiment of the invention automatically generates an abstract high-level workflow template according to the topological relation of each node in the TOSC service template, can be expanded based on the workflow template, adjusts the node sequence or adds a self-defined action node, then generates a workflow execution script file expressed by a specific workflow execution language according to the high-level workflow template, and finally completes the modeling of the network service life cycle management workflow, thereby introducing the flexibility of the command workflow while considering the convenience of the declarative workflow, and effectively supporting the modeling of the network service life cycle management flow under the NFV scene.
An embodiment of the present invention further provides a workflow modeling apparatus 60, as shown in fig. 13, where the workflow modeling apparatus 60 includes a processor 601 and a memory 602; wherein the content of the first and second substances,
the memory 602 for storing a computer program operable on the processor;
the processor 601 is configured to execute the steps of the workflow modeling method as described above when running the computer program.
It will be appreciated that the memory 602 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 602 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.
The method disclosed by the above-mentioned embodiment of the present invention can be applied to the processor 601, or implemented by the processor 601. The processor 601 may be an integrated circuit chip having signal processing capabilities, and more particularly, incorporating workflow modeling algorithms, i.e., having workflow modeling capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 601. The Processor 601 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. Processor 601 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 602, and the processor 601 reads the information in the memory 602 and performs the steps of the aforementioned methods in conjunction with its hardware.
In an exemplary embodiment, the workflow modeling apparatus may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, Micro Controllers (MCUs), microprocessors (microprocessors), or other electronic components for performing the foregoing methods.
In an exemplary embodiment, the embodiment of the present invention further provides a storage medium, which may be specifically a computer-readable storage medium, for example, a memory including a computer program, where the computer program is executable by a processor of a workflow modeling apparatus to perform the steps of the foregoing method. The computer readable storage medium may be Memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM.
Embodiments of the present invention provide a computer readable storage medium storing one or more programs, which are executable by one or more processors to implement the steps of a workflow modeling method as described in any one of the above.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (12)
1. A workflow modeling method, comprising:
analyzing the obtained service template to obtain each node defined in the service template;
generating a directed graph based on the nodes, wherein the directed graph is used for representing the relationship among the nodes in the service template;
generating a high-level workflow template according to the directed graph, wherein the high-level workflow template comprises: the workflow of each node in the service template;
and generating a workflow execution script file according to the high-level workflow template, and establishing the association relationship between the workflow execution script file and the service template.
2. The method according to claim 1, wherein the generating a directed graph based on the respective nodes comprises:
traversing each node to obtain the relationship among the nodes in the service template;
and generating the directed graph according to the relationship among the nodes in the service template.
3. The method of claim 1, wherein generating the high-level workflow template from the directed graph comprises:
acquiring a first node in the directed graph according to the execution sequence of each node, acquiring an operation defined by the first node in the service template, and adding a first workflow node in a preset high-level workflow template according to the type of a preset life cycle management process, wherein the first node is a node started in the work execution sequence, and the first workflow node is used for indicating the operation defined by the first node;
when the directed graph comprises nodes except the first node, repeatedly obtaining a second node in the directed graph according to the execution sequence of each node, obtaining the operation defined by the second node in the service template, and adding a second workflow node in 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 into the preset high-level workflow template, wherein the preset high-level workflow template added to each node in the directed graph is the high-level workflow template, the second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
4. The method of claim 1, wherein after the generating a high-level workflow template from the directed graph, the method further comprises:
and acquiring a service demand, and adjusting the high-level workflow template according to the service demand to obtain the adjusted high-level workflow template.
5. The method of claim 4, wherein said adjusting the higher layer workflow template according to the business requirement comprises:
and adjusting the execution sequence of each node in the high-level workflow template according to the service requirement.
6. The method of claim 4, wherein said adjusting the higher layer workflow template according to the business requirement comprises:
and adding at least one workflow node in the high-level workflow template according to the service requirement.
7. 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 comprises:
and 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 relation for searching the preset workflow execution script file by the service template.
8. A workflow modeling apparatus, comprising:
the analysis unit is used for analyzing the acquired service template to acquire each node defined in the service template;
a generating unit, configured to generate a directed graph based on the nodes, where the directed graph is used to represent a relationship between the nodes in the service template; and the high-level workflow template is also used for generating a high-level workflow template according to the directed graph, and the high-level workflow template comprises: the workflow of each node in the service template; and the workflow execution script file is generated according to the high-level workflow template, and the association relation between the workflow execution script file and the service template is established.
9. The apparatus according to claim 8, wherein the generating unit is specifically configured to:
acquiring a first node in the directed graph according to the execution sequence of each node, acquiring an operation defined by the first node in the service template, and adding a first workflow node in a preset high-level workflow template according to the type of a preset life cycle management process, wherein the first node is a node started in the work execution sequence, and the first workflow node is used for indicating the operation defined by the first node;
when the directed graph comprises nodes except the first node, repeatedly obtaining a second node in the directed graph according to the execution sequence of each node, obtaining the operation defined by the second node in the service template, and adding a second workflow node in 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 into the preset high-level workflow template, wherein the preset high-level workflow template added to each node in the directed graph is the high-level workflow template, the second node is a node executed after the first node, and the second workflow node is used for indicating the operation defined by the second node.
10. The apparatus according to claim 8 or 9, further comprising an adjusting unit configured to adjust an execution sequence of each node in the higher layer workflow template according to a service requirement.
11. The apparatus according to claim 8 or 9, further comprising an adjusting unit configured to add at least one workflow node in the higher layer workflow template according to a business requirement.
12. A computer readable storage medium, characterized in that the computer readable storage medium stores one or more programs which are executable by one or more processors to implement the steps of the workflow modeling method as claimed in any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810616144.8A CN110609675B (en) | 2018-06-14 | 2018-06-14 | Workflow modeling method and device and computer readable storage medium |
| PCT/CN2019/092336 WO2019238136A1 (en) | 2018-06-14 | 2019-06-21 | Workflow modeling method and device and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810616144.8A CN110609675B (en) | 2018-06-14 | 2018-06-14 | Workflow modeling method and device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110609675A true CN110609675A (en) | 2019-12-24 |
| CN110609675B CN110609675B (en) | 2023-08-08 |
Family
ID=68842751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810616144.8A Active CN110609675B (en) | 2018-06-14 | 2018-06-14 | Workflow modeling method and device and computer readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110609675B (en) |
| WO (1) | WO2019238136A1 (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162737A (en) * | 2020-10-13 | 2021-01-01 | 深圳晶泰科技有限公司 | Universal description language data system of directed acyclic graph automatic task flow |
| CN112181854A (en) * | 2020-10-30 | 2021-01-05 | 重庆农村商业银行股份有限公司 | Method, device, equipment and storage medium for generating flow automation script |
| CN112579325A (en) * | 2020-12-29 | 2021-03-30 | 上海众源网络有限公司 | Business object processing method and device, electronic equipment and storage medium |
| CN112631696A (en) * | 2020-12-29 | 2021-04-09 | 智慧神州(北京)科技有限公司 | Service arranging method, arranging device, processor and service arranging system |
| CN112685154A (en) * | 2020-12-25 | 2021-04-20 | 北京有竹居网络技术有限公司 | Data processing method of task flow engine, device and medium |
| CN113596037A (en) * | 2021-07-31 | 2021-11-02 | 南京云利来软件科技有限公司 | APT attack detection method based on event relation directed graph in network full flow |
| CN114691187A (en) * | 2020-12-29 | 2022-07-01 | 北京嘀嘀无限科技发展有限公司 | Node registration method and device, computer equipment and storage medium |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114489572B (en) * | 2020-11-13 | 2023-12-29 | 华为技术有限公司 | Service demand adjustment method and related equipment |
| CN113031929B (en) * | 2021-04-29 | 2024-04-09 | 中国工商银行股份有限公司 | Service realization method and device |
| US11934817B2 (en) * | 2021-10-25 | 2024-03-19 | Jpmorgan Chase Bank, N.A. | Systems and methods for deploying federated infrastructure as code |
| CN115455135B (en) * | 2022-06-30 | 2023-10-31 | 北京九章云极科技有限公司 | Visual automatic modeling method and device, electronic equipment and storage medium |
| CN117234882B (en) * | 2023-09-28 | 2024-04-16 | 哈尔滨工业大学（威海） | Online application cloud resource supply software definition model construction method and terminal |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103761111A (en) * | 2014-02-19 | 2014-04-30 | 中国科学院软件研究所 | Method and system for constructing data-intensive workflow engine based on BPEL language |
| CN105243521A (en) * | 2015-11-20 | 2016-01-13 | 华润电力投资有限公司河南分公司 | Workflow management method and system |
| CN106961453A (en) * | 2016-01-08 | 2017-07-18 | 中兴通讯股份有限公司 | Service calling method and device based on TOSCA |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9461876B2 (en) * | 2012-08-29 | 2016-10-04 | Loci | System and method for fuzzy concept mapping, voting ontology crowd sourcing, and technology prediction |
| CN107766042A (en) * | 2016-08-23 | 2018-03-06 | 南京中兴软件有限责任公司 | A kind of visual data manager and device of the model file based on CSAR |
-
2018
- 2018-06-14 CN CN201810616144.8A patent/CN110609675B/en active Active
-
2019
- 2019-06-21 WO PCT/CN2019/092336 patent/WO2019238136A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103761111A (en) * | 2014-02-19 | 2014-04-30 | 中国科学院软件研究所 | Method and system for constructing data-intensive workflow engine based on BPEL language |
| CN105243521A (en) * | 2015-11-20 | 2016-01-13 | 华润电力投资有限公司河南分公司 | Workflow management method and system |
| CN106961453A (en) * | 2016-01-08 | 2017-07-18 | 中兴通讯股份有限公司 | Service calling method and device based on TOSCA |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162737A (en) * | 2020-10-13 | 2021-01-01 | 深圳晶泰科技有限公司 | Universal description language data system of directed acyclic graph automatic task flow |
| CN112181854A (en) * | 2020-10-30 | 2021-01-05 | 重庆农村商业银行股份有限公司 | Method, device, equipment and storage medium for generating flow automation script |
| CN112181854B (en) * | 2020-10-30 | 2023-12-22 | 重庆农村商业银行股份有限公司 | Method, device, equipment and storage medium for generating process automation script |
| CN112685154A (en) * | 2020-12-25 | 2021-04-20 | 北京有竹居网络技术有限公司 | Data processing method of task flow engine, device and medium |
| CN112579325A (en) * | 2020-12-29 | 2021-03-30 | 上海众源网络有限公司 | Business object processing method and device, electronic equipment and storage medium |
| CN112631696A (en) * | 2020-12-29 | 2021-04-09 | 智慧神州(北京)科技有限公司 | Service arranging method, arranging device, processor and service arranging system |
| CN114691187A (en) * | 2020-12-29 | 2022-07-01 | 北京嘀嘀无限科技发展有限公司 | Node registration method and device, computer equipment and storage medium |
| CN113596037A (en) * | 2021-07-31 | 2021-11-02 | 南京云利来软件科技有限公司 | APT attack detection method based on event relation directed graph in network full flow |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019238136A1 (en) | 2019-12-19 |
| CN110609675B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110609675A (en) | Workflow modeling method and device and computer readable storage medium | |
| US11714621B2 (en) | Application blueprints based on service templates to deploy applications in different cloud environments | |
| US11347555B2 (en) | Integrated system to distribute and execute complex applications | |
| US20190155578A1 (en) | Determining the identity of software in software containers | |
| US9047160B2 (en) | Designing and building virtual images using semantically rich composable software image bundles | |
| JP5941541B2 (en) | System and method for mobile application development | |
| US20180113799A1 (en) | Model generation for model-based application testing | |
| US11048524B2 (en) | Creating a tokenized process template for invoking one or more services by replacing service references with respective tokens | |
| WO2018036342A1 (en) | Csar-based template design visualization method and device | |
| US11113050B2 (en) | Application architecture generation | |
| CN111104103B (en) | Visualization method and system for software editing micro-service | |
| US20170048331A1 (en) | Platform runtime abstraction | |
| CN111399840B (en) | Module development method and device | |
| JP6917695B2 (en) | Hierarchical data export from source code control (SCM) system to product lifecycle management (PLM) system | |
| EP3447635A1 (en) | Application architecture generation | |
| US9501263B2 (en) | Automated model derivation and alignment | |
| US9116777B1 (en) | In-flight process instance migration between business process execution language (BPEL) suites | |
| CN113805882A (en) | Method and device for developing application program, electronic equipment and storage medium | |
| Rivero et al. | MockAPI: an agile approach supporting API-first web application development | |
| CN110704031A (en) | Software application project creating method and device and electronic equipment | |
| Harzenetter et al. | Automated generation of management workflows for applications based on deployment models | |
| CN113835705A (en) | Big data service product development method, device and system | |
| CN116569141A (en) | Workflow repair | |
| US20220413843A1 (en) | Combining model-driven applications and canvas-type applications with application lifecycle management | |
| Harzenetter et al. | An Integrated Management System for Composed Applications Deployed by Different Deployment Automation Technologies |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |