Start Recording- helps facilitate minutes and Action Items
Welcome 1st Time Attendees
Documentation
Lab Architecture & Build
Secure Slicing Follow-Up & Next Steps
Lets Build!
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.
Welcome all. new attendees. If you have any questions about participating in this community, please contact Louis Illuzzi (lilluzzi@linuxfoundation.org).
Standing Motto: document as you code.... document as you build
Documentation is critical to successfully showcase and archive our work. It allows for evolution of the work to continue forward. It allows consumers to duplicate the work, and it allows participating companies to leverage the collateral and showcase the work they have done in the project.
For this demo we have to start documentation early and continuously leading off with documenting the overall architecture, labs topologies, setups, and builds, marketing storylines.
Call for documentation lead(s). The lead can be a person or company. The lead(s) will help faciliate and realize the motto; document as you code.... document as you build
ONE Summit Demo
The goal is to demonstrate end to end slicing from core to RAN
Expectations- Radio (RAN), Transport, Core slicing
Transport slicing (DoD/GovOps)
Options-
GV- proposal to put GXC in UNH and connect with a pipe. This way transport is part of the soluton.
Hardik JainAll 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).. Use Case Scenario (Neil)- Locate GXC equipment in the Kaloom lab with Kaloom UPF; this could represent a use case where you need to co-locate the UPF and RAN to get higher preformance traffic split out at an edge site. In this case the UNH lab can represent resources deeper in the network that might handle with a lower performance requirement. Demo can show slices at the Kaloom lab (edge), with core function happening in the UNH lab.
Secure slicing- Muddasar to lead
Muddasar Ahmed To provide a holistic view of security attributes, then we can decide what can be implemented in the Nov timeframe and beyond. Detail the steps and security functionality needed at every stage of the slice life-cycle. Queue this up for
Consult with Periton Labs on IoT device security
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.
Satish Sadagopan provided vision on Use Case details/definition/Architecture
Can also be folded into a safety Use Case (fire alert).
Wireline inspections for grid utilities - mobile IoT device
One camera can support multiple models
Deployment models based on Helm charts - confirm with Satish
Use of a common orcherator was discussed- Satish Sadagopan to look into this
Option- ONAP can take the place of IBM Edge Application Manager (Chaker). Showcase ONAP as a common orchestrator where any edge service can be plugged into ONAP and ONAP can support all control loop functions as well as data analytics, and collection analytics
Consider EMCO
Analytics Use Case - Muddasar- Drill down on Use Case submission
Periton Labs (David) - working on security of IoT devices attached to 5G networks (via DARPA)
Edge Computing Support (DoD/GovOps):
IoT Device Authentication at the Edge - Periton Labs has technologies for authentication and ?remote added station? at the edge.
Traffic Routing at the Edge -
Packet Filtering at the Edge - can enable device authentication at the edge
Core Options:
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)?
Finalizing overall labs architecture and topologies
What are the outstanding questions and issues that need to be addressed?
Lab architecture updates based on use case functionality needed. The ask is to update the lab diagrams with what components currently in-place/installed, in what lab, what components are pending installation, and where components need to be installed based on the Use Cases
Kaloom Status-
Free5GC Installed - do we shift Free5GC to UNH per above?
GXC RAN installed
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
Massive IoT emulator - to demonstrate the system can handle millions of IoT devices
Traffic Routing (stretch goal?) - what does the Use Case look like?
Packet Filtering (stretch goal?) - what does the Use Case look like?
Yogen thoughts:
a) Dynamic and static slicing is already been demonstrated in early version, using eMBB in last Oct/Nov. though it's not completely dynamic but mix of static and dynamic factors. b) In current state of art, static slicing for URLLC and demonstrating GenX RU/DU/CU compliant with O-RAN and UE device from IBM will be value add.
One can characterize this effort to show case following values: 1. O-RAN compliant RAN stack. 2. URLLC use case demonstration with static slicing. 3. Transport slicing (if required). 4. 5G enabling AI/ML MEC application in edge location.
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?
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
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
Kader KhanSuresh Krishnan Create requirements document capturing ONAP requirements for Magma (as discussed on 03/08). Requirements doc created
Hardik Jain dedicated resource from GenXcomm to work 5G SBP. Ben will help with resource. Rajesh Ramesh is named resource.
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.
