Achieving Alignment Between ONAP and ETSI MANO N

Achieving “Alignment” Between ONAP and ETSI MANO N IO Gil Bullard, AT&T March 28, 2018 D F A R F T R O S I D S S CU

Scope of ETSI Relative to Scope of ONAP Os-Ma-nfvo ONAP Functional Scope BSS/OSS NFV Service Catalog ETSI Functional Scope NFV Orchestrator (NFVO) VNF Catalog NFV Instances NFVI Resources Or-Vnfm EM Intersecting Scope VNF Ve-Vnfm-em VNF Manager (VNFM) Ve-Vnfm-vnf Vi-Vnfm Vn-Nf NFVI Nf-Vi Virtualised Infrastructure Manager (VIM) Or-Vi DRAFT FOR DISCUSSION ONAP and ETSI have differing scopes, with ETSI scope being a proper subset of ONAP scope

“Plugging In” a VNFM Into ONAP Automatic “Ack” for any “Grant” request originating in ONAP (instantiate, terminate, scale) Role of the VNFM Adaptor Determine and Route to Proper VNFM Instance Update A&AI Map ONAP Data for VNFM Use External VNFM Query VNF, LCN Notify Operate VNF/Custom Change VNF Flavor (Software) Heal VNF Modify VNF (Info, Connectivity) Grant Lifecycle Operation Instantiate/Scale/Terminate VNF Create/Delete VNF Identifier Load VNF CSAR into VNFM SOL 003 DRAFT FOR DISCUSSION VNFM Adaptor

“Plugging In” a VNFM Into ONAP SO Service Level and VNF Loop Level Workflows not shown for simplicity. Instantiate Example SO Internal: VNF Level Workflow Assign VNF SO sends to a VNF-level request to a sub-orchestration process to “create” the VNF. The “Routing/Proxy” function determines the endpoint. Instantiate VNF (with optional data attributes) In the internal ONAP case, it is an SO sub-flow that loops through the modules and calls Multi. VIM on a per-VF Module basis. SDNC The VF Module level looping would be moved down from the VNF Level Workflow to the sub-flow. Routing VNF-Level Proxy Gathers assignments and other input data and maps to VNFM format. VNF-Level VNFM can ignore the VF Module structure if it likes, because the network assignments passed to it would be organized by VM. Configure VNF (application level) VNFM Adaptor SOL 003 (Create. Vnf. Id, Instantiate, Grant) SO Internal: VF Mod Loop Level WF Loop through VF Modules VNFM Doesn’t necessarily care about VF Modules Deployment Data Per VF-Module for Scaling (data attributes map to HEAT ENV for example) Multi. Cloud VIM DRAFT FOR DISCUSSION SO VNF Gen NFC

“Plugging In” a VNFM Into ONAP Terminate Example DRAFT FOR DISCUSSION SO: VNF Level Workflow SO sends to a VNF-level request to a sub-orchestration process to “delete” the VNF. The “Routing/Proxy” function determines the endpoint. Deconfigure VNF (application level) (e. g. , remove VNF from usage pool) App. C Delete VNF Handles the “Grant” request (automatic “ack”) In the internal ONAP case, it is an SO sub-flow that loops through the modules and calls Multi. VIM on a per-VF Module basis. VNFM can ignore the VF Module structure if it likes, because the network assignments passed to it would be organized by VM. Routing Proxy VNF-Level VNFM Adaptor SOL 003 (Grant, Terminate, Delete. Vnf. Id) SO: VF Mod Loop Level WF Loop through VF Modules This is new Delete VF Module VNFM Doesn’t necessarily care about VF Modules Per Whatever …or… for Scaling Multi. VIM Release VNF Assignments VIM Deployment Data VNF SDNC

