Versions Compared

Old Version 181

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user cl664y@att.com

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Info


Meetings: 

Mailing List:  (Groups.io)

Calendar:  (Groups.io)

Slack ChannelRecordings

Bi-Weekly- Wednesday, 7.30am PST 

onap-enterprise@lists.onap.org

List URL: https://lists.onap.org/g/onap-enterprise  
Sticky Post:  https://lists.onap.org/g/onap-enterprise/message/7
Hashtag: #enterprise

https://lists.onap.org/calendar

#sub-enterprise


Enterprise Recordings


ONAP For Enterprise - Roadmap (Latest Update: Jan 11th, 2022)


Meeting Minutes 

Table of Contents
maxLevel2

Meeting Minutes - 1/20/2021

Key Questions: 

#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

...

...

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?

...

...

#3 Maybe reconnect with Helen Chenabout Healthcare

...

...

#5 Kick-off a survey to get feedback about interest and use cases

Meeting Minutes (LFN Event) - 2/2/2021

  • 2021-02-02 - ONAP: TSC Task Force- ONAP For Enterprise Business - LF Networking - Confluence

Meeting Minutes - 2/17/2021 

  • Review action items from LFN Event
  • Importance
    • 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

Image Removed

  • 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?)

Meeting Minutes - 3/3/2021 

  • Suggestion to reschedule this meeting on Wednesday at 7am PST (to be discussed on 3/4 during the next ONAP TSC)
  • Creation of a new EUAG (End User Advisory Group) dedicated to Enterprise Businesss (under preparation) - LFN Board to be voted on March 24th, 2021
    • Kenny will provide criteria to be part of this new EAUG (not company membership) but people involved in deployment, design, implementation, etc. 
    • Open beyond "carriers" 
  • Intro about DARPA Program with Trudy Morgan (Cloud Computing Expert)
    • Focus on 5G Network Security
    • 4 years program
    • E2E Open Source 5G Network across the US
    • ONAP Added-Values: ONAP for Orchestration including Network Slicing, AI/ML/DL
    • Mostly all the components are open source components except RAN part
    • Some ONAP pages about Network Slicing
    • SDOs: ETSI, 3GPP
    • Current status:
      •  Amar Kapadia(representing LFN/ONAP Community) is currently setup an ONAP test-bed to demonstrate E2E Network Slicing capabilities
      • Lab currently open but required VPN connection, located in San Diego

Meeting Minutes - 3/17/2021 @7am PST

  • 5G Super Blueprint
  • Discussion about ONAP/ODA Integration
    • How ONAP could improve/build Network Service Visualization/Customer Facing Service (CFS)?
    • Currently Network Slicing activities are trying to work on this area 
    • TAC Whitepaper is in progress
      • Additional information about CSMF
      • What are CSMF functionalities supported by ONAP today?
      • Will ONAP support any CFS capability?

Meeting Minutes - 3/31/2021 @7am PST 

  • Trudy Morgan : Present first ONAP/OPS-5G use cases 
    • 5 year effort - all work being done in the LF. Work will be up-stream w/o forking code
    • NIWC: Naval Information Warfare Center 
    • Research project - all work is unclassified.
    • Deck presented today: OPS 5G Use Case.pdf 

Image Removed 

  • 5G Super Blueprint Roadmap is also considering the OPS 5G program inputs.
  • 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.

Meeting Minutes - 4/14/2021 @7am PST 

  • Latest ONAP/OPS 5G updates from Amar Kapadia
    • 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 Introduction Neil Hoff, NIWC PAC 

Super Blueprint and 2021 Roadmap, including slicing Amar Kapadia, Linux Foundation 

OPS-5G Technical Area 3 (SABRES) – Secure Slicing Dr. Erik Kline, USC/ISI 

MAGMA - Target release for network slicing and timeline for requirements development Amar 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

            Advantage: full re-use of the current E2E Network slicing capabilties developed in ONAP - 5G Super Blueprint_ONAP_Magma proposal (V1)

Image Removed

            Other Info:

Magma Core Orch is decsribed here https://docs.magmacore.org/docs/orc8r/architecture_overview
Code: https://pkg.go.dev/github.com/go-magma/magma

