Meeting Recording

Chat File


Attendance

Please enter you name and company. Tag yourself using LF ID User Name. Don't have an LF ID yet? Go here: https://myprofile.lfx.linuxfoundation.org/.

NameCompany

LJ Illuzzi

Linux Foundation
Ganesh VenkatramanKaloom
Brandon WickAarna Networks
Anindita RaychoudhuriRebaca Technologies
Satish VermaSpirent Communications

Pano Xinos

LFN
Paul ChoiseulAmerican Tower
Satish SadagopanIBM
Kenny PaulLFN
Muddasar AhmedMITRE/ONAP
Yogendra PalAarna Networks
Robert EdwardsMatrixx Software


















                        

Agenda:

  • Start Recording- helps facilitate minutes and Action Items
  • Antitrust
  • Welcome 1st Time Attendees
  • Invitation to Collaborate on the Agenda and Discussion Topics
  • Marketing Update
  • ONE Summit Demo
  • Off-Week Deep Dive Meeting
  • Any Other Business


###################################

LF Anti-trust

  • We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.


Start Recording


Welcome 1st Time Attendees

Welcome all. new attendees. If you have any questions about participating in this community, please contact Louis Illuzzi (lilluzzi@linuxfoundation.org).

5G Super Blueprint Overview and Getting Started


Invitation to Collaborate on the Agenda and Discussion Topics

  • In an effort to get even more community input on the agenda and the discussion topics we are using the groups.io mailing list to send an invitiation to contribute to the meeting agenda. The invitations are set to go on the Monday prior to each bi-weekly meeting.


Marketing Update


ONE Summit Demo

  • The goal is to demonstare end to end slicing from core to RAN
    • Expectations- Radio (RAN), Transport, Core slicing
    • Transport slicing (DoD/GovOps)
      • GV- proposal to put GXC in UNH and connect with a pipe. This way transport is part of the soluton.
      • Hardik Jain All equipment may be installed Montreal. If so how do we proceed with Transport slicing?
      • Potential for Core (Free5GC) to be installed at UNH (per Neil).
    • Secure slicing- Muddasar to lead?
  • Use Case(s): what do we want to show?
    • Streaming
    • IoT (security cameras, robotics)
      • Visual inspection at the edge use case (Satish Sadagopan) - application layer, as opposed to network layer. Can be transitioned to Ultra-low lantency use case.
    • Edge Computing Support (DoD/GovOps):
      • IoT Device Authentication at the Edge - include DARPA Performers
      • Traffic Routing at the Edge - 
      • Packet Filtering at the Edge - can enable device authentication at the edge
  • Core:
    • Free5GC - installed in Kaloom lab, along with GXC RAN
    • SD-Core - DARPA Performers have experience with SD-Core
    • What capabilities does the core need to have to full fill the use case(s)?

Lab Status/Upgrades

  • Lab Architecture Slides
    • Lab architecture updates based on use case functionality needed.
  • Hardware order status?
    • Graphic cards shipped, need to be installed
  • Software upgrades at Kaloom Lab? - Tunde to provide details
    • Currently we will do both CU and DU at same location.
    • Based on last discussion if needed we can split between UNH and Kaloom lab


Off-Week Deep Dive Meeting-  

Next Meeting Aug 16 -

  • Neil Hoff- pull in DARPA Performers to discuss: 
    • IoT Device Authentication at the Edge - include DARPA Performers
    • Traffic Routing at the Edge - 
    • Packet Filtering at the Edge - can enable device authentication at the edge
  • Satish Sadagopan Visual inspection at the edge use case (Satish Sadagopan) - application layer, as opposed to network layer. Can be transitioned to Ultra-low latency use case. Automotive applications
  • Lab Architecture Slides
    • Lab architecture updates based on use case functionality needed.

 



Work Stream Updates


Architecture & Adjacent Communities


