WO2018036342A1

WO2018036342A1 - Csar-based template design visualization method and device

Info

Publication number: WO2018036342A1
Application number: PCT/CN2017/095176
Authority: WO
Inventors: 王淼; 徐代刚; 吕波; 黄健
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-08-23
Filing date: 2017-07-31
Publication date: 2018-03-01
Also published as: CN107766042A

Abstract

A CSAR-based template design visualization method and device. The method comprises: developing, on a visualization interface of a user interface development environment (UIDE) platform, and on the basis of a preconfigured network function virtualization (NFV) scenario, a template tree, and creating a plurality of indexes based on CSAR template files (210); creating, on the basis of the indexes, a node type and a node correspondence type of the template files, and defining a topology structure between nodes (220); and scheduling workflows for the nodes to obtain the template files (230).

Description

Visual design method and device for model file based on CSAR

Technical field

The present disclosure relates to the field of information technology, for example, to a visual design method and apparatus for a CSAR-based model file.

Background technique

In recent years, cloud computing and virtualization technologies have developed rapidly, bringing a lot of innovations and putting a lot of pressure on operators. The problem facing operators is how to find new revenue growth points to offset the video of the open Internet. (Over the Top, OTT) The impact of the business, reducing the company's management expenditure (OPEX), and quickly launching business.

The Topology and Orchestration Specification for Cloud Applications (TOSCA) is proposed by the Organization for The Advancement Of Structured Information Standards (OASIS). The specification consists of two parts: the network topology, which describes the composition of the cloud application and the services that can be provided by multiple nodes of the cloud application. The orchestration information is a collection of services provided by multiple nodes in the topology, which can be expressed as planned Plan work. Flow mode. As shown in Figure 1, the left side of the figure is the service template structure diagram of the TOSCA model, and the right side is the file structure diagram defined by the TOSCA model. In TOSCA, the corresponding archive format of the model file is called Cloud Service Archive (CSAR). Design a CSAR that conforms to the specification and deploy it in a specific environment to execute and manage the lifecycle of a cloud application.

TOSCA is a set of specifications that point out how to describe a cloud application. A TOSCA-compliant application can generate a conforming model, the TOSCA model, and the application can parse the TOSCA model. However, TOSCA did not explain how to design a build model file, nor how the model file should be deployed.

For example, in the TOSCA model, there must be a TOSCA-Metadata folder containing the TOSCA.meta file for recording information about the model; and for the development of the Plan workflow, you can use a variety of different standard workflow languages ( Such as BPEL2.0, BPMN2.0), you can also write the processing flow yourself. For developers, there is no suitable integrated development environment, and the development and modification of standard model files is more complicated. At the same time, there is no ready-made environment to deploy the TOSCA model, which is difficult to test and use.

Summary of the invention

The present disclosure provides a visual design method and apparatus for a model file based on a Cloud Service Archive (CSAR) to solve a CSAR-based model file in the related art without a suitable integrated development environment, and a standard model file. Develop and modify more complex issues.

An aspect of the present disclosure provides a visual design method for a CSAR-based model file, including:

On the visual interface of the UIDE platform of the user interface development environment, the model tree is developed based on the preset Network Function Virtualization (NFV) scenario, and multiple directories of the model file based on the cloud service architecture CSAR are created;

Creating a node type and a node relationship type of the model file based on the directory, and defining a topology between the nodes;

Workflow orchestration is performed on the node to obtain the model file.

Optionally, the method further includes:

The model file is uploaded to the TOSCA server, and the TOSCA server is triggered to complete the parsing and service deployment of the model file.

Optionally, the method further includes:

The TOSCA server is triggered to obtain a service that can be provided by the model file, and the parsing of the model file is completed by calling the service.

Optionally, the triggering the TOSCA server completes parsing and service deployment of the model file, including:

Triggering the TOSCA server to decompress the model file to generate a temporary file, parsing the temporary file, saving the node attribute and the relationship attribute between the nodes, saving the deployment file location information of the node according to the node definition, and acquiring the service provided by the node according to the node definition The corresponding implementation file, the corresponding plug-in is called for deployment, and the correspondence between the service provided by the node and the deployment information of the node service is saved.