Meeting Minutes - 4/28/2021 @7am PST 

  • 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

  • Integration with Magma Controller/GW

#1 Review the 4 ONAP/Magma action items identified on 4/14/2021 - Feedback from Amar Kapadia, Prabhjot Singh Sethi (prabhjot@aarnanetworks.com)
        Magma Controller REST Interface - magma | 1.0.0 | karthiksubraveti | SwaggerHub

        Magma Controller = orc8R = magma/orc8r at master · magma/magma · GitHub

        Doc web site: Introduction · Magma Documentation

        There is no Magma GW documentation at this stage

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 (sad)  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

Meeting Minutes - 5/12/2021 @7am PST 

Image Removed

    • 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 

Image Removed

cl664y@att.com will submit a proposal - details will be defined later with the Task Force. Key Speakers (TBC): Byung-Woo Jun, Prabhjot Singh Sethi.

Meeting Minutes - 5/26/2021 @7am PST 

Working Group Activities

Recent Presentation Material

Meeting Minutes - 6/2/2021 @7am PST

Meeting Minutes - 6/23/2021 @7.30 am PST 

Image Removed

Meeting Minutes - 7/7/2021 @7.30 am PST 

https://wiki.lfnetworking.org/download/attachments/56066612/ONAP%20For%20Enterprise_LFN%20DDF%20June%202021_Final_V2.pdf?version=1&modificationDate=1623166120000&api=v2

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)

Image Removed

  • Additional areas that we could explore in parallel:
    • alarms/events generated by VNF Magma 1.5 GW (question)
    • Create alarm/events catalog and check if 3GPP compliant
    • DCAE VES (question)

Meeting Minutes - 7/21/2021 @7.30 am PST 

...

  • Prabhjot Singh Sethi
    • #1 enabling 5G as part of the Access GW will be part of the next Magma release (v1.6) but roadmap not yet finalised
    • No major in the Configuration API discussed on 7/7
    • Network slicing and complex features will be part of later Magma releases (but not v1.6)

...

Functionalities (3GPP TS 23 501 Rel 17 June 2021) related to "Session Service Continuity"  (deliberately not including details on SSC Mode 1-3 related to UPF/PSA selection/re-selection) and "Local Traffic Routing" functions/capabilities for "inter-" and "intra-"  Platforms/Systems  communiction (HPLMN and VPLMN) with regard to %G NFs Cloud Native factors adoption in CSP Service Solution Frameworks.

Related to that, there is also the issue of Authentication, Authorisation and Accounting (also as part of the Security) (SUPI; SUCI; GUTI) for both, Applications/Service commissioning/instantiation and Users and related to them UEs.

...

Image Removed

Image Removed

E.g aiming at 3GPP Service Communication Proxy (SCP/SeCoP), as a CNF, a Component performing Proxy-like Routing Tasks can be certainly decomposed into Micro Services based on their Workload type (e.g. Long-Running Tasks versus Short Logical Operation to determine an outcome).  However, by De-composing a NF into Microservices the newly created CNFs need to be addressable among each other based on Stateless Protocols like HTTP. The result is a typical “Chicken and the Egg” Problem, as the CNFs were supposed to implement Service Routing, but relies on a Service Routing among them.

Other Factors such as Port Binding and Dev/Prod Parity simply do not apply to Functions that sit below the Transport Layer where Ports are exposed.

Furthermore, for Networking related Tasks (Routing, Firewalling, etc.) Packets from senders such as the UE that are supposed to be handled must be encapsulated in a Stateless Protocol to reach the next Microservice that forms the Networking Application. Thus, not all VNFs can be ported to CNFs to enable an economy at scale.  However, even though not all Cloud Native factors can be fulfilled for some VNF types, VNFs can be Cloudified aiming at a high adoption of the Cloud Native Factors without the notion of decomposing a VNF into Microservices (CNFs) that form the Application.

  • Questions about Magma: Is there any performance metrics about Magma? How many users per GW etc without any additional infrastructure? Prabhjot Singh Sethi said that Magma team said that currently put high physical devices as an Access GW, you will get a better number.
  • Magma Containerization is delayed, not date/commitment yet, phasing approach but the requirements have been created in Github.
  • Chaker Al-Hakim discussed the LF Open Source Component Projects for 5G under LF Edge umbrella. Chaker invited people to attend the LFN 5G Super Blueprint meeting. 
  • Prabhjot Singh Sethigave some information about Akraino Blue print part of LF Open Source Component Projects for 5G. Magma GW has a monolithic architecture and not yet foreseen for Edge blue print.
  • Chaker Al-Hakimwill join Akraino TSC meeting to provide some awareness about  LF Open Source Component Projects for 5G.

