5G & NETWORK TRANSFORMATION CONFERENCE An Introduction to ONAP Amar Kapadia
My Introduction Author of Understanding OPNFV, ONAP Demystified NFV specialist with background in OpenStack, Ceph, dataplane acceleration technologies Co-founder Aarna Networks, Inc. Previously at Mirantis, Seagate, Emulex, Philips, HP MS EE from University of California, Berkeley
Aarna and Argela Partnership Aarna Networks provides the only LF-approved ONAP training courses Aarna and Argela are strategic partners around ONAP
What is ONAP OPEN NETWORK AUTOMATION PLATFORM: Comprehensive platform for real-time, policy-driven orchestration and automation of physical and virtual network functions. 100% open source, part of Linux Foundation. Born Mar/2017
Who is Behind ONAP AT&T ECOMP + Linux Foundation Open-O merger in Q2 2017 100% open source, part of Linux Foundation Operators represent 60+% of mobile users worldwide
Why ONAP? High levels of agility for 5G and MEC will require a sophisticated automation tool such as ONAP
ONAP in the NFV Architecture Context OSS / BSS / E- Services / Big Data EMSs NFVO VNFs NFVI Software Virtual compute, storage, networking, dataplane acceleration VNFMs/ PNFMs Global DC SDN Controller NFVI Hardware servers, storage, switches VIM Modified ETSI NFV Architecture
ONAP Scope Design Framework Runtime Framework ETSI NFVO, VNFM, PNFM Monitoring and Service Assurance
External modules & artifacts (e.g. VNF packages, analytic apps, svnfm, EMS) ONAP & Other Software Systems OSS/BSS/Big Data/E-Services ONAP NFVI/VIM/SDN Controller * ONAP supports svnfm, but eliminates external policy engine or EMS Fault, configuration, accounting, performance, security
ONAP Architectural Principles Model Driven Cloud Native DevOps Automated without hardcoding Built for the cloud and to manage cloud native VNFs Built using CI/CD manage VNFs using CI/CD
Additional Architectural Considerations Pluggable modules Centralized design studio Policy driven Real-time Self-service (users, operators) Multi-tenant Secure Closed loop (and open loop) automation Alignment with standards e.g. ETSI, MEF, TMForum
A Day in the Life of ONAP VNF Vendor 1 Vendor provided VNF (cloud-hosted, optimized or native) 2 Vendor packages VNF as per ONAP requirements; can use VNF SDK PNFs need to be packaged as well Design 3 4 Design/test teams onboard VNFs Designers create products, services, recipes Run- Time 5 BSS system triggers service deployment 6 Service lifecycle management Closed Loop 7 Constant monitoring & service assurance
VNF SDK Modeling Integration VNF Validation VNF Requirements Benchmark Documentation ONAP Beijing Release Portal/API CLI Use Case UI External Data Movement & APIs Portal Framework Supporting Projects Design-time Run-time SDC OA&M Dashboard (VID) SO DCAE Holmes Policy A&AI MSB/DMaaP CLAMP ONAP Operations Manager Common Service OF Logging AAF CCSDK MUSIC Multi Cloud Controllers SDN-C APP-C VF-C
ONAP Design Time Environment Operations Onboard VNFs Create Services Create Recipes Onboard Functions - Create license model - Onboard VNF - Test VNF - Store VNF in catalog - Create service/product - Test service - Store in catalog - Approve - Distribute - Create policies - Create workflows - Create closed loop flows - Create change mgmt - Onboard collectors - Onboard analytics apps - Onboard microservices - Onboard datastores if high_load scale_out backup: quiesce snapshot restart service geo-repl snapshot Service Design & Creation (SDC) & Closed Loop Automation Management Platform (CLAMP) : Graphical, Guided, Extensible, Role-based
ONAP Run Time Environment Service LCM Monitoring & Service Assurance API or GUI API or GUI Service Orchestrator (SO): TOSCA /Heat descriptors for network service + config parameters + workflow Data Collection Analytics and Events (DCAE) (Collectors, data stores, microservices, analytic apps) Active & Available Inventory (A&AI) graph from subscriber network service VNFs virtual infrastructure physical infrastructure SDN Controller (SDN-C) APP-C or VF-C gvnfm/svnfm interface MultiCloud DCAE controller (Cloudify)
ONAP VNF Onboarding Projects VNF Requirements VNF SDK VNF Validation Document used by VNF designers to create the VNF and associated artifacts (VNF-D, Yang models, CI/CD tests, VES etc.) Tool used by VNF designers to create the TOSCA based VNF package Tool that validates a VNF and provides an ONAP compatible label APP-C (Heat), VF- C (TOSCA)?
ONAP Beijing Release 2nd Release 286 452 Authors June 2018 9.6K 14.8K Commits * From onap.biterg.io 11/27/17 to 5/16/18
What s New in Beijing? NB Interface alignment with standards S3P Stability Security Scalability Performance Change Management Scaling One case: in-place update One case: manual trigger DCAE containerized for OOM New initiatives: MUSIC, benchmarking, CDT
Use Cases in Beijing Release vfw: Virtual Firewall/ vdns: Virtual DNS vcpe: Virtual Customer Premise Equipment VoLTE: Voice over LTE
vfw Simple virtual firewall demo Entire lifecycle through 40+ steps: VNF Onboarding Service, policy creation Service, policy distribution Service deployment Traffic generation Closed loop automation Useful to see how ONAP works and perform validation on a deployment
vcpe Residential gateway split between Bridged Residential Gateway (on-prem) and virtual Gateway (cloud-based) All open source VNFs Several optimized for FD.io/VPP Use gvnfm Six network services created Steps: ESR, VNF onboarding, hardware platform awareness (HPA) policies, service creation, instantiation, monitoring, closed-loop automation, in-place upgrade, termination
VoLTE vepc + vims complex service Proprietary VNFs with svnfms Steps: vepc: ZTE/Huawei vims: Huawei/Nokia svnfm/ems: Huawei/ZTE/Nokia PE: Huawei (not virtualized) DC/WAN/SPTN controller: ZTE VNF onboarding, vepc/vims service design, underlay/overlay VPN template import, VoLTE service design, closedloop automation (with Holmes), manually triggered scaling, termination; via Use case UI
ONAP Getting Involved Developer Start with ONAP wiki Join the community (free) Read about project(s) Join mailing list, calls Read about developing on ONAP, download tools Or Read about integrating with ONAP Attend events User Start with ONAP wiki Join the community (free) Read about project(s) Join mailing list, calls Deploy ONAP Try vfw, vcpe use cases Deploy PoC with all artifacts and interfaces developed Attend events
Open Source Alternatives to ONAP Open Source MANO (OSM) Under ETSI NFVO/VNFM/Design focus Extensible via ecosystem S/W 5th release 5G, MEC focus Led by Telefonica OpenBaton ETSI compliant MANO SDKs for integrating with VIM, svnfms Extensible/customizable Powered by Fraunhofer Fokus Part of 5G Berlin
Joint Argela-Aarna ONAP Training Private ONAP training can be scheduled any time at your site Public ONAP training planned for Q1 19 at Argela 5G Center of Excellence in Ankara
Questions? akapadia@aarnanetworks.com @akapadia_usa