#1 What does ONAP offer to an enterprise customer (IoT, Financial, Healthcare, Gaming, etc) that we can't get from existing cloud offers or outside the Cloud.
#2 What does ONAP offer on top of that outside of the telco space?
Different Scenarios
1) 3rd party vendors using ONAP to serve their enterprise customers (operating model - managed services)
2) Operators offering solutions to Enterprises (based on 5G Techno - Network Slicing, Virtual Edge, etc) supported by 3rd party vendors
Feedback from Carriers:
Fernando Oliveira- Investment in Gaming, Edge Computing - possibility to re-use ONAP as a key orchestrator
Catherine Lefevre - Edge Computing is the area where AT&T have invested (i.e. Akraino) in conjunction with ONAP possibilities; We have a Gaming division inherited from TimeWarner but not yet explored added-value of ONAP in this space
3) Enterprise customers running ONAP themselves (on their premises), supported/trained by 3rd party vendors
Additional thought(s)
#1 Investigate what Openstack is offering to Enterprise Business?
to rebrand ONAP and its components outside the "Network" domain
to be able using ONAP components independently
to demonstrate with some real cases ONAP components with other systems/applications (not CNF, PNF, VNF)
to use ONAP (or a subset of ONAP) as a black box
Survey- key items (in progress)
Comments: Need to re-adjust the survey and also ONAP message based on "Enterprise" Terminology
What are your goals about Cloud migration?
Are you already hosting your IT applications in public cloud or private cloud managed by a 3rd party vendors? If not - Where are you in your virtualization journey?
What are the different major steps being part of your migration?
Which OSS/BSS systems/IT applications will not be part of your virtualisation journey? Hybrid model (Private on prem/Cloud & Public Cloud)
(After introducing ONAP) which consumption model do you think you would like to adopt? Or will you adopt another one not listed below? Need to re-adjust the consumption model for Enterprise Business
Have you any regulatory requirement to be considered?
Any particular device/standard to be supported and connected to your IT application(s) ?
Size of production deployment (small/medium/large)? Define "size' for Enterprise Business
What would you consider "as a service" for your Enterprise Business (which application, what type of IT support, etc?)
Goal is to use as much OSS as possible, but may need commercial solutions initially in areas that are less OSS mature like RAN i.e. 5UE, Commercial gNB
From a testing perspective, the goal is to us Nationwide network to enhance DoD ability to test 5G Core security (Multisite OPS 5G Joint Independent Testing Option) but it will also dependent on Magma deployment model.
ONAP capabilities to support this program:
Orchestrate/Instantiate and Magma Orchestrator (instead of SO)
ONAP Network Slicing functionalities
LCM
Control Loop mechanisms (including ONAP/Acumos)
Akraino/ONAP Blueprint
Believe that we need to be proactive on this
Would like Aarna to provide a regular update on progress to this team. Set aside the first 5-10 mins of every meeting for that purpose.
Need to make sure that standard process workflow is followed for feeding requirements into the community
ONAP Enterprise Task Force will be the first entry point for OPS 5G program supported by the Requirements, Architecture and Security subcommittee representatives.
ONAP/Magma discussions on April 8th - Deep Dive about ONAP
Current understanding is that we could use REST API (northbound ITF) or Mesh
OPS 5G meeting on April 9th - focus on E2E Network Slicing
Welcome and IntroductionNeil Hoff, NIWC PAC
Super Blueprint and 2021 Roadmap, including slicing Amar Kapadia, Linux Foundation
OPS-5G Technical Area 3 (SABRES) – Secure SlicingDr. Erik Kline, USC/ISI
MAGMA - Target release for network slicing and timeline for requirements developmentAmar Padmanabhan, Facebook
ONAP - How network slicing will be orchestrated by ONAP Swaminathan Seetharaman, Wipro
OUSD(R&E) comments / discussion
Key take away: Align people on "what it is a Slice" terminology
How could ONAP interact with Magma GW/Magma Controller?
Some additional info about Magma
First deployment of 5G-FWA in June 2021 (Brazil)
Can be deployed on ARM/ESXI
Horizontal scaling
NB ITF= REST (to be connected with ONAP) or Mesh
3 options:
#1 Create a dedicated controller via SDNC and handle Magma GW like any other device
#2 Have an adapter for the magma in ONAP Service Orchestrator and use it as a resource orchestrator for the specific jobs. Disadvantage: create something specific
#3 5G PNF Plug & Play and consider Magma GW as a PNF?
Current proposal: Avoid to create something specific but re-use what it is already developed in ONAP (SO/SDNC/SDNR) and orchestrate directly the Magma GW via gRPC
Need to understand what it is behing the Magma GW and explore if there is a possibility to interact directly with the devices? Maybe not acceptable
Feedback from Swaminathan Seetharaman about future scope/functionalities/roadmap supported by CSMF (Communication Service Management Function)
With ref. to the roadmap for CSMF, there is nothing planned for Istanbul release. Anything beyond it will depend on the interest from use case contributors and/or community.
A few points which came up in our earlier discussions include the following. However, none of them have progressed further since then.
#1 Control Loop actions at Communication Service (e.g., eMBB) level (service assurance) which will be driven by CSMF. This could result in slice-level reconfigurations, or even re-mapping of the service to a different slice instance.
#2 Having different service priorities, e.g., resulting in pre-emption (when needed) during service fulfilment and during operation, for services having a higher priority
Magma GW = to be considered as CNF (by June 2021); currently available as PNF/VNF
Magma Controller= CNF
#2 Currently the goal is to interact with the Magma Controller as a first step directly.
As part of the roadmap, we should also investigate if there is a way to interact directly with the Magma GW (reduce 1 overhead layer between Magma/ONAP)
Additional information are required about Magma Controller to finalize the right architecture.
#3 Currently the scaling of GW is manual and triggered by the user.
Magma Controller is also manual so both (Controller/Magma) can be orchestrated via ONAP
Opportunity for ONAP to automate the scaling of Magma GW (Control Loop)
#4 Can we conclude Magma is an EMS (Element Management System)? YES
#5 5G Blueprint based on Guilin/Honolulu? Magma release is scheduled by June 2021 therefore let's consider ONAP Honolulu release
#6 Is there any Security Magma requirement? based on HTTPS, Mesh? Not yet available.
Currently used DockerCompose, next step will be used Helm v3.0.
#7 Any information about Magma packaging, modeling requirement?
Recommendations: TOSCA descriptor pointing to HELM (in alignment with ETSI specs
Byung-Woo Jun - Next on ONAP CNF Task Force - every Thursday at 1pm UTC
Initial analysis about Magma integration on April 29th, 2021
Review of the integration with Magma Controller/GWs
Byung-Woo Junshared the latest Magma architecture proposal
Amar Kapadia explained that there are two interactions expected with ONAP: Deployment/Onboarding & Instantiation
Arun Thulasi (from Magma's team) provided additional information about how Magma Controller & GWs are deployed. Magma Controller is today deployable on AWS K8s. Goal is to have GWs fully containerized by June 2021. Magma controller (orc8R) is managing all GWs. Additional information: Configure AGW · Magma Documentation
Chaker Al-Hakim sees Magma components as services orchestrated by the ONAP Platform. ONAP will onboard Magma via SDC, instantiate Magma Controller via SDNC and then collect KPIS/Telemetry data to trigger any Control Loop action (if required) + Network Slicing capabilities (NSMF through NBI)
Prabhjot Singh Sethi shared the HL Integration Plan
Upstreaming - each project will host the source code and provide artefacts/containers to be used for 5G Super Blueprint
Feel free to review offline and add any component
How do we plan to communicate with the other open source communities about 5G Super Blueprint (Akraino, Anuket, LF Edge) to discusse dependencies and requirements?
<Catherine> Bring this item to the next 5G Super Blueprint call.
Magma 1.6 is currently delayed by another month. This release might not contain the CNF Magma Access GW version.
Suggestion to move forward with the VNF Magma Access GW (and use Magma 1.5 only supporting 4G) but will not use "5G - PNF Plug and Play"
Call flows to be updated accordingly - slight changes versus original CNF flows
Magma 1.6 will contain VNF Magma Access GW supporting 5G (to be available end of July 2021)
Potential APIs change - impacting the registration (hope backward compatibility and/or 'tags" to support 5G (and still LTE)
Additional areas that we could explore in parallel:
alarms/events generated by VNF Magma 1.5 GW
Create alarm/events catalog and check if 3GPP compliant
DCAE VES
Agenda - 7/21/2021 @7.30 am PST
Magma/ONAP Integration - latest updates
Kick-off discussions with LF Edge?
Action Items (In Progress)
Prabhjot Singh Sethi- Will check how long Magma 1.5 support will be available? Will VNF Magma GW still available with Magma 1.6? What's the process to raise a bug? How long it will take to fix it?Check if Magma 1.6 API backward compatible (supporting both LTE/5G) to Magma 1.5
Amar Kapadiato follow up with Louis (LF) to setup a repository for Helm Charts (Magma special packaging); Amar Kapadia : I have followed up with LJ Illuzzi
Catherine Lefevre "How do we plan to communicate with the other open source communities " - Bring this item to the next 5G Super Blueprint call.
(Catherine) To follow up with Swaminathan Seetharaman about scope/functionalities/roadmap supported by CSMF
Kenny): Setup onboarding process for DARPA Program
(Veronica): Provide the Orange Invite to be shared with the ONAP community
(Kenny) Collect any EUAG Use Cases
(Kenny) add an item to TSC call - 3/25 about EUAG for Enterprise
(Kenny) add an item to TSC call - 3/4 - new schedule for Task Force - Enterprises + introduce agenda (3/31) - Alla Goldner, Timo Perala (requirement subcommittee) and Chaker Al-Hakim(architecture subcommittee) to attend
(David): Follow-up with Amar Kapadiaabout TSC presentation about current status regarding OPS-5G & LFN Activities
Catherine Lefevre Discuss with Arpit about the new name a.k.a "5G Open Source Stack" - can be confusing with OpenStack initiative from RedHat; preference is to use "Open 5G Stack"
Rework our ONAP Added Values Message in alignment with Vertical Industry & Enterprise Business - presented during the DDF Event in June 2021
Contact Enterprise Business Units within our own company
and triggered by the user.