Meeting Minutes - 8/4/2021 @7.30 am PST 

  • SABRES (Secure, Adaptive, roBust, Resilient, and Efficient Slices) presented by Dr Erik Kline
  • Gervais-Martial Ngueko : Proposal of SABRES Integration into ONAP E2E Network Slicing call flows

Meeting Minutes - 8/18/2021 @7.30 am PST 

=>  Catherine to open the bridge on Wednesday (8/25) at xxx - team to let us know (smile)

    • Feedback from Amar Kapadia - Onboarding of standalone EMCO done but integration with ONAP still under discussion a.k.a. EMCO v2 (additional development/integration work will be required)
    • Magma CNF date not yet available - current path: Magma VNF (1.6?). Nevertheless let's complete our current path so we can learn from our initital integration (not only from a service delivery perspective but also from service assurance, security, resiliency, etc perspectives
  • ONAP/SABRES Integration - current status: SABRES constructor/validator under prototype/development; ONAP/SABRES - Design level, no implementation/integration yet
  • Follow-up on Michael August's questions  - In order to document a test plan about how to evaluate the network slicing security research being done by Dr. Kline's team. Can the ONAP Community provide information about:

1) Is there an API within ONAP's VNF Manager component or Element Management that enables assignment/allocation to specific pieces of hardware within the NFVI/cloud infrastructure?

Some information are currently available in the AAI component (Active Available Inventory)

Our model can also easily be adapted to store any information needed if our current model does not support it. APIs for inventory operations are auto generated once added to the model.

Can you please review our current model/relationships to see if it supports what you are looking for

Our schema: https://gerrit.onap.org/r/gitweb?p=aai/schema-service.git;a=blob;f=aai-schema/src/main/resources/onap/oxm/v24/aai_oxm_v24.xml

Allowed relationships: https://gerrit.onap.org/r/gitweb?p=aai/schema-service.git;a=blob;f=aai-schema/src/main/resources/onap/dbedgerules/v24/DbEdgeRules_v24.json

A&AI API Documentation: https://wiki.onap.org/display/DW/AAI+REST+API+Documentation+-+Istanbul

Associations between virtual and physical resources is currently done in A&AI.

Question: What level of granularity do we need to consider (pod, container, etc)? Michael to confirm 

VNF Manager in the context of ONAP:

#1 external VNFM adaptor provided by SO (ETSI compliant)

#2 VNF (CNF) LCM is provided by SDNC/CCSDK (Heat compliant)

2) If the underlying VIM provides APIs for placement of virtual resources on specific pieces of physical hardware, then does ONAP provide corresponding APIs that the VNFs can use to leverage these VIM placement APIs to perform precise placements of the virtual resources they use onto specific nodes within the physical infrastructure? It also depends on what the VNF/CNF/PNF provide as information. 

If the VIM is based on k8S then the new EMCO version (developed by Openness) will support a way to define the platform requirements on per workload basis as intents. 

At the time of deployment, it can do match making between requirements and capabilities it discovered early on to select the right K8s cluster.

OpenNESS - EMCO API Documentation. Currently the latest EMCO version (V2) has not yet been integrated to ONAP.

3) Are there APIs between the Network Slice Instance layer and the Resource layer (resource management functions) that enable a network slice instance to gain information about the current mapping of network slice instances to physical resources? Likewise, are there APIs that enable the network slice instances to leverage specific resources available within the resource layer?

The current Network Slicing functionality (till Istanbul release) hasn't considered VNF placement, resource occupancy levels of a cloud instance, occupancy levels of a VNF, etc. due to a number of reasons (first focus on the basic functionality and key lifecycle phases, limited interest/contributions from community for core slicing (where VNF/CNF will be most relevant), etc.). Some of the aspects were being discussed for future releases beyond Istanbul.