Optionally, the NFV scenario development model tree is a development directory defined by a file structure of the model file according to the cloud application-based topology and the business process specification TOSCA.

Another aspect of the present disclosure provides a visual design device for a CSAR-based model file, including:

Developing a project tree component, set to develop a model tree based on a preset network function virtualized NFV scenario on a visual interface of the UIDE platform of the user interface development environment, and creating the CSAR-based model Multiple directories of files;

a modeling tool component, configured to create a node type and a node relationship type of the model file based on the directory, and define a topology between the nodes;

A workflow designer is configured to perform workflow scheduling on the node to obtain the CSAR-based model file.

Optionally, the device further includes: a deployment server component;

The modeling tool component is configured to upload the model file to a TOSCA server and trigger the deployment server component;

The deployment server component is configured to enable the TOSCA server to complete parsing and service deployment of the model file under the trigger of the modeling tool component.

Optionally, the apparatus further includes: a workflow server component, configured to trigger the TOSCA server to obtain a service that the model file can provide, and complete the parsing of the model file by calling the service.

Optionally, the deployment server component is configured to: trigger a TOSCA server to decompress the model file to generate a temporary file, parse the temporary file, save a node attribute, and a relationship attribute between the nodes, and save the node deployment file according to the node definition. The location information is obtained, and the implementation file corresponding to the service provided by the node is obtained according to the node definition, and the corresponding plug-in is invoked for deployment, and the corresponding relationship between the service provided by the node and the deployment information of the node service is saved.

Optionally, the NFV scenario development model tree is a development directory defined according to a file structure of the model file of the TOSCA.

The present disclosure also provides a computer readable storage medium storing computer executable instructions for performing a visual design method of the CSAR-based model file described above.

The present disclosure develops a model tree based on a preset NFV scenario, creates a plurality of directories of a model file, and creates a node type, a node relationship type, and a node of the model file according to the directory, on a visual interface of the integrated development environment UIDE platform. The topology between the two, and finally through the workflow of multiple nodes orchestration, get the model file. The present disclosure uses the integrated development environment UIDE for development, enhances development efficiency through powerful functional components, and reduces development difficulty and simplifies development of model files through "what you see is what you get" visual development methods and standardized development processes. The modified steps effectively avoid the problem that the CSAR-based model files in the related technology do not have a suitable integrated development environment, and the development and modification of standard model files are complicated.

DRAWINGS

1 is a schematic structural diagram of a cloud service archive in the related art;

2 is a schematic flow chart of a visual design method of a CSAR-based model file according to the embodiment;

3 is a schematic flow chart of another visual design method of a CSAR-based model file according to the embodiment;

4 is a schematic flowchart of a method for automatically deploying a CSAR-based model file according to the embodiment;

FIG. 5 is a schematic flowchart diagram of a visual design and an automated deployment method of a CSAR-based model file according to the embodiment; FIG.

6 is a schematic diagram of a visual design and an automated deployment framework of a CSAR-based model file according to the embodiment;

7 is a schematic structural diagram of a visual design device for a CSAR-based model file according to the embodiment;

8 is a schematic structural diagram of another visual design device for a CSAR-based model file according to the embodiment;

FIG. 9 is a schematic diagram showing the hardware structure of a communication device according to this embodiment.

detailed description

In order to solve the problem that the CSAR-based model file in the related art does not have a suitable integrated development environment, and the development and modification of the standard model file is complicated, the embodiment provides a visual design method and device for the CSAR-based model file. In this embodiment, a user interface development environment (UIDE) is used to develop a model file, wherein UIDE is an integrated development environment (IDE), and the development efficiency is improved by powerful functional components. Through the "what you see is what you get" visual development method and the standardized development process, the development difficulty is reduced. Finally, through the association of UIDE and TOSCA server, the developed model file can be directly deployed to the TOSCA server, simplifying the model file. The steps of development and modification effectively avoid the problem that the CSAR-based model files in the related technologies do not have a suitable integrated development environment, and the development and modification of standard model files are complicated. The present disclosure will be described in detail below with reference to the accompanying drawings and embodiments. This embodiment provides a model text based on CSAR The visual design method of the piece, see FIG. 2, the method may include the following steps.

