Invitation to Collaborate on the Agenda and Discussion Topics
Marketing Update
5G Cloud Native Demo Documentation Update
Roadmap Refresh
Architecture & Adjacent Communities
Proposal for 5G SBP Requirements Advisory Group
Proposal for Every other Tuesday
Workstream Updates
Action Items
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).
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.
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
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
- 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).
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.
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.