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..
- Change Management - will be our focus for R2
- 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
- Service Assurance - Analysis in parallel to clarify architecture and requirements. Is it topology design?
- 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
There is no need for Designer to define workflow for VNF and Service MACD operations.
- TBD
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Design Workflows | Designer should be able to define workflows for various VNF operations | Must Have | |
| 2 | Workflow Changes | Operations 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 |
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|