Best of both worlds Drivers Latency Physics Bandwidth Economics Context Proximity Privacy Legal Geo Distributed Computing trend 2 WAN Public Private Cloud m S4 m S4 m S3 m S2 m ID: 1043658
Download Presentation The PPT/PDF document "@twitter ONAP and Cloud Native" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. @twitterONAP and Cloud NativeBest of both worlds
2. DriversLatency/ PhysicsBandwidth/ EconomicsContext/ ProximityPrivacy/ LegalGeo Distributed Computing trend2WANPublic/ Private CloudmS4mS4mS3mS2mS1mS1Cloud PlatformNetwork (LAN/ WAN)Edge 1mS1mS2mS1EdgePlatformWANPublic/ Private CloudmS4mS3mS4Cloud PlatformExternal SystemEdge nmS1mS2mS1EdgePlatformWANCatherine to give introduction
3. Big Picture - service orchestration3Service OrchestratorEdge Platform (K8S based)MachinesK8s Site1K8s Site NSite1 Cluster1Site1 Cluster MEdge Platform (Openstack based)MachinesSiteSiteOSS/BSSDeployed CNFs/VNFsWhy do you need service orchestrator?ONAP is a Service Orchestrator. What is the value proposition of ONAP?Questions for Catherine to ask Panel.Where does ONAP fit in CNF landscapeDoes ONAP implement ETSI specifications? Edge-computing and Cloud native CNFs require support for K8s VNFMs in ONAP. Where are we in this journey?
4. Why do you need Service Orchestrator?45G Use caseUniversal CPE Use caseLarge Number of sitesComputing (Apps across sites) – MECMultiple tenant applications along with operator CNFs.Workload types - VMs, VNFs, CNFs, CNAs and Functions (FaaS)Note: K8s is becoming choice of workload orchestrator in each clusterMulti Edge/Cloud computing scale is similar (or even higher) to Hyper-scalers’ scaleNow Telcos, Enterprises, MSPs need @scale Orchestration and Automation solutions SRINI to talk to it
5. What is the value proposition of ONAP?5ONAP (Service Orchestrator)OSS/BSSDesign time(SDC)Openstack VNFMK8s VNFMONAP itself uses Micro-service architecture & uses Cloud Native principlesONAP Manages Network-service & application LCM across Multiple VIMs (Openstack, K8s) ONAP supports standard models & APIs as per ETSI, TMF, MEF, 3GPPONAP enables Day2 configuration of Network functions via RESTful API, NetConf, K8s CRDsONAP Design tools support multiple descriptions (Helm, TOSCA, HEAT etc..)ONAP DCAE collects telemetry from remote sites, analyzes them and generate any closed loop actions (Scale, Heal)ONAP OOF chooses the right locations to place workloadsOpenstack siteOpenstack siteK8s Edge ClustersK8s Cloud ClustersK8s Edge ClustersK8s Cloud ClustersOrchestrator(SO, OOF, A&AI)Day2/Operations(DCAE, POLICY, CLAMP, CDS)Alla to talk to itONAP is comprehensive service orchestrator
6. Cross-community CNF landscapeTestingRequirementsCNF ConformanceEnd-to-end testingK8s Addon Specs: CSI, CRI, CNI, etcCloud native Principles:Definition, Papers1Requirements to create a reference platform w/workloads meeting the model (high-level requirements and features)Test cases can cover the requirements and be used for verification of the various implementationsLFN’s certification and badging program. Will use the results of several upstream testing sources. Will use multiple sources for requirements.CertificationCore+AddonsBest PracticesSIGSImplementationsCommunities can use the requirements as-is or with adjustments when implementing solutions for their end-usersCNTT Reference Model+ ArchitectureCNF ConformanceCNTT RC-2 (Testing)CNTT RI-2 (Testing)XGVela… any other telcom creator’s solutionsSource: https://docs.google.com/presentation/d/1rTUDacKW96IUJYt-QckITmxwRUD1l8pFZe1xCqyK6yo/edit?ts=5f1f18cd#slide=id.g8ecce7b011_2_0Ranny to talk to it
7. ONAP for ETSI SDO (Conformation to ETSI Specifications)NS/VNF/PNF Modeling and Packaging ConformationSOL004 for VNF and PNF packagesSOL007 for NS package SOL001 for describing VNF, PNF and NS modelsSOL003 (IFA007) for VNF Package ManagementSOL005 (IFA 013) for NS/PNF/VNF Package ManagementSEC022 for ETSI Package and API securityLifecycle Management Conformation for SDC for SOL004 and SOL007 package onboarding, design and distributionONAP NFVO (VFC and SO NFVO) and External NFVO for ETSI MANO SOL005-compliant NFVO functionalities.SOL003 Adapter for SOL003-compliant VNF LCM interfacesSOL005 Adapter for SOL005-compliant NS LCM interfacesSOL002 Adapter for SOL002-compliant VNF/VNFC LCM interfaces (currently on hold)ETSI Catalog Manager for ETSI SOL004/SOL007/SOL001 Runtime Package Management and Parsing for NS/VNF/PNF7Ongoing CNF Modeling, Packaging and Orchestration ConformationIFA 011ONAP VNF/CNF package and models including Helm Charts & Container Images conform to IFA 011IFA 029ONAP CNF architecture and interfaces for MANO, NFVI, CISM and CIS conform to IFA 029IFA 040ONAP conforms to the OS container NFV object model, CISM and CIR management, based on IFA 040 IFA 010ONAP NFVO and VNFM orchestration functions conform to IFA 010 requirementsIFA 005ONAP NFVO and VIM interfaces conform to IFA 005 (Or-Vi)/OpenStackIFA 006ONAP architecture conforms to IFA 006/OpenStack for the interfaces between VNFM and VIMPrepared by: Byung-Woo Jun (Ericsson), Fred Oliveira (Verizon), Seshu Kumar (Huawei)Fred to talk to it
8. K8s VNFM – Past, Present and Future8Seshu to talk to it
9.