ONAP E2E Flow `

vCPE Service vBNG vHGW vRouter vCPE Servce

E2E Steps in Lifecycle Management of VNF Onboarding (involves Portal and SDC) Design Runtime (most ONAP components) Vendor provided VNFs & VNF artifacts Analytics processing VNF events Service Agnostic Control loop templates design Service Design steps including: Instantiation Performance and Fault Management (Control Loops) Change Management Runtime steps:

vBNG vHGW vRouter vCPE Servce Step 1: Onboarding Using the VNF-SDK: - get images, Heat files, various models from vendors Onboard VNFs VNF-SDK

Step 2: Service Design and Distribution vBNG vHGW vRouter vCPE Servce vCPE Service Design vCPE Analytics Design vCPE Policy Creation SDC Service Design Policy Creation Analytic Application Design Design Studio Policy Editor Analytics SDK SO A&AI Resource Onboarding Policy Rules KPIs, Alarms, Operators, etc. Certification Studio Conflict Identification Catalog Links to Artifacts Policy Storage Analytic Applications Library DMaaP ---- ---- ---- ---- ---- ---- ---- ---- Artifact distribution Y= Xi / n Controllers Product Process Library DCAE Controllers Service Resource Recipes & Eng. Rules Templates Controllers Recipe/Engineering Rules & Policy Distribution (metadata artifacts/recipes) Not a one time activity – happens whenever the service is modified/enhanced

vBNG vHGW vRouter vCPE Servce Step 3: Customer Order External to ONAP

Step 4.1: Instantiation and Chaining vBNG vHGW vRouter vCPE Servce vCPE orchestration request From SDC A&AI 1 SO Create Objects From SDC vCPE BPELs Inventory 7 Update Objects 4 0.5 Homing/placement Function Heat Instantiation Request vCPE Resources assignments 2 SDNC DCAE From SDC From SDC 3 Update/create Objects MSO BPEL recipe: verify request is new (query A&AI), create vCE, connect to vPE, associate with <customer>, … SND-C assigns the resources required for a regular VPN, and create initial vCE objects and network objects in the inventory, including assigned vlans, network and vCE names, … MSO then gets the newly created information from SDN-C, installs the parameters required by PO into the heat templates and sends them to PO PO instantiates the VMs via standard Openstack mechanisms, including loading the images, and assigning the compute, memory and disk resources; then goes to SDN-Local (Contrail) to assign the vlans and create the network connectivity PO (RO) then updates A&AI with all the assignments and the status, and returns to MSO a stack-id OpenStack 5 6 Create virtual networks vCE VMs vHGW vBNG vRouter Create virtual machines Infrastructure

Step 4.2: Configuration and Activation vBNG vHGW vRouter vCPE Servce Service is active 17 A&AI SO Inventory update 11 From SDC From SDC Inventory Inventory read 12 vCPE is up and running 8 13 15 Event System 16 Configure resources vCPE is monitored Controller 5 DCAE From SDC From SDC Inventory update 10 9 VNFs configuration & control Includes the telemetry collection and the event generation by DCAE when the threshold is crossed MSO subscribes to this event and when received activates a different recipe of this service – the one that initiates, configures, connects, and activates the VNFx on the VPN vCE VMs vHGW vBNG vRouter 14 Local telemetry collection & Analysis From SDC Local DCAE

Control Loop Flow (Design time – Fault Management) 3 SO SDC SDC : Control Loop Designer/cockpit Control Loop Dashboard 1 Onboard VNF (vBNG) create service 9 Query template services, VNFs 4 5 User configures template Distribute Service Update Create CL template CL Runtime statistics Reporting, etc. 2 Get alarm files 8 User can control Start/stop/update 7 11 Advance change toward distribution 6 Create and activate Configuration policies, Operation policies 9 Upload Blueprint and Locations File as artifacts A&AI Distribute Service Update Policy Engine 9 Distribute CL blueprint (Tosca) DCAE Inventory Distribution Client 10 DCAE Service Type for CL is pushed to Inventory DCAE

Fault Management Microservice Control Loop Runtime CL Runtime Cockpit & Dashboard ONAP Portal A&AI trigger Or MSO Dispatcher API Inventory API DCAE Orchestrator Inventory DMaaP Controller DCAE Controller Orchestration Policy API DCAE Central Policy Engine APIs DMaaP Local CL Flow Execution Fault Management Microservice Event Normalizer Docker Server CDAP Cluster A&AI Microservice SNMP Trap Collector Restart VM Docker Server Docker Server NTC DCAE Edge FTL OpenStack App-C Source VF: vBNG Restart VM 10

CM Process Design CM Building Blocks in Catalog CM Designer DCAE A&AI SDC (catalog) CM Building Blocks in Catalog DCAE micro-services, A&AI APIs, Controller capabilities (e.g., health check APIs), scripts/workflows. Onboard component capabilities DCAE A&AI Controllers CM Designer Modular composition to stitch different building blocks into a workflow (using a visual designer) e.g., In-place software upgrade, Build and Replace. SDC (CM Designer) SDC (CM catalog)

Change Management Scheduling & Conflict Avoidance ONAP Portal CM Schedule Optimizer Create a schedule/plan for rolling out a change such that we minimize service disruption during the change within the specific completion time Dependency modeling Conflict scoping Service Impact scoping Execution ordering CM Portal 5 1 7 6 CM schedule optimizer 4 Orchestrator 3 3 2 3 Tracking/ Notification OSS Policy DCAE A&AI 1 – Send workflow, VNF list and time range to schedule optimizer 2 – Request constraints for scheduling 3 – Request data for optimal schedule 4 – Identify CM schedule 5 – Provide the schedule for approval 6 – Once approved, send the schedule to Change tracking/notification OSS. 7 – Push the approved change schedule for execution

Change Execution Orchestration Execution: ONAP Portal CM Portal ** Orchestration Execution: Execute the orchestration building blocks and use RESTAPIs to interface controller for software upgrade, or A&AI for updates to the CM flag ONAP Portal: Track status of CM workflow execution – success/failure status of each building block Intercept CM workflow execution – pause/resume functions, and ability to inject new steps in the workflow Pre / Post Analytics: Performance analytics – pre/post performance comparisons, go/no-go decisions for network- wide deployment 2b 1 Orchestration 2 Policy 5 6 4 7 8 3 7b A&AI DCAE Controller 1 – Start execution based on schedule 2 – Conflict check 2b – Check roll-out status 3 – (Pre) health check 4 – Update CM flag 5 – VNF upgrade 6 – (Post) health check 7 – Pre/post impact analysis 7b – Fallback (possibly) 8 – Update CM flag ** – Status tracking and pause/resume execution at any/all times