Versions Compared

Key

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

add Meeting Recording

add 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
Linux Foundation
Martin Skorupskihighstreet technologies
representing on this call O-RAN-SC OAM project (smile)
Brandon WickLinux Foundation
HeatherLinux Foundation
Alex Stancu

highstreet technologies

representing O-RAN-SC SIM project

Gervais-Martial Ngueko Tracy Van BrakleCameron ShahrarayAT&T
Parthiban NalliamudaliWavelabs
Yogendra PalAarna Networks
Suresh GorijavoluWavelabs
Hanen GarciaRed Hat
UNH-IOL (hosts the Anuket LaaS systems / infrastructure)
American Tower *
Ali TizghadamTELUS *
Satish Sadagopan Satish SadagopanIBM *
Tracy Van BrakleAT&T (O-RAN WG10, TIFG, UCTG, MVP-C)






                        

Agenda:

...

  • Cloud Native Telco Day -May
    • Abstact Overview- Thank you Amar and Hanen!


5G Cloud Native Demo Documentation Update

...

  • ONAP/EMCO alignment updates - proposals in progress from both communities
    • Put a meeting on the calendar for next week. (Wednesday)
  • GenXcomm offering 5G RAN (RU + CU/DU)
  • ORAN-SC outreachout reach
    • ORAN/ONAP call- Service mgt and orchestration. What can be reused from there? Align use cases between ORAN/ONAP/5G SBP
    • Reference: www.o-ran.org
    • Next steps:
      • dedicate meeting time to work through alignment
      • Look at Reference arch for o-ran
      • Create wiki to look at the various use cases among communities. Martin to help lead

Workstreams

  • ONAP/Magma Integration #1
    •  -
    •  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
    •  -
    •  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 Radio:
    •  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)

Action Items (completed)

...