Action Items (open)

  • Kader Khan,  Parthiban Nalliamudali , Benjamin Posthuma begin work setting up radio components in Wavelabs lab. Can radio be shipped to Wavelabs in Hyderbad? GXC-radios working with Magma. Testing of all Magma 5G capabiliites underway. Other radio vendor DMW
  • Tracy Van Brakle  extend invitation to other operator members of ORAN (i.e. Verizon)
  • Heather Kirksey Reach out to outreach committee on Magma Slack #magma-outreach-committee to discuss joint marketing opportunities.
  • Tracy Van Brakle Any link to Multi-Operator RAN from Dec 2021? Referenced on a previous call.
  • Alex Stancu Can help with ORAN implementation. Martin- what is the success criteria? Agenda item for Deep Dive meeting?
  • Martin Skorupskican add detail and next steps for SMO Framework. https://wiki.o-ran-sc.org/x/-YvYAg


Any Other Business


********** Parking Lot **************

Lab Architecture:


Roadmap - updated 5G SBP Phases

  •  Off-Week deep dive meeting focus was on Road discussion: https://wiki.lfnetworking.org/x/iZ8ZB
  •  Roadmap refresh presented by Amar
    • 5G Super Blueprint Roadmap
    • Magma 1.7 release pending. Testing underway
    • Targeting early Q2 for Phase 1.
    • Phase 1- in addition Anuket will need to be refreshed.
    • Phase 2- key addition is to implement GenXcomm integrations:
      • GenXcomm with ONAP (ONAP working as a SMO)
      • GenXcomm with Magma
      • GenXcomm with Anuket
    • Phase 2 stretch goal- ONAP configuration management of 5G core and/or ORAN

Architecture and Adjacent Communities

  • Request for a 5G Super Blueprint Requirements & Use Case Advisory Group
    • The need for such a group was confirmed and formally requested during the March DTF
    • Wiki page created: Requirements & Use Case Advisory Group
    • Role: identify use cases, requirments, architecture, platform component roles and ensure alignment among the participating communities.
    • Discussion Points-
      • Community thoughts on creating this group?
      • Any additional thoughts on the role of the group? Especially from the folks who attended the March DTF.
      • How would we staff this group? one per community (ONAP, Magma, EMCO, Anuket, O-RAN, End Users, etc.)?
    • Call for Action- signup to work on this important Advisory group.
  • Proposal to use the off Tueday for working meetings
    • Perhaps we can rotate between Requirements & Use Case Advisory Group, ONAP and EMCO Alignment, ORAN Alignment teams, RAN workstream.
    • Call for Action- Anyone from these teams interested in taking the March 29 slot? Maybe ORAN Alignment per below Next Steps?
  • ONAP/EMCO Alignment updates
  • ORAN Alignment
    • Proposed starting points-
      • Look at O-RAN reference architecture
      • Sort/prioritize use cases
    • Potential workstreams- (picking up the discussion from 02/22)
    • Is there an ORAN (preferably ORAN-SC) implemention available that can be installed? Wavelabs offered to open their lab for this.
  • 5G RAN (RU + CU/DU)
    • Work that can be started now:
      • Coordination between GenXcomm, Wavelabs, UNH.
        • Kader offered to setup lab in India. Would need help setting up radio in India. off week meeting?
      • GenXcomm RAN server requirements.
        • Hardik/GenXcomm to name a dedicated resource to work 5G SBP
        • Ben will check on resource
      • GenXcomm has an ORAN implemenation that we can perhaps leverage.
      • ORAN-SC implementation - Alex Stancu can help
        • Yogen asked about recommended model. Tracy recommends a hybrid model over higherarcial model
  • Monthly Magma call- "Magma 5G- Everything you need to know". 
    • Last meeting recording: https://www.youtube.com/playlist?list=PLQ88zlc9KWGfhOZsRdtqs6UbP9vEeUExz
    • Logistics- 2nd Friday of every month 
    • Joint marketing opportunties - Heather
    • ONAP Requirements
      • Magma feature submission: https://github.com/magma/grants/issues => Issues 36, 37 and 38 have been submitted to cover ONAP Requirements
        • Here is the list of requirements to support ONAP/Magma Integration, supported by Neil Hoff (OPS 5G Customer):
          • We want to move forward with our Network slicing use case therefore we would like to know if there is any feedback on the presentation (ONAP/Magma Service Assurance Integration – KPIs) made by Jorge Hernandez-Herrero last year
          • What would be the Magma KPIs to support Network Slicing?
          • During our Integration with Magma, an issue has been identified: Magma K8s resources need to be installed in different namespaces, and therefore be split into separate Helm packages. Is there a delivery date from Magma to deliver it? thanks


Workstreams

  • ONAP/Magma Integration #1
    •  - Update from Aarna: The action item is to try workaround in Helm charts on ONAP Istanbul release. We have been facing challenges with ONAP (I release) deployment. On one ONAP deployment on the UNH server where we managed to deploy, the ONAP portal is extremely slow, and takes few minutes to respond. We are trying to install on another server but were unable to allocate new servers due to issues with UNH LaaS setup. These are finally resolved, and we are able to allocate a new server on which we will restart ONAP deployment, and then the workaround to deploy Magma with modified Helm charts. 
    •  - CBA and Helm repos. Louis/Yogen need to unstick check-in issue.
    •  - Ran out of time for update
    •  Yogendra: Working on a Helm chart issue by splitting them up. Access gateway. Small infra changes. We'll them be taking up the Magma orchestrator. Is there any specific help from Magma needed (Suresh)? Yes, that would be a great help (orchestrator charts). Suresh and Yogendra to synch offline. Helm chart fixes will require namespace changes (the ideal path). There is also a workaround to force all namespaces to be the same. The community agrees this is not the ideal long-term solution. It was requested that the Magma community, led by Suresh (Wavelabs) work with Yogen to package the Helm charts with namespace corrections as the long-term solution. Suresh to consult with Magma community if this will lead to any conflicts with Magma namespace as it exists today.
  • ONAP/Magma Topic: #2
    •  Kader - have servers and simulators. Waiting on 5G radio.
    •  
    •  - Ran out of time for update
    •  Wavelabs + Rebaca making good progress (in Wavelabs lab) on integration. Before Magma 1.7 come out, we'd like to replicate this in the community labs (by cloning). If using Wavelabs for community use, need to address some issues (e.g. jumphost set up as a trusted host). Can a jumphost be set up at Kaloom and/or UNH? Hanen/Suresh/Amar looking into it. Option may be to connect the labs. Reference- UNH lab is used for 5G resources (Amar).
  • Magma namespace changes- Namespace changes needed in Magma to resolve Helm chart issue (permanent fix)- Wavelabs/Suresh
  • ONAP/ORAN -SMO Framework workstream (Service Management Orchestration)
  • ORAN/Anuket workstream
  • 5G RAN:
    •  What workstreams can begin now that GenXcomm is onboard?
    •  Need to check in with GennXcom and determine RAN side of 5G SBP (CU/DU). Catherine suggestion: Bring this to the ORAN-SC community (Tracy + Martin). LF Staff to make connection. 

Lab Resources

  • UNH- Faraday cage in place.
  • Kaloom (Montreal) - Hanen, GenXcomm radio is currently at Kaloom lab. Hanen will talk with Ganesh. (Kaloom previously ran the UPF and fabric). Faraday cage in place
    • Missing radio parts- SW for RAN. If GenXcomm has this, then much easier to deploy
  • Wavelabs (India)-


Action Items (completed)


Any Other Business




  •  ONAP/Magma Integration - Service Assurance - KPI Network Slicing. This is being tracked by ONAP for Enterprise Task Force. Will come into play in the 5G SBP down the line.



  • No labels