Page History

...

• This project provides users with the ability to design workflows based on a suite of existing capabilities exposed by other ONAP components. For example, a user can make calls to a controller to execute actions, to A&AI to get inventory status, and existing orchestration flows, and combine these calls to achieve a higher level orchestration function. We envision that this design capability will get integrated with the SD&C environment.
• This project provides a capability to deploy (and undeploy) and upgrade the designed workflows to an execution environment (e.g., the service orchestrator). This assumes that the execution environment provides APIs to perform these functions.
• This project provides runtime management (start, pause, resume, stop, rollback) and monitoring of the workflows.  This project provides a portal for a user to come in and manually control these workflows or monitor them. Again we assume that the execution environment provides APIs to perform these functions. We also assume that other ONAP components (e.g., Policy) can trigger one of these workflows as part of a control loop action.
• This project provides capabilities for scheduling workflows. The schedule could range across a subset of the instances of an NF, across instances of multiple NFs or combinations therein.
• This project provides capabilities for selecting the type and instances of the NFs that need to be associated with the workflows (as well as for scheduling).
• The project will provide capabilities for tracking the history of workflows that have been executed.
• This project will document the best practices for End-to-End workflow design.

Architecture Alignment:

• How does this project fit into the rest of the ONAP Architecture?
Please Include architecture diagram if possible
• • The figures below show sample E2E flows that will be executed as part of NF Change. 
• Image Added
  
  
• Image Added
• Image Added
• 
  
  • What other ONAP projects does this project depend on?
• SD&C
• Portal
• Service Orchestrator
• Controllers
• A&AI
• Policy
• DCAE
• Optimization Framework

• How does this align with external standards/specifications?
• APIs/Interfaces
• Information/data models
• Are there dependencies with other open source projects?
• APIs/Interfaces
• Integration Testing
• etc.

...

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: