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: We have reduced the functionality scope for Change Management in Beijing to execute a pre-defined workflow to carry out in-place software upgrade.

Other functionalities would be considered in subsequent ONAP releases.

Beijing Pair-wise testing status: [In-progress] SB-07 environment

Main blocking issue - VNF instantiation is not working with R2 - vCPE is not instantiated in SB-07 using SO.

https://jira.onap.org/browse/SO-618

Resolution: Kang Xi manually instantiated vG/vCPE in SB-07 but the instance is not seen in A&AI due to which SO cannot proceed with the in-place software upgrade workflow. However, SDN-C is able to now test the Ansible playbook execution on the VNF instance.

1) SDN-C To Ansible and Ansible to VNF instance:

Given the manual instantiation, Ruchira Agarwal is working on testing the Ansible playbook execution from SDN-C to Ansible server and Ansible Server to VNF instance (vG/vCPE).

IP address of vG is 10.12.5.85

2) SO to SDN-C:

Issue currently with DMAAP - publish working fine but subscribe not yielding expected results. Elena Kuleshov and Ruchira Agarwal are working on the issue.

3) VID to SO:

NF role is important to be set in order to have VID start the change workflow execution. Currently, it is not set as part of instantiation flow. A&AI to provide API to set the NF role - robot will use during instantiation.

Beijing Development Completed - Code Delivered

Image RemovedImage Added

Architecture Alignment:

...

Resources:

• Primary Contact Person: Ajay Mahimkar(AT&T) - mahimkar@research.att.com
• Emmanouil Mavrogiorgis (emaurog@researchemaurog@research.att.com)
• Ajay Mahimkar(AT&T)
• Giritharan Rana (AT&T)
• Jennifer Yates(AT&T)
• Zihui Ge (AT&T)
  
  

...

Giritharan Rana ( giri@research.att.com )

*Link to TSC approval: