Versions Compared

Old Version 19

changes.mady.by.user Heather Kirksey

Saved on

compared with

New Version 20

changes.mady.by.user Catherine Lefevre

Saved on

Key

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

...

...

  • Proposal for 5G Super Blueprint Requirements Advisory Group
    • Proposed Role (draft): identify use cases, requirments, architecture, platform component roles
  • Proposal to use the off Tueday for working meetings - Tuesday 03/15 is DTF
  • ONAP/EMCO Alignment updates -
    • Followup meeting held on March 2- The ONAP and EMCO teams shared and are comparing notes to continue to hone in on alignment areas.
    • Next Steps:
      • Next call March 10, then the DTF sessions the week of March 14.
  • ORAN Alignment
    • Dedicated meeting to work through use cases and alignment. (MWC avoidance)
    • Proposed starting points-
      • Look at O-RAN reference architecture
      • Start putting together use cases among open source communities - Martin
    • Potential workstreams- (picking up the discussion from 02/22)
      • Plugfest (June 2022) focusing on 5G SBP and Multi-Operator RAN (reference Dec 2021- Multi-Operator RAN- Tracy)
  • GenXcomm offering 5G RAN (RU + CU/DU)
    • Work that can be started now:
      • Coordination between GenXcomm and UNH.
      • GenXcomm RAN. server requirements.
  • Monthly Magma call- add details and logistics
    • Joint marketing opportunties - Heather
    • Catherine- need awareness on requirements. 1. Submit to community directly, 2. Work with Wavelabs.
      • Catherine to resend specifics of requirements
      • Magma feature submission: https://github.com/magma/grants/issues
      • 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


https://www.linkedin.com/posts/kaderkhan_decoding5gzone-activity-6902687793781231617-EEFO


Workstreams

  • ONAP/Magma Integration #1
    •  - CBA and Helm repos?
    •  - 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
    •  
    •  - 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).

...