SO plugin support for VNFM ONAP Dublin Release

SO plug-in support for VNFM ONAP Dublin Release Architecture F 2 F meeting Montreal, 29 -31 st October, 2018 Ciaran Murphy, Ericsson, Amdocs, Verizon, other?

Introduction 2018 ONS ONAP Casablanca Arch F 2 F Focus on Scaling - Relation between scaling aspect and VF modules. - Resulted in addition to ETSI Specs Today: Introduce the proposal for Dublin Scope Nokia Adaptor Other 2

SO-ETSI ALIGNMENT SCENARIOS & USE CASES • Leverage ETSI standards for VNF LCM in SO • Build SO VNFM adaptor - Use SOL 003 APIs for VNFM communication - Support operations such as create, instantiate, scale, etc. • Enhance SO BPMN workflows & recipes - Pass VNF LCM requests to VNFM using adaptor • Scale out VNF/VF module based on policy - Enhance VNFM Adapter for VES event - Enhance Policy Framework for scaling decisions - Enhance SO workflows for VNF/VF Module Scale out 3

EXAMPLE COMPONENT ARCHITECTURE VID / UUI Create VNFM Adapter Resource workflow Terminate VNF Delete VNF Operate VNF Grant request Query VNF Resource Adapter Request DB Scale VNF SOL 003 Adapter (NBI) Adaptation SOL 003 Comm. Layer NBI Translation SDC Controller SDC BPMN Workflow Service Workflow VNFM Instantiate VNF API Handler CSAR SOL 001 (VNFD) SOL 002 SOL 003 SO API VNF (G/S)VNFM Register / Deregister … Catalog DB SO 4

VNFM Adapter – SVNFM SOL 003 Interfaces - Previously studied for Casablanca • Scale VNF - HTTP Method Type: POST - VNFM Endpoint: /vnf_instances/{vnf. Instance. Id}/scale - Request Payload: Scale. Request - Response Header: 202 accepted - Response Body: not applicable • Grant VNF Request - HTTP Method Type: POST - VNFM Endpoint: /grants - Request Payload: Grant. Request - Response Header: 201 success - Response Body: not applicable VNFM Adapter SOL Communication Layer • Instantiate VNF - HTTP Method Type: POST - VNFM Endpoint: /vnf_instances/{vnf. Instance. Id}/instantiate - Request Payload: Instantiate. VNFRequest - Response Header: 202 success - Response Body: not applicable access SOL Communication Layer • Create VNF - HTTP Method Type: POST - VNFM Endpoint: /vnf_instances/ - Request Payload: Create. Vnf. Request - Response Header: 201 success - Response Body: Vnf. Instance VNFM

VNFM Adapter – SVNFM SOL 003 Interfaces - Not previously studied for Casablanca • Terminating VNF - HTTP Method Type: POST - VNFM Endpoint: /vnf_instances/{vnf. Instance. Id}/terminate - Request Payload: Terminate. Vnf. Request - Response Header: 202 success - Response Body: not applicable • Delete VNF - HTTP Method Type: DELETE - VNFM Endpoint: /vnf_instances/{vnf. Instance. Id} - Request Payload: not applicable - Response Header: 204 success - Response Body: not applicable • Operate VNF - HTTP Method Type: POST - VNFM Endpoint: /vnf_instances/{vnf. Instance. Id}/operate - Request Payload: Operate. Vnf. Request - Response Header: 202 success - Response Body: not applicable - Query VNF Instances - HTTP Method Type: GET - VNFM Endpoint: /vnf_instnaces (for multiple VNFs), /vnf_instances/{vnf. Instance. Id} (for single VNF) - Request Payload: not applicable - Response Header: 200 success - Response Body: Vnf. Instance[] (for multiple VNFs), Vnf. Instance (for single VNF)

