Versions Compared

Old Version 11

changes.mady.by.user LJ Illuzzi

Saved on

compared with

New Version 12

changes.mady.by.user LJ Illuzzi

Saved on

Key

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

...


Roadmap Refresh- updated 5G SBP Phases

  •  Off-Week deep dive meeting focus was on Road discussion: https://wiki.lfnetworking.org/x/iZ8ZB
  •  Roadmap 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

Lab Resources -

  • UNH
  • Kaloom (Montreal)
  • Wavelabs (India)

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". This meeting occurs the  
    • Logistics- 2nd Friday of every month Readout from 03/11 meeting- Kader?
      • meeting has been canceled
    • 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

...

  • 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.  - 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. 
  • 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. 


Action Items (open)

  •  Kader Khan@GenXcomm begin work setting up radio components in Wavelabs lab
  •  LJ IlluzziRoadmap refresh
  •  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
  •  Kader Khan Suresh Krishnan Create requirements document capturing ONAP requirtements for Magma (as discussed on 03/08)
  •  Hardik Jain dedicated resource from GenXcomm to work 5G SBP. Ben will help with resource. Rajesh Ramesh is named resource.
  •  Tracy Van Brakle Any link to Multi-Operator RAN from Dec 2021? Referenced on a previous call.
  •  Alex Stancu Help with ORAN implementation
  •  LJ Illuzzi- SMO Framework packages. What ONAP group is involved?  Martin Skorupskican add detail and next steps for SMO Framework

Action Items (completed)

...