ONAP Dublin Workflow Designer Requirements 11072018 ATT CR
ONAP Dublin - Workflow Designer Requirements 11/07/2018 AT&T CR 2431 Rapposelli-Manzo
Workflow Designer Problem Statement: 1 Each workflow requires SO development (sometimes per VNF) 2 Have to wait on release cycles for any requested workflow change Design in SDC Tech Ops Automate Overall Goal: Workflows & VNF Operations Ability to use SDC to design workflows for SO execution based on available Activities – e. g. VNF Image/Software Upgrade, VNF Configuration Upgrade & VNF Scaling, Instantiation. Casablanca: Ability to use SDC to design workflows for SO execution – Use case: simple In Place SW Upgrade WF using 7 Activities. Dublin: Ability to use VID to initiate workflow execution & expand available Activities for Workflow creation – e. g. VNF Image/Software Upgrade, VNF Configuration Upgrade. VID, SO Deploy VNF, Operations & Workflow Initiate VNF Operations/ Workflow Reusable building blocks(Activities) Execute Workflow
Workflow Designer – Generic Workflow 1. Activity is Developed in SO & Activity. Spec is On-boarded to Catalog 2. Workflow Designed in SDC using Workflow Editor and Independent BPMN Artifact is generated SDC Activity. Spec Catalog (examples) • • • • Create. VNF Delete. VNF Configure. VNF Stop. VNF Start. VNF Lock. VNF Unlock. VNF Stop. Traffic Drain. Traffic Resume. Traffic Health. Check create. Snapshot copy. Snapshot Create. Ticket Manual Step 3. Distribute BPMN Firewall VNF Operations Instantiate Upgrade 4. Deploy Workflows 5. Workflow Associated to VNF Operations 6. Distribute v. NF Model SDC 7. Deploy VNF, Operations 8. Initiate VNF Operation 9. Execute Workflow Associated to Operation SO VID SO
SDC Requirements • Provide an easy and seamless way for workflow initiators to attest that a workflow has been tested for the v. NF the initiator wants to execute the workflow on. The workflow name, UUID, Invariant UUID, and user ID will be stored in ASDC. . • Store Workflow as an independent artifact in Camunda BPMN format with a UUID, invariant UUID, WF description. • Ability to distribute new workflow: - Develop Artifact notification to SO (over DMaa. P). - Develop WF API with get meta data operation to obtain the Workflow meta data which includes a reference to the BPMN. - Develop Generic artifact API to obtain the BPMN based on the BPMN reference in the WF API • Develop a copy, rename, save workflow operation. (Workaround is to export WF/rename/import). • SDC to create a new “WF API” for the WF Editor with two operations: - Get the list of available workflows used by the WF designer - Get the WF meta data used by MSO • Align WF Editor GUI to GUI standards 4
SO Requirements • Develop API for VID to obtain the list of all available and certified Workflows (SO Native and User Designed) for the user selected v. NF Type and the Meta Data for the Selected for Workflow. • Enhance to VID-SO Instantiation API to be more flexible to consume workflow parameters. • Recognition of new Distribution Notification for Workflow Distribution. • SO consumption of SDC WF API "Get Meta. Data" to obtain the WF definition/Metadata (WF name, WF Description, UUIDs, reference to the WF BPMN artifact) • The minimum requirement for Workflow errors is to execute Rainy Day Handling where the default policy is set to terminate the workflow and issue a trouble ticket. The target solution would be for Rainy Day Handling to stop the workflow and allow the user to respond to an error and have a choice to skip/continue or abort. This will be done when possible. • MSO to execute the activities (BBs) BAU. • MSO to include the NF_Role in status responses to VID. • For change operations that include a new Service and v. NF Model IDs, MSO must instruct the controller to make the appropriate updates in A&AI immediately after the change operation is successful. (Note: all SW update activities require inventory update). • All Activities to be enhanced to use GR-API. • Make all Activities required to create the following workflows Workflow Designer ready: - In. Place. SWUpdate Config Update Heatstack Update at the v. NF and v. FModule levels Delete and Build SW Update Build and Replace SW Update (stretch goal) • Make a “Pause for Manual Task” Activity workflow designer ready. 5
VID Requirements • Provide flexible v. NF search capabilities that allow the user to easily and quickly select the v. NFs they want to execute a WF operation on. • Provide security to prevent unauthorized users from initiating a WF operation on v. NFs outside of their authorized area. • Extract the list of available workflows by consuming and using a WF Search API provided by SO. SO will act as the Run time catalog of workflows. • Available workflows will be listed by unique operation name. • All workflows shall be displayed for the selected v. NF type to the user. Tested and MSO Native WFs will be marked as such. • Allow user to attest to a workflow being tested for the selected v. NF Type/Version and pass that information (WF name, UUID, v. NFType & Model Version, User’s ID) to SDC. • Ingest new API that allows VID to obtain workflow meta data (UUID, invariant UUID, WF input/output parameters). Workflow Meta Data from MSO. • Prompt user for workflow input parameters required by the "Workflow". • Support both simple and complex input data types (nested arrays). • Accept user input for parameters and package in the workflow request. 6
- Slides: 6