2025-11-19 RSAC Meeting notes

00-05

admin

@Martin Skorupski

Next meetings

• Wed 2025-11-19 8am UTC

• Wed 2025-11-26 noon UTC

• Wed 2025-12-03 8am UTC

• Wed 2025-12-10 noon UTC - canceled @Martin Skorupski OoO

05-10

M-Release

@Martin Skorupski

Please update today https://lf-o-ran-sc.atlassian.net/wiki/spaces/REL/pages/317784066 as requested by ToC. @Sridhar Rao needs infos to report tomorrow.
PLTs: https://lists.o-ran-sc.org/g/ptl-private/message/90

10-15

Versions

@bimo fransiscus asisi

https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/419725360

• updates on this page based on CVEs

• inform related project by Jira Sep 26, 2025 @Martin Skorupski

• Discussion on this page should be also “discussed” by Jira Sep 26, 2025 @Martin Skorupski

  • https://lf-o-ran-sc.atlassian.net/browse/AIMLFW-275

  • https://lf-o-ran-sc.atlassian.net/browse/INT-201

A check should be implemented if an Clould-Infa exists or not - only then deploy an Clould-Infa for SMO.

Alignment of Milestones between the projects required → AI: @Martin Skorupski

• target: AIMLFW should follow NonRtRic approach - @Martin Skorupski create JIRA or similar using https://lf-o-ran-sc.atlassian.net/secure/GHGoToBoard.jspa?sprintId=1118

15-15

O-RAN-SC O-DU integration

@Ray-Guang Cheng

O-DU LOW + xFAPI is done by Kyle @ Intel and Madhav @ Delhi University
Madhav is waiting Ankit to provide the correct repo for O-DU HIGH
Madhav will finish O-DU LOW + xFAPI + O-DU HIGH

15-25

Vision!
End-to-end use case

@bimo fransiscus asisi

SMO “one-click” deployment with selected components

• Continue with the “SMO one-click deployment” as stared by NonRtRic team (@John Keeney (Ericsson EST) )

  • Document the requirements an steps, automated and manual check points, @phani with support of all teams (NonRtRic, SMO, Tacker, AIMLFW, OAM, SIM, …)

  • rappManager first to onboard rApps

  • chartmuseum - by INT only

ES/EE rApps and End-to-end flow

• Continue work on https://lf-o-ran-sc.atlassian.net/wiki/spaces/IAT/pages/361758725 as started by INT team (@bimo fransiscus asisi )

  • PM Streaming according to spec

    • requires design and architecture - 3GPP/O-RAN - ASN.1/websocket - stream info

  • collaboration with e2e integration

  • rApp onboarding

  • integration with AIMLFW → with updates on call-flow

  • Alignment with Non-RT RIC team and SMO/Tacker team required for rapp onboarding management and automatic homing via O2.

    • ES-rApp and Profile merged by NonRtRic team - please have a look - (add reference)

Integration of “model learning” into the end-to-end flow above.

• // to be updated by Subhash

R1 compliant interface

Security

• common user management

--

Bimo has created Jira for rApp development

• discussion between Bimo and Aravindhan

  • clean-up the env by script

  • follow-up in Jira AI: @Martin Skorupski add Jira reference

Subhash

• installation along with SMO

• alignment in OWL

• share approach with Bimo

• Jira will be created by Subhash - AI: @Martin Skorupski add Jira reference

Github Action

• Matt - is your men

30-41

Q/A

@all?

Lab Requirement for O-DU integration with Tacker

@Martin Skorupski find lab… ongoing…

@ASHUTOSH MISHRA : see email - required acceleration card - srv7 to be used! @Martin Skorupski

End of the Meeting

55-55

@Ray-Guang Cheng

Activities at NTUST (Taiwan Lab)

• Presentation by @Yosafat Marselino (please see presentation in previous minutes)

• end-to-end pipeline with O2 and OAI

• testing pipeline

Open Points

• How to integrate NFO extensions from Taiwan team into NFO by Tacker Team? → Toshi

• How to integrate NFO into SMO? → Seshu

Missing function of NFO to be contributed

• O2-DMS

  • ETSI profile to O-RAN-SC repo - SMO/O2

  • How is the integration with Tacker in this case?

• O2-IMS

  • some extensions - where? to be answered by Seshu

AI @Martin Skorupski - reach out to Tacker and SMO team

Info from @John Keeney (Ericsson EST)

• SMO deployment targets deployment of tacker and/or nephio based approach - current start is nephio

• IMS in nephio implementations ongoing…

• FOCOM implementation in nephio by Capgemini
  
  

Thanks Toshi for sharing the Tacker plan: <add link here>

55-55

Different implementation for similar functions

@bimo fransiscus asisi

Alignment of similar deployments within SMO

55-55

M-Release

@Martin Skorupski

Timeline

• https://lf-o-ran-sc.atlassian.net/wiki/spaces/REL/pages/317784281

How to update

• https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333217793

• the page: Release "M" Software Versions should be referenced

  • Chartmuseum - possible solution with NodePort - Bimo to decide

    • solved - merge request in gerrit - https://gerrit.o-ran-sc.org/r/c/it/dep/+/14788

    • Chartmuseum with name local - separated from k8s due to github actions

    • pipeline under construction.

  • O-DU support k8s deployment - declaration file → N-Release?

  • Where to host a binary → AI: Martin reachout to Sridhar - what are possible solution

    • in case of private → token - where to host

    • what is the status of the discussion

55-55

Resources in OWL

@bimo fransiscus asisi

Resource Allocation

• https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16405829

Password Manager

• used of shearing bare-metal and OpenStack credentials.

• https://o-ran-sc.1password.com

• under construction

Github Actions / CI/DI and impact on OWL

• external APIs → triggered from outside

• AccessControl and firewalls software?… - Martin/Ravi

@bimo fransiscus asisi is using srv2 until Friday

55-55

N-Release

@Martin Skorupski

Just Info - N-Release → https://lf-o-ran-sc.atlassian.net/wiki/spaces/REL/pages/495878146