“Plugging In” a VNFM Into ONAP Scale to Level Example (Scale Out) v. VNF Scaling Level Definitions Level 1 = {1 “Base” VF Module, 1 “Add-On” VF Module} Level 2 = {1 “Base” VF Module, 2 “Add-On” VF Modules} Level 3 = {1 “Base” VF Module, 3 “Add-On” VF Modules} Etc… Assign VNF (Scale to Level=3) SO sends to a VNF-level request to a sub-orchestration process to “scale” the VNF. The “Routing/Proxy” function determines the endpoint. Scale VNF Gathers (Scale to Level = 3) (with delta VM-level assignments and other assignment attributes) In the internal ONAP case, it is an SO sub-flow that loops through the modules and calls Multi. VIM on a per-VF Module basis. Routing Proxy SOL 003 (Scale. To. Level, Grant) SO: VF Mod Loop Level WF Loop through delta VF Modules in VNF This is new VNFM can ignore the VF Module structure if it likes, because the network assignments passed to it are organized by VM. VNFM Adaptor SDNC Determines if any VF Modules need to be added/assigned. input data and maps to VNFM format. DRAFT FOR DISCUSSION SO: VNF Level Workflow Per VF-Module for Scaling (data attributes map to HEAT ENV for example) Multi. VIM Configure VNF (application level) VNFM Doesn’t necessarily care about VF Modules Per Whatever …or… for Scaling VIM Deployment Data VNF App. C

“Plugging In” a VNFM Into ONAP Config. Backup Upgrade. Software Application Healthcheck SO: Software Upgrade Change Management The sequence of orchestrated activities in SO Application. Health. Check, Config. Backup, Upgrade. Software, Config. Restore Routing Upgrade. Software Proxy Application. Health. Check, Config. Backup, Upgrade. Software, Config. Restore VNFM Adaptor SOL 003 (Change. Flavor, Get. Operation. Status, etc. ) Controller (SDNC or Gen NFC) VNFM VNF DRAFT FOR DISCUSSION LCM Software Upgrade Example Application Healthcheck

“Add-On VF Module” Service v. VNF 1 VMBn+1 0. . 8 An Example VNF KEY v. VNF VFCBn+1 VMBn Each v. VNF instance is comprised of 2 -18 VMB backend server VNFs. VMB 2 intdataplane_net_id VMB 1 VFCB 2 VFCB 1 “Base VF Module” VMA Assigned by SDNC, provided to NFVO Assigned by VNFM or Cloud Provider extdataplane_net_id VFCA Resource v. VNF extoam_net_id DRAFT FOR DISCUSSION The Load Balancer VFCA must be configured with the intdataplane IP Address of each backed server VFCBn. This configuration is delegated to the VNFM as part of its “deployment data” configuration. VFCBn 1

Distributed Orchestration Implementation Approach (Single ONAP Instance) VNF & Sub-VNF Orchestration Federation Example VNF-Level Flow X Model Driven Routing Function X X VF Module. Loop Level Flow Remote Proxies BBx Proxy encapsulates the application level interface in a remote API call. BBx-p 1 X The equivalent functionality of BBx could alternately be implemented in something other than SO. This implementation also requires a local proxy to make the remote call and perhaps to map the interface. When calling a VNFM, BBx-p 2 would adapt the “X” input to a (perhaps modified) SOL 003 API call (“Y”). X BBx-p 2 Y Orchestration Instance 2 (Optional) This subflow BBx implementation can execute either locally or remotely, though remote execution requires a local proxy to make the remote call. VF Module-Loop Level Flow BBx Fx Equivalent Sub-VNF Functionality Non-SO Implementation (e. g. , VNFM) DRAFT FOR DISCUSSION Orchestration Instance 1 The VNF-level flow calls the functional API “X” irrespective of Deployment Variation. The SDC Model drives a “routing function” which calls the specific implementation to be used per Resource type.

10 DRAFT FOR DISCUSSION ONAP Standard Flow, with Alternative Flow Shown Whereby a VNFM Plugged into SO

Service Level and VNF Assignments Level Processing Continued on next slide DRAFT FOR DISCUSSION 11

Standard ONAP Processing VNF Creation (with optional deployment parameter configuration) Continued from prior slide 12 DRAFT FOR DISCUSSION Continued on next slide

Alternative Flow with VNFM Plugged into SO (Part 1) Continued from prior slide 13 DRAFT FOR DISCUSSION Continued on next slide

Alternative Flow with VNFM Plugged into SO (Part 2) Continued from prior slide 14 DRAFT FOR DISCUSSION Continued on next slide

Return to Common Flow in ONAP for Application Configuration Continued from prior slide DRAFT FOR DISCUSSION 15