|
||
|
||
|
||
|
Date/Time Generated: |
11/21/2018 2:26:26 PM |
|
Author: |
Chris Rapposelli-Manzo |
EA Repository : CCPCloudEA|
CREATED WITH |
|
---|---|
Table of Contents
1 Overview, Scope, Dependencies2
2 Introduction3
2.1 Out of Scope (OoS) items (For this project & Release)3
2.2 Risks4
2.3 Working Team Contacts- Contributors5
3 Block Diagram6
3.1 Flow Designer Orchestration High Level Diagram6
4 Solution7
4.1 44884 Context Run Time Support of Workflows diagram8
4.2 Operations User8
4.3 AAI8
4.4 Portal9
4.5 SDC9
4.6 SDN-CP10
4.7 SO10
4.8 Scheduler11
4.9 VID12
4.10 Sequence Diagram: Run Time Support of User Designed Workflow diagram12
5 Requirements Run Time Support of Workflows15
5.1 44884 Requirements Run Time Support of Workflows15
5.2 44884 Requirements SDC Support of User Designed WFs15
6 Prioritized Activities/Building Blocks to be Developed22
6.1 Prioritized Activities/Building Blocks to be Developed22
7 Solution25
7.1 44911 Activity/BB Enhancements diagram25
7.2 Operations User26
7.3 SO Developer26
7.4 WF Designer27
7.5 SDC27
7.6 SO27
7.7 VID28
7.8 Deferred: CTH/UTH -Common/Universal Task Handler28
7.9 44911 Activity/BB Enhancements diagram28
8 Solution30
8.1 Enhance Activity Spec Restrictions diagram30
8.2 SO Developer31
8.3 SDC31
8.4 SO32
8.5 Correct bugs in Actions & BBs32
8.6 Enhance Activity Spec Restrictions diagram32
9 Requirements34
9.1 Enhance Activity Spec Restrictions34
10 Information Model35
10.1 Information Model35
10.1.1.1 Component Parameters35
11 Parameters and IST Testing Sections39
11.1 IST Testing Requirements DRAFT TO BE UPDATED39
11.1.1 IST Test Criteria and Preconditions39
11.1.2 IST Test Use Cases 39
11.1.3 IST Self-Serve Flow Test Cases41
11.1.4 Development and Test Environment Needs41
11.1.4.1 VNFs/Services Available and Required for Testing41
Dublin Workflow Designer
Name |
Workflow Designer |
Release |
ONAP - Dublin |
Contributors |
AT&T: SO, VID, SDC WF Independent Distribution |
Dependencies |
SDC and SO workflow development of Casablanca release |
|
Ansible/Chef/Puppet servers and scriptbooks for E2E operation |
|
|
Document Version
|
|
Document last updated : |
11/19/18 |
Document Latest Version: |
|
ONAP Wiki Document link: |
|
Document Revision History
Date |
Revision |
Description |
ATT UID |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The purpose of this document is to outline the scope, design and requirements for the Initiation of user designed workflows created using the SDC Workflow Designer and extension of the possible activities that can be used to design a workflow.
High level Key deliverables |
Develop functionality to support the execution of user designed workflows using the Self Serve SDC Workflow Designer Editor tool. |
# |
Description |
|
---|---|---|
Conflict avoidance other than pserver. |
||
Ability to provide Workflow Outputs to the user (although Amdocs may be developing this, it will not be implemented in SO or VID). |
||
Workflow functionality is only applicable to vNFs instantiated on an AIC and does not apply to Flexware(vNFs on uCPE). |
||
Development of new workflow activities (building blocks and actions) in the current release other than those specified in this document. |
||
An option at the VID interface during WF initiation for the user input "skip" a manual task (pause) activity. |
||
Prevent a user from closing a maintenance ticket in the ticketing system when it was opened by the scheduler. |
||
APPC vNF onboarding functionality moving to SDC. This is being handled by Configuration Management project. |
||
Versioning and updating of Activities (BBs and Actions) in SDC in production. In the production environment updating is strictly internal to SO and must not change the activity definition or inputs and outputs. |
||
Ability for SO to auto rollback a user created workflow to the start state of the workflow. |
||
Full Rainy Day Handling as designed for SO workflows will only be available at the existing functionality of building block level. |
||
Deprecation and deletion of workflows and activities (BBs). |
||
Full Versioning of workflows. Workflow modifications that change the WF definition must be newly created vs a new version. |
||
Ability to map vNF properties to an ECOMP Data Dictionary |
||
Use of a Task Handler for notification of a workflow in a "Paused for Manual Task State." |
||
Anything other than the creation of workflows with sequential building blocks and single path post decision points (i.e. follows a yes path or no path exclusively) is not supported e.g. execution of parallel paths in a workflow or concurrent Activities as stated in the customer requirement section (marked as deferred) is not supported. |
|
|
User experience improvements pertaining to previous projects are Out of scope unless otherwise noted. |
||
|
# |
Risk Description |
Mitigation Plan |
---|---|---|
1 |
Ansible/Chef Server not available for testing. |
|
2 |
Failure to fully deliver ONAP Flow Designer from the Casablanca Release |
|
3 |
Lack of resources to resolve open issues. |
Obtain full commitment from contributors. |
4 |
Lack of Funding or resources causing reduction of features developed and therefore E2E capability not delivered. |
Communication that E2E capability cannot be delivered. |
5 |
Lack of fully functional vNFs and corresponding Ansible/Chef/Puppet scripts available for testing |
vNF owners to provide vNFs with all required scriptbooks and ensure resources are available in the test environments. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Group |
Primary Contacts |
Secondary Contact |
ONAP Change Management Lead |
Ajay Mahimkar |
|
Overall Design |
Chris Rapposelli-Manzo - AT&T |
Steve Katz, Lauren Lewis- AT&T |
SO |
Steve Smokowski, Elena Kuleshov - AT&T |
Michael Zitella, Keith Dorking - AT&T |
SDC |
Srini Vellanki - Amdocs, Eden Rozin- AT&T |
Priyanshu Agarwal - Amdocs, Edith Ronen & Tali Fridman - AT&T |
VID |
Golan Harel - AT&T |
Eden Rozin - AT&T |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Backward Compatibility
Version 1.0, Author:CR2431
Created on 11/12/2018. Last modified 11/21/2018.
Flow Designer Orchestration High Level Diagram
Package in package '44884 Run Time Support of User Designed WorkFlow'
Solution
Version Phase 1.0 Proposed
mm7817 created on 11/12/2018. Last modified 11/12/2018
Analysis diagram in package 'Solution'
44884 Context Run Time Support of Workflows
Version 1
CR2431 created on 11/12/2018. Last modified 11/12/2018
44884 Context Run Time Support of Workflows
Actor Name: Operations User |
|
|
|
Stereotype: |
|
|
Complexity: |
Easy |
|
Notes: |
|
|
Last Updated: |
11/12/2018 2:17:10 PM |
Object Name: AAI |
|
|
|
Stereotype: |
«existing» |
|
Complexity: |
|
|
Notes: |
Active and Available Inventory
|
|
Last Updated: |
11/12/2018 3:10:52 PM |
Object Name: Portal |
|
|
|
Stereotype: |
«Push to ONAP» |
|
Complexity: |
|
|
Notes: |
Portal |
|
Last Updated: |
11/12/2018 4:27:13 PM |
Object Name: SDC |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
|
|
Notes: |
Service Design and Creation
|
|
Last Updated: |
11/12/2018 4:23:54 PM |
Object Name: SDN-CP |
|
|
|
Stereotype: |
«existing» |
|
Complexity: |
|
|
Notes: |
SDN Controller Platform
|
|
Last Updated: |
11/12/2018 4:27:48 PM |
Object Name: SO |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
Medium |
|
Notes: |
Service Orchestrator
|
|
Last Updated: |
11/12/2018 3:10:28 PM |
Object Name: Scheduler |
|
|
|
Stereotype: |
«Push to ONAP» |
|
Complexity: |
|
|
Notes: |
ECOMP Scheduler |
|
Last Updated: |
11/12/2018 4:26:11 PM |
Object Name: VID |
|
|
|
Stereotype: |
«enhanced» |
|
Complexity: |
|
|
Notes: |
Virtual Infrastructure Deployment (MOTS ID: 26377) (PRISM ID: 26377)
|
|
Last Updated: |
11/12/2018 3:19:45 PM |
Interaction diagram in package 'Interactions'
Sequence Diagram: Run Time Support of User Designed Workflow
Version 1
CR2431 created on 11/12/2018. Last modified 11/21/2018
Sequence Diagram: Run Time Support of User Designed Workflow
Version 1, Author:CR2431
Created on 11/12/2018. Last modified 11/14/2018.
44884 Requirements Run Time Support of Workflows
Version 1.0, Author:CR2431
Created on 11/12/2018. Last modified 11/20/2018.
44884 Requirements SDC Support of User Designed WFs
FunctionalRequirement Name: 44884 SO Enhance InPlace Activity to Update Inventory |
|
|
|
Notes: |
SO to enhance the InPlaceSWupdate Activity to update inventory (A&AI) with the new vNF model version ID. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:18:16 PM |
|
Last Updated: |
11/20/2018 3:31:44 PM |
Requirement Name: 44884- 21 SDC WF Editor Usability Improvements |
|
|
|
Notes: |
TBD based on prioritized input from users as they "play" with the WF Editor. Need to set up WF Designer in a stable lab for users. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/20/2018 11:16:47 AM |
|
Last Updated: |
11/20/2018 11:28:28 AM |
Requirement Name: 44884-12 SDC Indicate Expected User WF Inputs |
|
|
|
Notes: |
The SDC Editor must give the WF (hence SO and VID) a way to indicate what inputs are expected from the initiating user as input to the workflow. Those inputs are expected by the Activities used in the workflow. Any Activity inputs not provided by the user are expected to come from the other Activities used in the workflow by SO.
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/13/2018 4:52:14 PM |
|
Last Updated: |
11/13/2018 5:21:46 PM |
Requirement Name: 44884-8 SDC API Add WF Reference to vNF Model |
|
|
|
Notes: |
Develop an API to add a WF Reference to the vNF model indicating that the workflow was tested for the vNF Type/Version. Also include the users id and date. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/13/2018 5:23:24 PM |
|
Last Updated: |
11/13/2018 5:25:55 PM |
FunctionalRequirement Name: 44884-1 SO: Consume SDC "Get" Workflow APIs |
|
|
|
Notes: |
|
|
Keyword: |
MSO |
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:26 PM |
|
Last Updated: |
11/21/2018 1:37:03 PM |
FunctionalRequirement Name: 44884-2 VID: Get Available Workflows |
|
|
|
Notes: |
VID to obtain and display all available, user created workflows and SO Native workflows to the user for the selected vNF_Type/Version model using the new SO WF Get/Search API.
|
|
Keyword: |
VID |
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:23 PM |
|
Last Updated: |
11/13/2018 5:46:16 PM |
FunctionalRequirement Name: 44884-3 VID: Obtain WF Input Values |
|
|
|
Notes: |
Consume WF input parameters from the workflow metadata data
|
|
Keyword: |
VID |
|
Status: |
Proposed |
|
LOE: |
Moderate |
|
Created: |
11/12/2018 2:17:14 PM |
|
Last Updated: |
11/12/2018 4:54:36 PM |
Requirement Name: 44884-5 SO: Get Workflows & Meta Data API |
|
|
|
Notes: |
-SO to develop a new API that allows VID to obtain the list of available tested/certified workflows for the vNF Type/Version Selected and the MetaData for the user selected workflow.
|
|
Keyword: |
VID, A&AI |
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:28 PM |
|
Last Updated: |
11/13/2018 5:43:47 PM |
Requirement Name: 44884-6 VID-SO: Enhance Workflow Req. (Instantiation API) |
|
|
|
Notes: |
Existing Instantiation API presently utilized for the Workflow Request to be modified to be more flexible to handle complex data types requiring user entry. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:25 PM |
|
Last Updated: |
11/12/2018 4:48:25 PM |
Requirement Name: 44884-7 SDC: Workflow Distribution Notification |
|
|
|
Notes: |
Distribute the workflow (If workflow is made an independent artifact, otherwise, no change required.)
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:23 PM |
|
Last Updated: |
11/12/2018 4:31:25 PM |
Requirement Name: 44884-13 VID Display WF Name and Description |
|
|
|
Notes: |
-VID to display the Human Readable WF Name and WF description when displaying the list of available workflow names for the selected vNF type/Version model.
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:27 PM |
|
Last Updated: |
11/13/2018 5:47:14 PM |
Requirement Name: 44884-14 SDC: Certify WF-vNF Pair |
|
|
|
Notes: |
ASDC will follow the existing certification and governance processes used for Service to certify a workflow associate it with a vNF Type/Version. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:22 PM |
|
Last Updated: |
11/13/2018 5:17:23 PM |
Requirement Name: 44884-15 VID: Get WF Meta Data |
|
|
|
Notes: |
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Moderate |
|
Created: |
11/12/2018 2:17:20 PM |
|
Last Updated: |
11/12/2018 5:06:29 PM |
Requirement Name: 44884-16 SDC: Develop WF API Search & Get WFs Operation |
|
|
|
Notes: |
Develop new WF API to Enable an SDC WF Editor to obtain a list of all user designed workflows with the workflow description. The purpose of this is to allow the user to select and modify a workflow |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:17:20 PM |
|
Last Updated: |
11/12/2018 4:38:01 PM |
Requirement Name: 44884-18 SDC: Copy/Save Workflow |
|
|
|
Notes: |
Allow a user to copy an existing workflow, save it to a new name and subsequently modify it. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:17:13 PM |
|
Last Updated: |
11/12/2018 4:38:25 PM |
Requirement Name: 44884-19 SDC Store Workflow as Independent Artifact |
|
|
|
Notes: |
SDC workflow designer will store the workflow BPMN as independent artifacts and assign a UUID and invariant UUID. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:17:26 PM |
|
Last Updated: |
11/12/2018 4:36:23 PM |
Requirement Name: 44884-22 SDC Enhance Generic Artifact API |
|
|
|
Notes: |
Enhance Generic Artifact API to allow SO to extract the WF BPMN and associated Meta Data based on the workflow UUID. (Required if WF is made an independent artifact). |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:19 PM |
|
Last Updated: |
11/20/2018 11:27:41 AM |
Requirement Name: 44884-24 VID: Enhance Schedule WF API |
|
|
|
Notes: |
Dependent on Scheduler being pushed to ONAP by AT&T.
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:18 PM |
|
Last Updated: |
11/13/2018 5:39:06 PM |
Requirement Name: 44884-25 SDC Enhance TOSCA Parser |
|
|
|
Notes: |
Enhance vNF TOSCA Parser to extract workflow references from the vNF model. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:17:13 PM |
|
Last Updated: |
11/12/2018 4:32:43 PM |
Requirement Name: 44884-27 VID: UX Enhancement Requests |
|
|
|
Notes: |
Provide search and filtering tools that allow a user to pinpoint the list of vNF instances they want to perform an operation on.
|
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Easy |
|
Created: |
11/12/2018 2:17:25 PM |
|
Last Updated: |
11/12/2018 5:01:06 PM |
Version 1.0, Author:CR2431
Created on 11/12/2018. Last modified 11/12/2018.
Prioritized Activities/Building Blocks to be Developed
Building Block/Activities Name |
DublinPriority |
Description |
ChangeModelServiceInstanceBB |
4? |
Call SDN-C ChangeAssign |
Remove?? ModelAdminChangeUpdateBB |
? |
Update service-instance object in A&AI (update model info). |
AAIUpdateServiceModelVersion (New) |
1 |
CONCEPT: Need bulding block(s) to update the model (Service, Module, vNFC) version in A&AI due to an administrative change made to the model in ASDC such as a license renewal. MSO should perform a "diff" of all administrative "properties" of the model and only make the version update if those have changed. The base requirement is that use of the this building block needs to be restricted to non-functional model updates i.e. cannot be used due to a SW update. |
AssignVnfBB |
4 |
Update the Service model version ID in A&AI to match the ASDC service version due to an ASDC model administrative or external Service update |
UnassignVnfBB |
4 |
Create generic-vnf object in A&AI, orchestration-status = Inventoried |
ActivateVnfBB |
4 |
Call SDN-C Assign |
DeactivateVnfBB |
4 |
Update generic-vnf object in A&AI, orchestration-status = Assigned |
ChangeModelVnfBB |
1 |
Call SDN-C Unassign |
AAICheckVnfInMaintBB |
1 |
Delete generic-vnf object in A&AI |
SDNOVnfHealthCheckBB |
4/5? |
Call SDN-C Activate |
GenericVnfHealthCheckBB |
6 |
Update generic-vnf object in A&AI, orchestration-status = Active |
UpdatevNFModelVersion (New) |
1 |
Call SDN-C Deactivate |
AssignVfModuleBB |
4 |
Update generic-vnf object in A&AI, orchestration-status = Assigned |
UnassignVfModuleBB |
4 |
Call SDN-C ChangeAssign (change model) |
ActivateVfModuleBB |
4 |
Update genric-vnf object in A&AI |
DeactivateVfModuleBB |
4 |
Get generic-vnf object in-maintenance attribute |
ChangeModelVfModuleBB |
1 |
Send VNF health diagnostic request message to SDN-O |
CreateVfModuleBB |
4 |
|
DeleteVfModuleBB |
4 |
Update the Resource model version ID in A&AI to match the ASDC service version due to an ASDC model administrative or external Resource update |
HeatStackUpdateVfModuleBB |
3 |
Create vf-module object in A&AI, orchestration-status = Inventoried |
ConfigurationScaleOutBB |
6 |
Call SDN-C Assign |
Pause for Manual Task |
1 |
Update volume-group object in A&AI, orchestration-status = Assigned |
CreateVolumeGroupBB |
4 |
Call SDN-C Unassign |
DeleteVolumeGroupBB |
4 |
Delete vf-module object in A&AI |
Package in package '44911 -Activity/BB Enhancements'
Solution
Version Phase 1.0 Proposed
CR2431 created on 11/12/2018. Last modified 11/12/2018
Analysis diagram in package 'Solution'
44911 Activity/BB Enhancements
Version 1.0
CR2431 created on 11/12/2018. Last modified 11/14/2018
44911 Activity/BB Enhancements
Actor Name: Operations User |
|
|
|
Stereotype: |
|
|
Complexity: |
Easy |
|
Notes: |
|
|
Last Updated: |
11/12/2018 2:17:41 PM |
Actor Name: SO Developer |
|
|
|
Stereotype: |
|
|
Complexity: |
Easy |
|
Notes: |
|
|
Last Updated: |
11/14/2018 4:30:47 PM |
Actor Name: WF Designer |
|
|
|
Stereotype: |
|
|
Complexity: |
Easy |
|
Notes: |
|
|
Last Updated: |
11/12/2018 2:17:41 PM |
Object Name: SDC |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
|
|
Notes: |
Service Design and Creation
|
|
Last Updated: |
11/13/2018 5:57:48 PM |
Object Name: SO |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
Easy |
|
Notes: |
Service Orchestrator
|
|
Last Updated: |
11/14/2018 4:19:25 PM |
Object Name: VID |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
Easy |
|
Notes: |
Virtual Infrastructure Deployment
|
|
Last Updated: |
11/13/2018 5:55:36 PM |
Process Name: Deferred: CTH/UTH -Common/Universal Task Handler |
|
|
|
Stereotype: |
«process» |
|
Complexity: |
Easy |
|
Notes: |
Defer -Locate System where MSO can invoke an API to instruct a "team" to perform a required task. |
|
Last Updated: |
11/12/2018 2:17:43 PM |
Interaction diagram in package 'Interactions'
44911 Activity/BB Enhancements
Version 1
CR2431 created on 11/12/2018. Last modified 11/14/2018
44911 Activity/BB Enhancements
Package in package 'Enhance Activity Spec Restrictions'
Solution
Version Phase 1.0 Proposed
CR2431 created on 11/12/2018. Last modified 11/12/2018
Analysis diagram in package 'Solution'
Enhance Activity Spec Restrictions
Version 1
CR2431 created on 11/12/2018. Last modified 11/14/2018
Enhance Activity Spec Restrictions
Actor Name: SO Developer |
|
|
|
Stereotype: |
|
|
Complexity: |
Easy |
|
Notes: |
Impacts
|
|
Last Updated: |
11/14/2018 3:45:14 PM |
Object Name: SDC |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
Medium |
|
Notes: |
Service Design and Creation
|
|
Last Updated: |
11/14/2018 3:30:14 PM |
Object Name: SO |
|
|
|
Stereotype: |
«enhance» |
|
Complexity: |
Difficult |
|
Notes: |
Service Orchestrator
|
|
Last Updated: |
11/14/2018 3:37:19 PM |
Process Name: Correct bugs in Actions & BBs |
|
|
|
Stereotype: |
«process» |
|
Complexity: |
Easy |
|
Notes: |
Correct bugs and test Activity. |
|
Last Updated: |
11/14/2018 3:41:25 PM |
Interaction diagram in package 'Interactions'
Enhance Activity Spec Restrictions
Version 1
CR2431 created on 11/12/2018. Last modified 11/14/2018
Enhance Activity Spec Restrictions
Version 1, Author:CR2431
Created on 11/12/2018. Last modified 11/14/2018.
Enhance Activity Spec Restrictions
Requirement Name: SO Autopush Activities |
|
|
|
Notes: |
SO to AutoPush Activities to SDC using Activity Spec API upon SO startup. In the Test Env., SDC to allow for Activity overwrite. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/14/2018 4:00:44 PM |
|
Last Updated: |
11/21/2018 1:47:17 PM |
Requirement Name: SDC Activity Spec to allow Activity Replacement (Test Env. Only) |
|
|
|
Notes: |
SDC Activity Spec API, to allow SO to push modified activities to SDC. in the test environment. This is used solely for bug fixes. |
|
Keyword: |
|
|
Status: |
Proposed |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:18:10 PM |
|
Last Updated: |
11/21/2018 1:43:35 PM |
Requirement Name: OoS ASDC: ModifyActivity Operation |
|
|
|
Notes: |
Out of Scope |
|
Keyword: |
|
|
Status: |
Implemented |
|
LOE: |
Medium |
|
Created: |
11/12/2018 2:18:13 PM |
|
Last Updated: |
11/14/2018 4:05:32 PM |
Component 1 |
Component 2 |
Parameters |
VID |
SO |
Get list of all workflows with description. |
VID |
User |
Display all available workflows. Allow the user to choose a Workflow. |
VID |
SO |
VID to pass the workflow input parameter/value pairs to SO. |
SO |
VID |
Manual task status and activities to perform for manual task. |
SO |
SDC |
If independent WF is implemented: Upon receipt of a new workflow artifact notification (over DMaaP), SO extracts the workflow definition (New API) and BPMN artifact from SDC artifact catalog using the Generic Artifact API. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7.3.2 API and Interface Dependencies and Specifications
Author: Linh Nguyen, Chris Rapposelli-Manzo
ASDC
# |
Interfacing Applications |
API Name/Version |
Existing/Enhanced/New |
|
Impact Summary |
---|---|---|---|---|---|
1 |
SDC – SDC |
WF API(search WF operation) |
New |
|
SDC to develop a new API to allow the workflow designer to "search" the workflows for display to the user to choose a workflow to modify or to save as a new workflow to then modify. |
2 |
SDC -SO |
WF API (get WF meta data operation) |
New |
|
SDC to develop new API with an API-operation that allows SO to get the workflow meta data WF name, WF description, input/outputs with descriptions, reference to WF BPMN. |
3 |
SDC -DMaaP |
Distribution Notification |
Enhance |
|
SDC publishes new WF notification to DMaaP. |
VID
# |
Interfacing Applications |
API Name/Version |
Existing/Enhanced/New |
|
Impact Summary |
---|---|---|---|---|---|
1 |
VID-SDC |
Get vNF Model API |
Existing |
|
Enhance TOSCA parser and TOSCA model |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
VID-MSO |
Instantiationor New API |
Enhance or New |
|
Enhance existing Instantiation API or develop new API (Operation for WF Request) to support the WF parameters. Enhancement or new TBD during development. |
|
|
Instantiation or New API |
Enhance or New |
|
Enhance response to VID for Status: |
SO
# |
Interfacing Applications |
API Name/Version |
Existing/Enhanced/New |
|
Impact Summary |
---|---|---|---|---|---|
1 |
SDC-SO via DMaaP |
Notification |
Enhance |
|
Receive Distribution Artifact notification from DMaaP (published by SDC) |
2 |
SO-SDC |
Get WF API |
New |
|
SO obtains new WF Definition/MetaData from SDC, includes reference to BPMN artifact. |
|
SO-SDC |
Activity Spec API |
Exists |
|
|
3 |
SO-VID |
Instantiation or New API |
Enhance or New |
|
VID sends to SO the WF request package (WF name UUIDs inputs/values meta data). Enhance or new TBD during development. |
4 |
SO-VID |
Instantiation API or New |
Enhance |
|
Enhance response to VID for Status: |
Identify test criteria and preconditions for testing. Consider the Integrated Platform flows described earlier in Section 7 and any additional flows needed for backward compatibility testing. Requires inputs from IPSD Lead, Client Rep (e.g., from Greendyk, Medamana and/or Shannon org), ECOMP IST Tester (Josh Becker team), Client Test Teams (e.g., Jerry Leger team), D2 Integration Testing Rep (Deneen White team), and ECOMP Self-Serve Team (Stephanie Parlamas team).
Author: TG784d, CR2431
Project Success Criteria
Identify the test use cases for the proposed feature(s) identifying all the nodes that are involved in the system. Include the flows described in Section 6 and any additional flows needed for backward compatibility testing. Requires inputs from IPSD Lead, Client Rep (e.g., from Greendyk, Medamana and/or Shannon org), ECOMP IST Tester (Josh Becker team), Client Test Teams (e.g., Jerry Leger team), D2 Integration Testing Rep (Deneen White team), and ECOMP Self-Serve Team (Stephanie Parlamas team).
Author: CR2431
Feature Use Cases Design Workflows: Note: ensure all Activities are utilized in the workflows designed.
Feature Use Cases Execute Workflows:
Apply Testing use cases to at least one L4+ vNF that uses Chef and one that uses Ansible
Insert error conditions into all test cases.
Feature "Pause for Manual Step" Use Case
Identify the Self-Serve test use cases for the proposed feature(s) and for backward compatibility testing identifying all the nodes that are involved in the system. Include the flows described in Section 6 and any additional flows needed for backward compatibility Self-Serve flow testing. Requires inputs from IPSD Lead, Client Rep (e.g., from Greendyk, Medamana and/or Shannon org), ECOMP IST Tester (Josh Becker team), Client Test Teams (e.g., Jerry Leger team), D2 Integration Testing Rep (Deneen White team), and ECOMP Self-Serve Team (Stephanie Parlamas team).
Author: SK1692
TO BE PROVIDED
Identify the IST Test Environment requirements based on the Self-Serve test use cases for the new capabilities being delivered and for backward compatibility testing. Requires inputs from IPSD Lead, Client Rep (e.g., from Greendyk, Medamana and/or Shannon org), ECOMP IST Tester (Josh Becker team), Client Test Teams (e.g., Jerry Leger team), D2 Integration Testing Rep (Deneen White team), ECOMP Self-Serve Team (Stephanie Parlamas team), and TESP Rep (Jonathan Roll team/Isabella Szutkowski).
Author: Robin Kimble (RK2369)
Development Lab Needs:
Application |
Development Lab Resource Request |
Dev POC |
Notes |
|
||
SO |
No special needs |
|
|
|
||
VID |
No special needs |
|
|
|
|
|
APPC |
No special needs |
|
|
|
|
|
SDNC |
No info provided yet |
|
|
|
||
SDC |
MinimumVM with 2 VCPUs, 4 GB RAM & Storage of 20GB~. |
Srini Vellanki |
|
|
IST Environment Needs:
Author: CR2431
At least one Ansible, one Chef and NetConf L3 and L4-7 vNFs with all supported ansible/chef/Netconf script books must be available and active in the test environment. The vNFs must have an assigned Ansible/chef/Netconf server. Note: vNFs must be non-complex e.g. not like vProbes.
At least one NetConf Layer 3 vNF must be available and active in the test environment. The vNFs must have an assigned Netconf/Ansible/chef server. Note: vNFs must be non-complex e.g. not like vProbes.
At least one Netconf server, one Ansible server and one chef server loaded with the required script books must be available in the test environment.
Netconf/Ansible/Chef server assignment and retrieval features must be fully implemented for testing.
Identify example data to use for Self-Serve test use cases. Requires inputs from Client reps and Client test teams (e.g., Greendyk, Medamana).
Author: CR2431, DC2964
Required: User to create SDC designed workflows to test at least one Ansible and one Chef L4+ and one NetConf L3 vNFs each (3 vNFs total).
Ansible (to be confirmed) vNFs that can be used for testing:
vMMSC (Mobility L4+)
vCCF (VoIP L4+)
vRAR (VoIP L4+)
VCE - Requires ADIOD API consolidation completion and scripts available
SDWAN: VHNGW, VHNPortal
Tentative NetBond vFNAT, NetBond vRNAT
Chef vNFs that can be used for testing:
Tentative - vShaken (VoIP L4+, used to prevent Robo calls)
Tentative - vIRC (VoIP L4+)