Versions Compared

Key

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

Meeting Recording

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

                        

Proposed Agenda:

  • Start sending formal Invitation (using the mail list calendar) to invite community members to add to the bi-weekly Agenda
  • Start Recording- helps facilitate minutes and Action Items
  • Antitrust
  • Welcome 1st Time Attendees
  • Marketing Update
  • 5G Cloud Native Demo Documentation
  • LFN Developer and Testing Forum, January 10-13, 2022 (virtual event) - recap
  • Architecture:
    • US Navy Use Cases
    • Orchestration Blueprints
    • Need RAN vendor
  • Reset Plan and phases for 2022 (proposal)
  • Workplan Updates
  • AOB

###################################

...

Welcome all. new attendees. If you have any questions about participating in this community, please contact Louis Illuzzi (lilluzzi@linuxfoundation.org).Marketing Update


5G Cloud Native Demo Documentation - underway

  • Community participation & input will be key to success
  • Status: Writer team (WaveLabs) working with Aarna Networks team on developer interviews
  • Next Steps:
    • Interviews: Kaloom, Red Hat, A10, Cap Gemini Engineering, Turnium, GenXComm, Intel, UNH
    • Rebaca documents previously provided. Any other documentation opportunities from Rebaca?
  • Reference:Community participation & input will be key to success


LFN Developer and Testing Forum, January 10-13, 2022 - Recap

...

  • US Navy Use Cases:
    • In a centralized site, they want to use ONAP for the 5G SBP

    • For remote/smaller sites with limited IT staff, they want something lighter. So they want to go with EMCO.

    • There is also the issue that remote sites may not always have good connectivity. So in that case, ONAP will be the global orchestrator in a central site. EMCO will be the edge domain orchestrator. When connectivity is there, ONAP can manage EMCO as a southbound controller.

    • Next Steps: architecture diagrams, and end to end flows. ONAP + EMCO + Magma meeting then include Anuket.
  • US Navy use cases above as well as demostrations demonstrations from DTF lead to 4 potential 5G Orchestration Blueprints:
    • Magma with ONAP CNF Orchestrator
    • Magma with EMCO
    • Magma with ONAP (global orchestrator in a central site) and EMCO (edge domain)Free5GC with EMCO. Roadmap item. Navy Resources?
  • Need RAN vendor - community input. Qualitifcations? Criteria? Help grow ORAN. Explore vendor(s) in ORAN community. Bob M. can help.
  • ONAP Honolulu vs Istanbul. Current testing with Honolulu. Continue with Honolulu, then move to Istanbul
  • Use Case: Private LTE Network security. Need Magma and ONAP SMEs
    • Kader/Wavelabs can help with secure aspects with slicing and private mobile network. Setup separate call. Include Neil Huff. Need R&D from Magma.
  • 2 flows: EMCO under ONAP and EMCO standalone (SA)
  • Anuket as cloud infrastructure
  • Rebaca interop testing / synch with Wavelabs (Kader/Samir)
    • Show Magma/ABot testing on 11/30
    • End to end slicing- pickup where it was left off on 5G demo. Issue with firewall may be key issue. Jamie, Constanten, Jason, Samir. Samir to update on Nov 30.
  • Physical radio integration: Is the RAN ready for testing on GenXcom? Cap Gemini/Intel to confirm (Sam/Utkash).
  • Consider other RAN options


Reset Plan and Phases for 2022 (proposal)

  • Phase 1: Magma + EMCO + Anuket - integration complete (ABot pending)
    • Next steps: blueprint creation, documentation/cookbook, ONEEF collateral (tentative in April, virtual)
  • Phase 2: Magma with ONAP CNF/VNF Orchestrator+ E2E + MEC
  • Phase 3: 5G Slicing + ORAN SC + MEC
  • Phase X: Magma with ONAP (global orchestrator in a central site) and EMCO (edge domain)


Workplan -

  • ONAP/Magma
    • CBA development to automatically register the Magma AGW with the Magma 'Controller' is complete
    • Trying out the Magma Helm Chart workaround while Wavelabs works on updating the Helm Charts
      • On the Helm Charts, there are two paths: short-term (Aarna) Yogen will try to workaround forcing the namespaces to be the same. Long-term fix; K8s resources need to be installed in different namespaces, and therefore be split into separate Helm packages (Wavelabs). The long term fix is a best practice offered on ONAP for Enterprise community and should be documented.
  • Slicing-
    •  Kaloom was able to fix the firewall issues and now we have the high and low video use case working through the 2 different slices
      • Next Step: gather requirements for slicing. Working with the Magma team.
  • Radio
    • GenXComm Radio. Can we start using it? Intel/integration issue. GenXComm coming on as a member.
  • Labs for 2022: UNH Solid, Kaloom still on board? Do we need CENGN?
    • Louis reached out to Kaloom for documentation above and broach lab question.
  • Rebaca/Magma:
  • Document as you build

  • Placeholder - Do we need separate call for 5GSPB phase Next for execution?  (similar to weekly 5G Cloud Native Network demo). Alternate Tuesdays?

...

  • ONAP + Magma (orchestrate Magma CNFs using ONAP) - See Above
    •  see Workplan above
    •  
      • Aarna moving to ONAP Honolulu for this work.
      • ONAP Istanbul is due out on Nov 4. This release brings improvements for deployment and day2 of more complex CNFs. What is the LOE to move from Honolulu to Istanbul? Or wait for Istanbul?
    •   - Pending Seshu meeting.
    • ONAP+Magma integration- issue at TOSCA packaging level. ONAP community to assist in debugging TOSCA issues, starting 08/25. Helms charts working
    • Enterprise Task Force (Amar, Prabhjot, Siraram, Catherine, Kader, Phil)
    • Meeting Details Here: https://wiki.onap.org/display/DW/TSC+Task+Force%3A+ONAP+for+Enterprise+Business
    • Align with ONAP + Magma Milestones / Timeline
    • Onboard Magma Controller (gateway) with ONAP (currently as VNF)
    • Network Slicing. Reminder: Monthly meeting on how to align with other communities, address pain points. Next meeting: Friday, Aug 13, 10-11 AM CST time. Details in Magma community calendar: 

      https://calendar.google.com/calendar/u/0/embed?src=c_gbiu1t7a67ika1th2smldeh19s@group.calendar.google.com&ctz=America/Chicago 

    • Networking Slicing Meeting last week including security efforts, breaking out into a separate meeting series. Working toward service assurance kickoff based on Magma capability. Meeting Details Here: TBD

...