In step 210, on the visual interface of the integrated development environment UIDE platform, a model tree based on a preset Network Function Virtualization (NFV) scenario is developed to create a plurality of directories of CSAR-based model files.

In step 220, based on the directory, a node type and a node relationship type of the model file are created, and a topology between the nodes is defined.

In step 230, workflow processing is performed on the node to obtain the model file.

In this embodiment, on the visual interface of the integrated development environment UIDE platform, the model tree is developed based on the preset NFV scenario, multiple directories of the model file are created, and the node type and node relationship type of the model file are created according to the directory, and The topology between nodes is obtained by workflow orchestration of multiple nodes to obtain a model file. This embodiment uses the integrated development environment UIDE for development, improves development efficiency through powerful functional components, and reduces development difficulty and simplifies development of model files through "what you see is what you get" visual development method and standardized development process. And the steps of modification can effectively avoid the problem that the CSAR-based model file in the related technology does not have a suitable integrated development environment, and the development and modification of the standard model file is complicated.

The step 210 of the embodiment may include: the embodiment uses an integrated development environment UIDE platform, develops a model tree based on a preset NFV scenario, and obtains a catalog of CSAR plan plans and the like.

The development model tree of the preset NFV scenario described in this embodiment is a TOCCA-metadata, Plans, and other file development directory defined according to the file structure of the TOSCA model file.

The directory described in this embodiment includes a directory of all nodes of the template of the cloud service archive CSAR in FIG. 1, such as TOSCA metadata TOSCA-Metadata and the like.

Those skilled in the art can set the NFV scenario development model tree according to actual needs, and clear the relationship between multiple directories under the NFV scenario development model tree through the visual interface of the UIDE platform.

The step 220 described in this embodiment may include the following steps.

Through the modeling tool, on the UIDE visual interface, create node types and node relationship types based on existing directories, and define the topology between nodes.

In this embodiment, a definition function of a node type, a node type, a relationship type, and the like is defined on a visual interface, and a topology is designed by selecting and connecting nodes by dragging and dropping the visual interface.

The step S230 in this embodiment may include: programming the process by using a workflow designer.

Optionally, in this embodiment, a workflow file is designed by dragging and selecting a process node, setting a sequence relationship, and the like on the visual interface.

In this embodiment, the workflow definition information corresponding to the model saved in the Plans directory is configured by using a workflow designer.

FIG. 3 is a schematic flowchart of a visual design method of another CSAR-based model file according to the embodiment. As shown in FIG. 3, on the UIDE visual interface, the visual design method of the model file in this embodiment includes the following steps.

In step 310, a node type is defined, and a node's attributes and interface implementations are set.

In step 320, the relationship type of the node is defined, and the attributes of the relationship and the interface implementation are set.

In step 330, one or more node templates are created.

In step 340, a new relationship template is created based on the relationship type and the nodes are connected.

In step 350, through the workflow designer, the calling process is programmed, the Plan workflow is designed, and the Plan workflow is added to the template definition.

In step 360, a TOSCA compliant model file is generated.

Optionally, the method in this embodiment may further include the following steps.

Optionally, in this embodiment, the model file is directly uploaded to the TOSCA server for automatic deployment by using an association function with the TOSCA server. The TOSCA server receives the upload request of the model file, saves the model file, completes the parsing and service deployment of the model file information, and completes the NFV task scheduling by calling the service.

The step of triggering the TOSCA server to complete parsing and service deployment of the model file may include the following steps.

The model file is decompressed to generate a temporary file, the temporary file is parsed, the node attribute and the relationship attribute between the nodes are saved, and the deployment file location information of the node is saved according to the node definition.