In addition, , there is work done on VNF/VF module placement optimization done in OOF. The HAS functionality in OOF could be leveraged, a couple of references are given

o          https://docs.onap.org/projects/onap-optf-has/en/latest/index.html#master-index

o          https://wiki.onap.org/display/DW/OOF-HAS+Homing+Specification+Guide

There was also another functionality FGPS (Fine-Grained Placement Service) in OOF which I think is no longer maintained

Seshu Kumar Mudigantiwill provide additional further information about SO NSSMF adaptor, compliant with 3GPP

CSMF and NSMF are implemented using SO BPMN workflows to support 5G network slicing use case. CSMF workflow will process the user input (service request) that comes from CSMF portal (UUI) and save the order information into a communication service instance in AAI. Then CSMF will send network slice request to NSMF workflow, and NSMF will then create service profile, NSI and NSSI. Service profile is a logical concept which exists only in AAI - it contains two AAI instances, one is a profile instance that will hold the slice parameters, and the other is a service instance which will be used to organize the NSI. NSI is also a service instance in AAI which will be used to organize NSSI. NSSI is the actual entity which will be created by NSSMF and an AAI service instance will also be created to represent NSSI in ONAP context. NSI and NSSI can both be shared.

SO queries OOF for slice template selection and then slice instance selection. In response to slice instance selection query, OOF may return an existing slice instance or may recommend SO to create a new slice instance. A new process called Orchestration Task is created to manage recalibration of NSI&NSSI selection with manual intervention from the portal. A new SO adapter is created to be the adapter of NSSMF which will interact with external NSSMF for NSSI management. See the SO Impacts and Interfaces wiki page for details.

Meeting Minutes -  

Meeting Minutes - @7:30 am PST

Meeting Minutes - @7:30 am PST

  • ONAP Service Assurance based on Magma Glacier Peak v1.6 - Jorge Hernandez , Gervais-Martial Ngueko 
  • Discussion about ONAP Monitoring/Integration possibilities (slide 11)
  • Next steps:
    • #1 Meet the ONAP DCAE project to define which option to pursue.
    • #2 Share our initial analysis with the Magma Team.
    • #3 Identify which KPIs, i.e. QoS, to be integrated as suggested by Ike Alisson during today's session

Meeting Minutes - @7:30 am PST

  • ONAP/Magma KPIs Jorge Hernandez , Gervais-Martial Ngueko 
    • Can we be aligned with VES template? - to be validated with the Magma Team.
    • Determine the use cases, control loops that we can trigger out of Magma KPIs
    • Some options about Data Collection are still under evaluation including Prometheus (Apache 2.0 License)
    • How would we introduce Prometheus to ONAP? It is not specific for DCAE and could be used by other components
    • The main Prometheus server runs standalone and has no external dependencies.
    • The deployment of Prometheus requires some changes and ownership by the OOM Team
  • ONAP/SABRES Integration - waiting feedback from Dr. Eric Kline about the APIs (probably in November 2021) David McBride 
  • ONAP For Enterprise - Roadmap

Image Removed

Meeting Minutes - @7:30 am PST

  • ONAP/Magma Integration Updates? - Yogendra Pal Lukasz Rajewski  ( Byung-Woo Jun ,   Amar Kapadia )
  • ONAP/Magma KPIs discussions
    • Magma Contacts: Brian Barritt, Hunter Gatewood, Marie Bremner 
  • Prometheus proposal/feedback from Sylvain Desbureaux :
    • Not part of ONAP deployment a.k.a. OOM
    • But can consumed by our ONAP components
    • Timo Perala will advice how we could use Prometheus either on WindRiver, MS Azure, etc?
    • Two options shared by Jorge Hernandez (using Prometheus) and requests to the Magma team:
      • Magma compliant to VES specifications - preferred option
      • Magma sent notifications to DCAE directly and ONAP will perform VES mapping. Risk: Interface break if the format is changed and the ONAP community not informed 
  • Positive from Walmart's representative during the last LFN Governance Board meeting - Stay Tuned

