Verizons views on ONAP Architecture Evolution Fernando Oliveira

Verizon’s views on ONAP Architecture Evolution Fernando Oliveira ( Fred ) Viswanath Kumar Skand Priya ( Viswa )

ETSI Standards Alignment/Compliance Legacy OSS SOL 004 CSAR SOL 001 VNF-D & NS-D Onboarding SOL 001 NS-D SOL 005 SDC NFVO SOL 001 NS-D SOL 003 & SOL 001 VNF-D VNFM VNF SOL 002 VNF VNF App-C / GNF-C SO SOL 005 Legacy NFV-O SOL 003 VNFM SOL 002 VNF VNF VNF SOL 002

Flexibility - ONAP only & ONAP + Legacy OSS SOL 005 SO GNF-C SO VF-C SO SOL 005 SOL 003 S-VNFMs VNF VNF VNF Legacy NFV-O SO + g. NF SOL 003 S-VNFM VNF VNF VNF SOL 003 S-VNFMs VNF VNF VNF

Flexibility – Drop & Replace / Swap – Multi Vendor ONAP Components ( products ) SDC SO OOM Policy VF-C DCAE GNF-C AAI OOF ü Stateless APIs ü No ONAP Specific Assumptions ü No Shared states between ONAP Components ü Standard APIs with Vendor Specific extensions promoting innovation ü Dependency & Versioning clearly specified ü Clear separation of External & Internal DM ü Dynamic Registration

General Expectations ü Standards compliant on-boarding / orchestration interfaces - SOL 004 & 001 ( Onboarding and pass to VNFM) - SOL 003 & 002 (VNFM) - SOL 005 (OSS->ONAP & ONAP->NFVO) - VNF Certification ü Declarative model based orchestration - TOSCA for NSD/VNFD - YANG/Netconf/VES - Custom workflows support ü Fine grained RBAC for deployment dashboard - Custom Roles & ABAC ü Ability to deploy Geo-Redundant Highly available Network services - GR part of network design ü Geo-Redundant Highly available ONAP deployment - Shared runtime Catalogues ü Vendor Supported ONAP Distribution E. g. Red Hat / Canonical / Marantis