The implementation file corresponding to the node providing service is obtained according to the node definition, and the corresponding plug-in is invoked for deployment, and the corresponding relationship between the service provided by the node and the deployment information of the node service is saved.

As shown in FIG. 4, the automatic deployment method of the model file according to the embodiment of the present invention may include the following steps.

In step 410, the UIDE uploads the model file to the TOSCA server.

In step 420, the model file is decompressed to generate a temporary file.

In step 430, the template definition information in the temporary file is parsed, and the node attribute and the relationship attribute between the nodes are saved.

In step 440, the deployment file location information of the node is saved according to the node definition.

In step 450, the implementation file (script, WAR package, etc.) corresponding to the service provided by the node is obtained according to the node definition, and the corresponding plug-in is invoked for deployment, and the correspondence between the service provided by the node and the deployment information of the node service is saved.

In step 460, according to the definition of the Plan workflow in the template, the corresponding workflow server is invoked for different types of Plan workflows, the process definition information is deployed, and the calling relationship between the template and the deployment process is saved.

In step 470, the temporary file information is deleted and the deployment is completed.

FIG. 5 is a schematic flowchart of a visual design and an automated deployment method of a CSAR-based model file according to the embodiment. As shown in FIG. 5, the method in this embodiment includes the following steps.

In step 510, based on the integrated development environment UIDE platform, the model tree is developed through the NFV scenario, and a directory such as the CSAR Plans is obtained.

In step 520, a node type and a node relationship type are created on the UIDE visual interface through a modeling tool to define a topology between the nodes.

In step 530, the workflow definition information corresponding to the model is saved in the Plans directory, and the workflow designer is used to arrange the flow.

In step 540, the designed workflow file is imported into the modeling tool to complete the design of the CSAR-based model file.

In step 550, the model file is directly uploaded to the TOSCA server through an association function with the TOSCA server.

In step 560, the TOSCA server receives the model file upload request, saves the model file, and completes parsing and service deployment of the model file information.

In step 570, the workflow server parses and provides a call interface.

In step 580, the model information of the CSAR, the provided service information, and the like are obtained from the service provided by the TOSAC server, and the arrangement of the NFV task is completed by calling the service.

FIG. 6 is a schematic diagram of a visual design and an automated deployment framework of a CSAR-based model file according to the embodiment. As shown in FIG. 6, the framework includes two parts, one is integrated. The environment UIDE platform includes three components: development engineering tree, modeling tool and workflow designer. The second is the TOSCA server, which includes two components: deployment server and workflow server. among them,

Develop an engineering tree component that is set up to develop a model tree through a preset NFV scenario. The model tree defines the file development directory of TOSCA-metadata, Plans, etc. according to the file structure of the TOSCA model file.

The modeling tool component provides definition functions for nodes such as node type and relationship type, and selects and connects nodes through drag and drop of the visual interface to design a model file to be uploaded to the TOSCA server. Those skilled in the art can also set other ways to upload the model file to the TOSCA server, such as uploading the final model file through the workflow designer, or directly setting an upload interface to upload the final model file, and so on.

The workflow designer component provides the definition function of the Plan workflow. The model file is also designed by dragging and dropping the visual interface, selecting the process node, setting the sequence relationship, and so on.

Deploy server components that provide analytical model file content and service deployment capabilities, as well as information query and service invocation interfaces.

The workflow server component provides the parsing and running functions of the workflow file, and the workflow file can be triggered by the external interface.

Using UIDE for development has the following advantages: improving development efficiency through powerful functional components; reducing development difficulty through "what you see is what you get" visual development method; generating standard model files through standardized development processes. Through the association of UIDE with the TOSCA server, the developed model files can be directly deployed to the TOSCA server.

The method described in the present disclosure will be described below by way of an implementation case.

In the implementation case 1, the operator needs to create a virtual network function (VNF) model file. The operator creates a new NFV project in the UIDE graphical interface, and UIDE automatically generates the model file directory structure. The operator defines the VNF model in UIDE according to the actual situation of the VNF, and imports the VNF defined process information and the provided service implementation to complete the definition of the model file.