Meeting Minutes - @7:30 am PST

  • ONAP/Magma KPIs discussions
    • VES (Virtual Event steam) specs discussion scheduled for the first 30 minutes of the Magma Bi-weekly Engineering Meeting
    • Welcome Shubham Tatvamasi, Vipin Rathi, Guillaume Belanger (Magma team)!
    • Jorge Hernandez , Gervais-Martial Ngueko , Vijay Kumar (ONAP DCAE PTL) - provide information about VES specifications and any useful material (VES KPIs samples, ONAP/Magma POC material/intial inputs, etc.) to the Magma team prior the meeting on Nov 18th, 2021.
    • Setup a pre-meeting with Shubham Tatvamasi to share ONAP/Magma POC material/intial inputs - will be defined over Magma 'slack channel' (Genral). Logistics support will be provided by David McBride , Kenny Paul  - thank you all !
  • ONAP/Magma Integration Updates (Service Delivery)? - Yogendra Pal, Lukasz Rajewski , Byung-Woo Jun
    • Yogendra Pal  - ONAP Honolulu release has been deployed to resume integration with Magma 1.6 (VNF/AGW - Access Gateway). Trying to deploy on Nov. 11th the Magma package through ONAP SDC (Service Design & Creation).
    • Lukasz Rajewski - Instantiation of Magma CNFs (K8S) - using ONAP SO CNF Adaptor (work in progress). Is there any plan concerning Magma CNF? Not yet part of the Magma roadmap.
    • No CDS Integration yet scheduled
  • Walmart's representative (Ciby)
    • Meeting scheduled tomorrow at 2pm PST
    • Purpose is to share the goals from the ONAP Enterprise Task Force, Onboarding Community process and later on, discuss any potential use cases
  • Sharing the presentation to Layer123 World Congress on Nov 17th, 2021

Meeting Minutes - @7:30 am PST

  • ONAP/Magma KPIs discussions - follow-up discussions on what we have learned from Nov 18th, 2021
    • Material/demos/slides were shared
    • No push back about using VES Specifications to collect KPIs from Magma but no agreement yet
    • 'ONAP' Slack channel with Magma has been created to kick-off the implementation
    • Next steps:
      • Magma Team to assess all the information shared on 11/18
      • Follow-up with Magma team early in january 2022 to determine - shall we code "VES" adaptor (accepted by 3GPP) in Magma code; will Magma do it? Need to agree with Magma about the next steps.
      • Additional discussions are required to define concrete use cases that we want to implement from ONAP side i.e. monitor Magma GWs, Network Slicing etc., without overlapping any control loop capability already offered by Magma.
      • Identify KPIs related to ONAP E2E Network Slicing that could become a requirement for Magma - Deadline: January 8th, 2021. Let's review any requirement on our first Enterprise call on 1/5/2022
  • Feedback from the "SABRES" working session organised on December 1st, 2021
    • Meeting recording
    • Diagram shared by Erik Kline
    • SABRES Presentation from Gervais-Martial Ngueko
    • Next Steps:
      • Next meeting to be scheduled end of January 2022
      • Investigation about SABRES Resiliency and any other non functional requirements that might impact ONAP Integration
      • Send second iterations of the deck to Erik Kline including concrete questions
  • ONAP/Magma Integration Updates (Service Delivery)? Feedback about the onboarding of Magma VNF through SDC and next steps
    • Yogendra Pal has contacted the Magma team to perform helm chart changes
    • Is there any additional information to clarify the namespace usage?
  • LFN DDF event (Jan 10th-13th): Proposal has been submitted

Agenda - @7:30 am PST

  • EMCO/Magma integration
    • No issue encountered with Helm
  • Yogendra Pal ONAP/Magma Integration - Latest Updates (Service Delivery)
    • Align with the previous roadmap
      • ONAP CDS
      • SO CNF 
      • SDC Onboarding
  • Review our ONAP Enterprise Roadmap - what have we really completed in 2021 and what will be our 1H 2022 goals?  

Agenda - @7:30 am PST

  • Review any KPI Network Slicing requirement to be submitted to the Magma team 

Action Items (In Progress)

Action Item (Closed)

...

#1 Seize the opportunity to discuss Magma CNF requirements/roadmap as part of Nov 18th, 2021.#2 Check how long Magma 1.6 support will be available?  What's the process to raise a bug? How long it will take to fix it?

...