Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Target releaseR2
Epic
Document status
DRAFT
Document owner

Srinivasa Vellanki

Designer
Developers
QA

Goals

  • Enable Designers(Service Designer, VNF Owner or TechOps) to be able to specify the workflow for supporting VNF change management scenarios

Background and strategic fit

Currently Operation processes(workflows) are being developed by MSO developers, forcing Operations Team to wait for ECOMP software release cycles for any changes in the processes.

To allow for better agility the ask is to enable Designers to be able to specify the Service or VNF Operation processes(workflows).

Strategically Flow Designer is considered to be used in 3 major domain areas if not more..

  1. Change Management - will be our focus for R2
    1. There is little standardization in how to perform these operations across various Vendor VNFs, resulting in need of defining Workflow for VNF Change Management Operations
  2. Service Assurance - Analysis in parallel to clarify architecture and requirements. Is it topology design?
  3. Service Fulfillment - Workflows of SO can be generated from TOSCA Models of service and VNF i.e. declarative topology model driven workflows built by development as part of core platform capability and hence no needs in designer are anticipated at this time

Assumptions

  1. There is no need for Designer to define workflow for VNF and Service MACD operations.

  2. TBD

Requirements

#TitleUser StoryImportanceNotes
1Design WorkflowsDesigner should be able to define workflows for various VNF operationsMust Have
2Workflow ChangesOperations should be able to introduce new workflows or changes to existing workflows based on existing ActivitySpecs with-out any dependencies on ONAP releases Must Have  
3Manage ActivitySpecs SO or other ONAP orchestration components having workflows defined by Designer need to be able to manage(register) their ActivitySpecs so that the ActivitySpec are available for designer to use in workflows.Must Have  

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  1. ActivitySpec versioning is OOS for R2


  • No labels