Page Comparison

...

• 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. SDC will be used for designing the workflows.
• 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 or track the history of workflows that have been executed. 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. For complex scheduling use cases we foresee the use of SNIRO Optimization Framework to be used as a home for specific scheduling optimization micro-services.
• 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).
• This project will document the best practices for End-to-End workflow design.

Beijing Release:

Architecture Alignment:

• How does this project fit into the rest of the ONAP Architecture?
• The figures below show sample E2E flows that will be executed as part of NF Change. 
• 
  
  
• 
• 

...