“Plugging In” a VNFM Into ONAP: Instantiate VNF Determine cloud instance for each VNF Resource (including this one) Source – Casablanca Proposal for VNFM Adaptor (Gil Bullard) SO 2 Decompose SO Internal: VNF Level Workflow SO Loop: Per VF Module Only this single “instantiate VNF” sub-flow shown 14 Configure VNF 13 SO or VNFM Adaptor responsible for retrieving the assignments from SDNC (organized by VF Module) and consolidating them (organizing by VM type). If necessary Stub VNFM Adaptor 12 9 SOL 003 (Create. Vnf, Instantiate. Vnf, Grant) 7 Assign VF Module Only those major ONAP components associated with this new option are represented. Inventory 8 Instantiate VNF 6 Assign VNF (Instantiate) OOF Request Homing 4 Spawn Resource-Level Sub-Flows Determine Resource needs (including this VNF) VNFM (Doesn’t necessarily care about VF Modules) SDNC 10 11 Deployment Data (SOL 002) VIM 5 • Locate ordered set of VF Modules associated with the requested instantiation level (from the transformed VNF TOSCA). • Determine if requested instantiation level is allowed. (If not, return Error) 3 SO Internal: Service Level Workflow Resource Data 1 Create Service Instance VNF A&AI Gen NFC Application 15 Data

“Plugging In” a VNFM Into ONAP: Scale Out by Level Increment – Option A Source – Casablanca Proposal for VNFM Adaptor (Gil Bullard) Given the assumption that a single VNF must always reside in a single cloud instance, any homing interactions with OOF as part of the SO Service Level workflow are not interesting. Thus, they are not shown for simplicity. SO 6 SO Internal: Scale Out By VF Module Workflow 8 Create VF Module 9 Extract scaling. Aspect and Aspect. Level from VF Module description 7 Assign VF Module 14 Stub 2 Scale Request (SOL 003) If necessary 15 Configure VNF 13 VNFM Adaptor 10 SOL 003 (scale. By. Aspect +1, Grant) Update Scale Level A&AI Gen NFC 11 VIM (Doesn’t necessarily care about VF Modules) Resource Data Only those major ONAP components associated with this new option are represented. 12 Deployment Scale Indicator Data (SOL 002) 1 VNF Scale Request Event 5 Policy Scale Request Event 4 Application 16 Data SDNC VNFM • Determine if Aspect y is “uniform” or “non” • Query A&AI for Current Aspect=y Scale Level • Determine VF Module type associated with Current Level +1 3 VES Scale Request DCAE Event P: Increment Aspect y by 1

“Plugging In” a VNFM Into ONAP: Scale Out to Level – Option A Source – Casablanca Proposal for VNFM Adaptor (Gil Bullard) SO 7 For Each VF Module (in proper sequence) Given the assumption that a single VNF must always reside in a single cloud instance, any homing interactions with OOF as part of the SO Service Level workflow are not interesting. Thus, they are not shown for simplicity. SO Internal: Scale Out By VF Module Workflow 9 Create VF Module 10 Extract scaling. Aspect and Aspect. Level from VF Module description 8 Assign VF Module 15 Stub 14 VNFM Adaptor 11 SOL 003 (scale. By. Aspect +1, Grant) SDNC Update Scale Level 2 Scale Request (SOL 003) 16 Configure VNF A&AI VNFM VIM 12 Resource Data (Doesn’t necessarily care about VF Modules) Only those major ONAP components associated with this new option are represented. 13 Deployment Scale Indicator Data (SOL 002) 1 VNF If necessary Gen NFC 6 • Determine if Aspect x is “uniform” or “non” • Query A&AI for Current Scale Level • Determine the ordered set of VF Module types that form delta between current and target Level Scale Request Event 5 Policy Scale Request Event 4 Application 17 Data 3 VES Scale Request DCAE Event Q: Scale Aspect x to Level 3

DUBLIN REQUIREMENTS • Build SO VNFM adaptor - Use SOL 003 APIs for VNFM communication - Support operations such as create, instantiate, scale, etc. • Enhance SO BPMN workflows & recipes - Pass VNF LCM requests to VNFM using adaptor • Policy based VNF/VF module scale out - Enhance VNFM Adapter for VES event - Enhance Policy Framework for scaling decisions - Enhance SO workflows for VNF/VF Module Scale out • Modelling and A&AI updates may be required - Some of this work may already be implemented 10

s

ONAP & ETSI ORCHESTRATION SCOPES 12