Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
We start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Agenda
START RECORDING
Duration
Agenda Item
Requested by
Notes / Links
Duration
Agenda Item
Requested by
Notes / Links
30 mins
Cross-project discussion
This meeting is reduced to 30 minutes
host: @Byung-Woo Jun
O-RAN OSFG Fall 2025 Workshop
@Byung-Woo Jun
@Byung-Woo Jun , presented the ONAP status and ongoing work in relation to O-RAN activities at the O-RAN OSFG Fall 2025 Workshop. The focus will include ONAP semi-standalone projects and individual deployments that can help facilitate adoption within OSC.
SDNC and OOM can be used in OSC
A GitOps-based onboarding plan could be an interesting approach to ensure consistent architecture across LFN.
Reports:
As you know, the O-RAN OSFG Workshop was held last week at UNH, where I presented the topic of ONAP and OSC SMO collaboration (see attached).
@Byung-Woo Jun presented it in a way that would capture the attention of the OSC key players. Based on the feedback and discussions, it seems our work is being recognized and appreciated by the OSC leadership. Notably, David Kinsey and others suggested moving the OSC SMO functions into ONAP - leveraging ONAP functions for OSC SMO. More discussions are needed, but this is now a real possibility.
From my perspective, the current OSC SMO continues to face challenges in producing high-quality applications and lacks robust security support. I highlighted that ONAP’s modular components are already close to production quality, with flexible pick-and-choose capabilities. For example, DT has elevated several core ONAP components to production grade in their environment. I also emphasized that the ONAP security architecture (Service Mesh, Ingress Gateway, etc.) could significantly enhance the quality and reliability of the OSC SMO if adopted.
We’ll see how things develop from here.
Expecting some discussions between the ONAP PTLs and TSC and the key OSC stakeholders.
ONAP TSC LFN Budget 2026
@LJ Illuzzi
We are working on the 2026 LFN budget. Each LFN project is asked to provide budget requests for specific line items the project will need. This is the same process that has been used in the past and I added some input below. The LFN Board will be reviewing and approving the budget on its Oct 24 meeting.
Target completion by Oct 9
Category
Change from 2025 Same $/ More $ / Less $
Priority H / M / L
Notes, Explanations, etc.
Infrastructure requests
Same
M
GPU environment for GenAI and AI-driven orchestration
LF IT support (releng, sysadmin)
Same
H
Community Awards/Recognition
Same
Motivate ONAP contributors
Mentorship Program
Staffing (TPM, RelMgr, etc.)
Same
H
TCA support remains the same
Other
DoD & Georgia Tech AI-based Anomaly detection
@Byung-Woo Jun
DoD & Georgia Tech’s AI-based 5G anomaly detection demo, leveraging ONAP DCAE and other related components, is scheduled for the SECCOM meeting on September 30th.
@Toine Siebelink , can we test documentation that is associated with tags
tags can be removed for testing
@Matt Watkins , @Kevin Sandi can help for the removal
@Fiete Ostkamp , Once the guthub action migration is done, the contributor can focus on github, without worrying about jenkins and others? good points.
@Muddasar Ahmed , we may need to write a document to explain the changes related to semi-standalone projects. - WIP
DT and other operators' feedback is important.
“Notebook LLM” by google, try to use - summarize outline
Working with Matt - need more understanding and investigation - WIP
@Matt Watkins , github and rtd ; three tickets are opened - completed.