In the implementation case 2, the operator selects the edited NFV project in UIDE for automatic deployment. When the operator selects the NFV project and clicks the auto-deploy button, UIDE will call the upload model file interface of the TOSCA server and deploy the defined model file to the TOSCA server. The TOSCA server automatically parses and deploys the model files.

In the implementation case 3, the operator queries the definition information in the model file by calling the interface provided by the TOSCA server, and invokes the service provided in the model file to complete the instantiation and other operations of the VNF.

This embodiment provides a visual design device for a CSAR-based model file. Referring to FIG. 7, the device includes the following components.

The development project tree component 710 is configured to develop a model tree based on the preset NFV scenario on the visual interface of the integrated development environment UIDE platform, and create multiple directories of the CSAR-based model file.

A modeling tool component 720 is configured to create a node type and a node relationship type of the model file based on the directory and define a topology between the nodes.

The workflow designer 730 is configured to perform workflow scheduling on the node to obtain the CSAR-based model file.

Those skilled in the art can drag and drop on the visual interface through the modeling tool component 720, select and connect nodes, and design a topology.

Optionally, a workflow file can be designed by a workflow designer 730 by dragging and selecting a process node, setting a sequence relationship, and the like on the visual interface.

Optionally, the apparatus in this embodiment further includes: a deployment server component 740 and a workflow server component 750, as shown in FIG. 8.

The modeling tool component 720 is configured to upload the model file to a TOSCA server, The deployment server component 740 is triggered.

The deployment server component 740 is configured to enable the TOSCA server to complete parsing and service deployment of model file information under the trigger of the modeling tool component 720.

The workflow server component 750 is configured to trigger the TOSCA server to obtain a service that the model file can provide, and complete the orchestration of the model file task by calling the service.

The deployment server component 740 of the embodiment is configured to generate a temporary file by triggering the TOSCA server to decompress the model file, parse the temporary file, save the node attribute and the relationship attribute between the nodes, and save the deployment file of the node according to the node definition. The location information is obtained according to the node definition, and the implementation file corresponding to the service provided by the node is obtained, and the corresponding plug-in is invoked for deployment, and the corresponding relationship between the service provided by the node and the deployment information of the node service is saved.

The device described in this embodiment uses the integrated development environment UIDE for development, improves development efficiency through powerful functional components, and reduces development difficulty and simplifies development through "what you see is what you get" visual development method and standardized development process. The steps to develop and modify the model file.

The related content in this embodiment can be understood by referring to the device embodiment and the method embodiment, and details are not described herein again.

This embodiment uses the integrated development environment UIDE for development, improves development efficiency through powerful functional components, and reduces development difficulty and simplifies development of model files through "what you see is what you get" visual development method and standardized development process. And the steps of modification can effectively avoid the problem that the CSAR-based model file in the related technology does not have a suitable integrated development environment, and the development and modification of the standard model file is complicated.

The embodiment further provides a computer readable storage medium storing computer executable instructions for performing the above method.

FIG. 9 is a schematic diagram showing the hardware structure of a communication device according to the present embodiment. As shown in FIG. 9, the electronic device includes: one or more processors 810 and a memory 820. One processor 810 is taken as an example in FIG.

The electronic device may further include an input device 830 and an output device 840.

The processor 810, the memory 820, the input device 830, and the output device 840 in the electronic device may be connected by a bus or other means, as exemplified by a bus connection in FIG.

Input device 830 can receive input numeric or character information, and output device 840 can include a display device such as a display screen.

The memory 820 is a computer readable storage medium that can be used to store software programs, computer executable programs, and modules. The processor 810 executes a plurality of functional applications and data processing by executing software programs, instructions, and modules stored in the memory 820 to implement any of the above embodiments.

The memory 820 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the electronic device, and the like. In addition, the memory may include volatile memory such as random access memory (RAM), and may also include non-volatile memory such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.

