ONAP Package for O-RAN SMO Concept Proposal
Explore the proposed solution to create a streamlined package of ONAP for O-RAN SMO, focusing on essential projects and functionality required for Service Management and Orchestration. The aim is to simplify deployment, reduce complexity, and enhance user experience in utilizing ONAP for SMO purposes. The proposal suggests including specific projects, simulators, and documentation to cater to small and medium flavors of ONAP, tailored for SMO use cases. Various interested parties are involved in this initiative to enhance the O-RAN SMO concept within the ONAP framework.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
ONAP Package for O-RAN SMO Concept Amar Kapadia, Aarna Networks Christophe Closset, AT&T
O-RAN SMO The O-RAN specification defines a component called Service Management and Orchestration (SMO)
ONAP as an O-RAN SMO ONAP can comprehensively satisfy O-RAN SMO requirements In fact, many components of ONAP are already being used for O-RAN in both the ONAP and O-RAN-SC communities
Problem Statement Option#1: Install all of ONAP; some users get discouraged Option#2: Install a component at a time from O-RAN-SC: CM This approach results in an incomplete SMO docs.onap.org
Solution Create a package of ONAP for O-RAN SMO Include only the projects required for SMO functionality Specifically: - Create instructions for stand-alone deployment of small and medium flavors of ONAP specifically as an SMO - Include the right simulators (may require new Helm charts) - Reduce the size of projects included as well (e.g. wiki below or drop some services) - Create documentation (admin guide, user guide) that shows how to utilize ONAP as an SMO See Deploy OOM and SDC (or ONAP) on a single VM with microk8s - Honolulu Setup wiki page for inspiration
Proposal for Small & Medium Flavors NONRTRIC/CM SDN-C/R FM/PM DCAE DMaaP Policy NONRTRIC/CM SDN-C/R CDS CPS (?) FM/PM DCAE DMaaP Policy Orchestration SDC SO OOF (?) Multicloud Inventory A&AI Simulators Simulators Small Medium(s) *Supporting projects such as AAF will also be included *Supporting projects such as AAF will also be included Comments: 1. Tie flavors to use cases e.g. O1, A1, orchestration, slicing etc. this will drive documentation, simulators etc. Focus on which DCAE microservices, policies, and other artifacts to include for SMO use case(s) Opportunity to extend beyond ONAP e.g. A1 enrichment services, O-RAN-SC simulators 2. 3.
Interested Parties Aarna Networks AT&T highstreet technologies Samsung Tech Mahindra Checking with orange
Where Should the Project Reside? ONAP Documentation? ONAP Use Case? O-RAN-SC? OOM? [Main project we will be tied to] Somewhere else? Which release Honolulu or Istanbul or both? Proposal Use the PoC mechanism in ONAP to start with; release independent, very light approval process (maybe arch. committee) Free of the release related administrative processes Show idea is viable/useful, show demos (we get visibility), and make it more mainstream
Next Steps (DONE) Christophe to discuss with Sylvain: - Is orange interested to join - Should we get a sub-branch in OOM? Amar to update Catherine - Get her approval on the PoC concept - Understand what other approvals she would like us to get such as architecture subcommittee - Figure out whether we can use OOM meetings or dedicated meetings Amar to talk to David - Understand JIRA process (to create PoC requirements), where should we create the wiki page, Slack channel
OOM PTL meeting Discussed options for materializing the POC - Recommend creating one or several override files on master - Fine tuning of components is now possible (eg : no need to deploy ALL in a component) - Document usage in OOM RTD (+wiki?) If time allows : - Create a CNF package that can be onboarded in ONAP with O-RAN SC specific components + simulators - Create a basic O-RAN testsuite that : Onboard that CNF package Instantiate that package using SO CNF orchestration Run a hello world test on both SMO + O-RANSC components This would allow to integrate that suite in Gating and ensure the SMO + O-RAN SC components are part of ONAP regression test suite.
High level view POC scope ONAP O-RAN SC Non SMO/specific components charts O-RAN SMO Components Validate interactions with O-RAN tests SMO override + doc
High level view Final with tests automation ONAP O-RAN SC Non SMO/specific components charts O-RAN SMO Components CNF package ONAP Xtesting O-RAN suite focussed on testing SMO interactions SMO override
s akapadia@aarnanetworks.com www.onap.org