Memory 820 can be a non-transitory computer storage medium or a transitory computer storage medium. The non-transitory computer storage medium, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 820 can optionally include memory remotely located relative to processor 810, which can be connected to the electronic device over a network. Examples of the above networks may include the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

Input device 830 can be used to receive input digital or character information and to generate key signal inputs related to user settings and function control of the electronic device. The output device 840 can include a display device such as a display screen.

The electronic device of this embodiment may further include communication means for transmitting and/or receiving information over the communication network.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by executing related hardware by a computer program, and the program can be stored in a non-transitory computer readable storage medium. The program, when executed, may include the flow of an embodiment of the method as described above, wherein the non-transitory computer readable storage medium may be a magnetic disk, an optical disk, a read only memory (ROM), or a random access memory (RAM). Wait.

Industrial applicability

The visual design method and device for the CSAR-based model file provided by the present disclosure are developed by using the development environment UIDE, and the development efficiency is improved through powerful functional components, and the "what is seen" "Developed" visual development method and standardized development process, reducing development difficulty, simplifying the development and modification of model files, effectively avoiding the CSAR-based model files in the related technology without a suitable integrated development environment, and standard model files The development and modification of more complex issues.

Claims

A visual design method for a model file based on a cloud service archive CSAR, comprising:

On the visual interface of the user interface development environment UIDE platform, the model tree is developed based on the preset network function virtualization NFV scenario, and multiple directories of the CSAR-based model file are created;

Creating a node type and a node relationship type of the model file based on the directory, and defining a topology between the nodes;

Workflow orchestration is performed on the node to obtain the model file.
The method of claim 1 further comprising:

The model file is uploaded to the cloud application based topology and business process specification TOSCA server, and the TOSCA server is triggered to complete the parsing and service deployment of the model file.
The method of claim 2 further comprising:

The TOSCA server is triggered to obtain a service that can be provided by the model file, and the parsing of the model file is completed by calling the service.
The method of claim 2, wherein the triggering the TOSCA server to complete parsing and service deployment of the model file comprises:

Triggering the TOSCA server to decompress the model file to generate a temporary file, parsing the temporary file, saving the node attribute and the relationship attribute between the nodes, saving the deployment file location information of the node according to the node definition, and acquiring the service provided by the node according to the node definition The corresponding implementation file, the corresponding plug-in is called for deployment, and the correspondence between the service provided by the node and the deployment information of the node service is saved.
The method according to any one of claims 1 to 4, wherein the NFV scenario development model tree is a development directory defined according to a file structure of the model file of the TOSCA.
A visual design device for model files based on CSAR, comprising:

Developing a project tree component, configured to virtualize the NFV scenario development model tree based on the preset network function on the visual interface of the user interface development environment UIDE platform, and create a plurality of directories of the CSAR-based model file;

a modeling tool component, configured to create a node type and a node relationship type of the model file based on the directory, and define a topology between the nodes;

A workflow designer is configured to perform workflow scheduling on the node to obtain the CSAR-based model file.
The apparatus of claim 6 further comprising: a deployment server component;

The modeling tool component is configured to upload the model file to a TOSCA server and trigger the deployment server component;

The deployment server component is configured to enable the TOSCA server to complete parsing and service deployment of the model file under the trigger of the modeling tool component.
The apparatus of claim 7 further comprising:

The workflow server component is configured to trigger the TOSCA server to obtain a service that the model file can provide, and complete the parsing of the model file by calling the service.
The apparatus according to claim 7, wherein the deployment server component is configured to trigger the TOSCA server to decompress the model file to generate a temporary file, parse the temporary file, save node attributes, and relationship attributes between nodes, according to The node defines the deployment file location information of the node, and obtains the implementation file corresponding to the service provided by the node according to the node definition, invokes the corresponding plug-in to deploy, and saves the correspondence between the service provided by the node and the deployment information of the node service.
The apparatus according to any one of claims 6-9, wherein the NFV scenario development model tree is a development directory defined according to a file structure of the model file of the TOSCA.
A computer readable storage medium storing computer executable instructions for performing the method of any of claims 1-5.