94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

2024 TSC Recordings	2024 TSC Decisions	Anti-Trust Policy

Antitrust Policy Notice

We will 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.

Attended	Proxy (w/ @name)	Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Andreas Geißler	DT	Keguang He	China Mobile
Byung-Woo Jun	Ericsson	N.K. Shankaranarayanan	Individual
Dan Timoney	AT&T	Paweł Pawlak	CloudLinux/TuxCare
Guanyu Zhu (zhuguanyu)	Huawei
Dong Wang	China Telecom

Antitrust Policy Notice

Agenda Items

Presented By

Presos/Notes/Links/

Strategy (45 minutes)

ONAP takeaways

We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements.

LFN Quality and Security TAC

LFN TAC Update

N.K. Shankaranarayanan

New Project in LF:

ESSEDUM Framework for Model-Loading. LFN Candidate project. https://www.essedum.org (InfoSYS lead). LFN Candidate project
Salus RAI. https://www.project-salus.org. LF project, slated for LF AI&Data
LJ Illuzzi, will provide a presentation in two weeks

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

Task Force Updates

LFN Board Meeting Update - ONAP Evolution Proposal

Byung-Woo Jun

LJ Illuzzi

Ranny Haiby

LFN board approved this proposal
we have a full support from Arpit Joshipura and LFN Board
ONAP TSC, ARCCOM, OOM, PTLs and SECCOM need to formalize processes for making semi-standalone projects (architecture, CI/CD, Project Release Cycle, Normalized APIs, Security, documentation)
Byung plans to report the ONAP updates to the LFN Board in May.
See the ONAP Semi-Standalone Project Evolution wiki page for further details (coming soon).

Our proposals - ONAP TSC and PTL discussed and reached the following conclusions:

ONAP Organization Chart has been created (see below).
ONAP Semi-Standalone progress : ONAP TSC and PTL discussed and reached the following conclusions:

ONAP projects will be semi-standalone, meaning they will continue to share common governance and recommendations from the ONAP TSC, ARCCOM, OOM and Documentation teams.

The ONAP TSC, ARCCOM and SECCOM will oversee the ONAP projects to ensure best practices, architectural consistency, and strong security.
The ONAP PTLs prefer to retain the existing ONAP governance to minimize overhead.
The ONAP Documentation team will continue maintaining official ONAP documentation for now.

Each ONAP project manages its features and lifecycle in consultation with the ONAP governance committees.
ONAP functions will adopt more descriptive namespaces / prefixes for external clients. The final decision will rest with the respective ONAP PTLs.
OOM currently provides many useful services for ONAP projects. As a result, common services and OOM would be included by default.

Telecom operators may adopt alternative integration options. For example, if they may use their own security, secure communications and/or CD solutions (ArgoCD, Flux), and such choices will not be precluded.
The ONAP community plans to provide comprehensive documentation to support these deployment and integration options.
OOM Support includes: Strimzi, Istio, Keycloak, ONAP CI/CD pipeline, ArgoCD and Flux, Project build, Helm Chart repos.
The current common helm chart repository needs to be separated by project; further discussion is needed with PTLs.
DT is enhancing the OOM scripts to be aligned with their production-ready environment, but they are still open-source based.
DT is also contributing both ArgoCD and Flux CD solutions for individual ONAP component deployments, which are integrated into ONAP CI/CD pipelines.

- Currently, ONAP project functions are decoupled from security, secure communication and deployment, offering flexibilities for operators.
- ONAP projects will continue to be modularized, allowing sub-components to be selected at or after build time – offering greater integration flexibility based on operator use cases.
  - ONAP projects shall be lightweight, flexible and extensible in configuration based on the desired features
- ONAP projects should minimize interdependencies across components.

Dependencies for SDC, AAI and DCAE and MultiCloud will be analyzed.
The respective ONAP PTLs will also examine interdependencies among the Portal-NG, UUI, SO, Policy, CPS and CCSDK/SDNC.

Additional ONAP use cases and AI capabilities are being discussed among the ONAP TSC and PTLs.

China Mobile and China Telecom have contributed GenAI-related work, but their models and mechanisms are not open.
Discussions are underway around Open AI Models and frameworks, aligned with LFAID’s MOF and MOT initiatives.
ONAP PTLs were asked to explore possible AI integration into their projects
Disucssions are ongoing on how to create solutions that leverage individual ONAP component functions.

China Telecom has forked a “Lightweight ONAP platform” for its 6G research.
China Mobile plans to contribute a new MaaS (Model As A Service) AI capability to the ONAP Paris release.

DT and OdineLabs/TurkCell have chosen ONAP components for service orchestration.

In the DT cases, selected ONAP components are being included in their O-RAN-TOWN project.

O-RAN SC also plans to adopt ONAP functions.

Note that O-RAN SC would be very selective about the code from ONAP, according to O-RAN SC SMO PTL..

==============

Ranny Haiby,

The concept of elevating ONAP modules to semi-standalone entities was presented to the board and got positive feedback. One request that did come up was to clarify the evolution of the integration tests that are currently part of the ONAP-wide release process (will they still exist in some form to ensure interoperability between the independent modules?). The next step would be executing the necessary changes in the ONAP CI/CD system. I see that @Byung-Woo Jun already has a sessions planned for the ONAP DTF Day (https://lf-onap.atlassian.net/wiki/x/mICKBg) to discuss the next level of details. @LJ Illuzzi and I will of course support from the LF side.

Also, credits go to Ciaran Johnston and Christian Olrog
Byung-Woo Jun,

At the ONAP DTF days, I plan to present the ONAP TSC roadmap and Architecture evolution, covering this concept. Working with DT and other ONAP participating companies, I have outlined how ONAP will enable the individual build and deployment of ONAP components under the ONAP Streamlining evolution; i.e., ONAP already supports these capabilities.

The current OOM enhancements led by Andreas Geissler for ONAP CI/CD and ONAP architecture, leveraging Argo CD were tested during the Oslo release by DT and ARCCOM. Now, DT plans to contribute to ONAP CI/CD further by using both Argo CD and Flux during the Paris release. Additionally, China Telecom, China Mobile and DT have integrated several core ONAP components, referred to as Lightweight ONAP solutions, for their 5G and upcoming 6G.

Over the past couple of years, under the ONAP Streamlining evolution led by me (Byung), we have established a solid foundation, which has proven to be valuable.

Furthermore, ONAP TSC and ARCCOM have already discussed the possible integration solutions by leveraging individually built ONAP components. We are currently in the process of formalizing integration procedures and developing use cases for higher-level solutions. Additionally, I proposed the Runtime CI/CD for ONAP, and it will be part of my ONAP DTF Days presentations.

I fully agree with this direction, and we are proud of the foundational work achieved through this evolution. More to come… We have seen the future 😊

I plan to present the evolution to the ONAP DTF Days, and I look forward to collaborating with you all.

Kudos to all ONAP contributors!!! Thanks!
We need documentation for formalizing this new evolution. such as each each project documentation, API, security, release cycle, etc.

ONAP DTF Days 2025

Byung-Woo Jun

LJ Illuzzi

Byung-Woo Jun, created a page for ONAP DTF DAYs 2025; we plan to collect ONAP DTF session topics here before presenting them to LFN, and schedule for the event.
- Finalize the session topics and event schedule - TSC plans to decide today..
- We are aiming for early May as the target timeline. We plan to have a 2-day ONAP DTF event, taking multiple time zones in account;
  - e.g., scheduling our sessions from 8AM EDT - 11 AM EDT (12PM UTC - 3PM UTC) each day
- Pre and Post Marketing
  - The LFN team recommends May 13 - 14 to allow more time to promote and setup.
  - Who is the target audience? Existing ONAP contributors? new contributors/companies, both? both
  - Pre-event teaser video? Can the community create this? Sunny will provide a template.
  - Pre-event blog. Blog template: https://docs.google.com/forms/d/e/1FAIpQLSc1Dmp8kQfN8n2eVcFdI19p9P1-ZzLbQGSSqih3abqWsXTZew/viewform; Sunny will provide a template
  - Utilize LFN media channels; Sunny will handle this
  - Promote within the LFN TAC; Byung will report the ONAP DTF event ; Louis will add an agenda for this.
  - LFN can provide a community promotional kit that community members can use to promote the event within there company and there network.; Sunny will provide the kit
  - Registration. LJ Illuzzi
- TSC approved the ONAP DTF Days 2025 on May 13 - 14.

ONE Summit Summary

Byung-Woo Jun

ONE Summit: seeOpen Networking & Edge Summit 2025 Schedule & Directory

AI-RAN by Alex Jinsung Choi, AI-RAN Alliance, SoftBank Corp. : https://static.sched.com/hosted_files/onesummit2025/87/Linux Foundation Open Networking and Edge Summit 2025_Alex Jinsung Choi.pdf?_gl=1*15q9wq1*_gcl_au*MzI4OTA3MTU1LjE3NDM5NzY0MDk.*FPAU*MTQ4NTA4MTMxMy4xNzM2NTE1MDA0
- AI-RAN and Open Source: Building Scalable Dataset Pipelines for AI Training
- Accelerating AI development for RAN optimization and automation
- The evolution of Telecom networks into AI platform
AI - Lessons learnt from CMCC by Dr. Junlan Feng
- Challenges understanding and hallucination collaboration vs. AI ton enable large scale complex system
- Evolve to level 4 advanced autonomous network by 2025
- Build AI platforms to address network complexity, shorten innovation cycles, and lower R&D barriers
- Unified portal; automated closed loop; from invisible to visible ; world model aided RAN parameter adjustment and evaluation
- Inference aided handover parameter, adaptive multi-receptive field spatial temporal graph network for traffic forecasting;
- Injecting global information into independent channels for long time series forecasting; graph-based decomposition approach for cellular traffic prediction; human trajectories generation based on variational point processes
- New model of open collaboration for AI+Network
OMDIA: an industry analyst’s perspective on Telco Cloud
- Network functions becoming cloud native
- Moving from ETSI NFV to GitOps-based frameworks
- Cloud-native as enabler for autonomous networks
- Moving to a horizontal cloud for IT and network functions
EdgeAI by STL Partner
- $100 billion opportunity; the edge AI leverages edge computing for certain AI workloads
Network Infrastructure to APIs - how Open Source enables speed of invocation and monetization by DT
- Why does DT build a SMO platform based on ONAP?
- History of T-NAP / TaaS OS evolution, including ONAP, along with O-RAN SMO
- https://static.sched.com/hosted_files/onesummit2025/ae/ONES_DT_NR_SZ.pdf?_gl=1*kkfjpc*_gcl_au*MzI4OTA3MTU1LjE3NDM5NzY0MDk.*FPAU*MTQ4NTA4MTMxMy4xNzM2NTE1MDA0
- Vendor independence, network differentiation, short lifecycles …
- use of CAMARA, Aduna, others
InstantX: Vodafone’s edge innovation for the future of Telco
- Safer transport for Europe Platform (STEP) - Vodafones enterprise V2X (vehicle to everything) service
- InstantX - Vodafones projects with LF Edge - ensuring the secure and reliable exchange and distribution of data in real-time between users in a certain geography
IOWN Global Forum and Open Source - Key enablers for next decade by IOWN Technology Director
- IOWN global forum’s areas of activity
- an industry consortium established in 2020 by NTT, Intel and Sony
- Open all-photonic network (APN); Digital Twin computing; Cognitive Foundation, integrating AI and ML for network
AI Framework for Networking and Responsible AI by Infosys
- Why AI for Networking and a Framework? ; roadmap towards digital brain (plan & design slice, testing slice, assurance slice) thru agents;
- Why responsible AI? ; Enhanced security, data privacy, explainable AI, Fairness/Bias mitigation, Versatility)
- E2E framework approach for AI in networks
Open Networking Operation System for all, by Peter Plak from Dell Technologies
- Dell networking use cases including ISG, DC to Edge, merging AI fabrics
- SONiC use cases in Microsoft; Kubernetes based SONiC Device Management; AI Traffic characteristics and solutions
AI 101 for Networking and Edge by Fatih Nar - RedHat, Ranny Haiby - LF
- AI adoption for networking and edge computing is accelerating
- Enterprise AI use; Real world AI consumption Example, DeepSeek Impact using MoE (neural network design where only a subset of model components (called experts) are activated for a given input
- Agentic life; deployment architectures (Centralized vs. Distributed, Hybrid with workload assessment & placement)
- Security is not an external component; Telco-AIX; Ent-ObX (Observability experiments); Domain Specific AI
Panel discussions: Spotlight on innovation: the latest developments shaping open source networking (Lingli Deng - CMCC, Olaf Renner - Nokia, Ciaran Johnston - Ericsson, Ranny Haiby - LF)
A journey towards automated Telco Cloud by Odline Labs, Turkcell
- their Telco Cloud Automation architecture, including ONAP
- Why do they choose ONAP? ; Alignment with ETSI MANO; Open-Source, vendor-neutral benefits, Active community and roadmap, new modular architecture - ONAP streamlining, ONAP’s capabilities on orchestration, policy, closed-loop automation, synergy with other LF projects and AI roadmap
- Architecture:
- Expectations from the ONAP project and community
  - better CNF lifecycle support (helm, k8s-native orchestration, simplified onboarding workflows and model tooling, enhanced modularity and testability
  - More hands-on tutorials and quick-start guides, alignment with ETSI MANO evolution, Foster feedback channels between users and developers, promote interoperability across ecosystem tools
LF - Horizontal and vertical foundations, panel discussion Dr Junlan Feng from CMCC, Johnne Sominent from Nokia, christian Olrog from Ericsson, Arpit Joshipura from LF -
- relationships (manufacturing, energy, gas, commerce & retail, automotive, Fleet & transportation, building automation, cities & government
- LFN, collaboration hub for opensource networking, edge and access
- Pushing local innovation with global collaboration - all built off open standards and open source
- APAC & China: Networking contribution / leadership
- India strategic drivers - LF India launched in Dec 2024 to enable India’s growing open source ecosystem across telecom, blockchain, edge, security, cloud
- EU Open Source Networking Drivers - DT deploys ONAP in O-RAN TOWN, CAMARA, 6G SNS, Sylva
- Technology 2025 - reality check; cloud-native is in over 2/3 networks/product deployment, domain specific AI focus on AI frameworks and data sharing (2 new project in LFN Essedum, LF Salus)
- Edge - Cloud continuum & AI+data at Edge are two main focus areas
- Network monetization with CAMARA APIs reaching peak awareness and early adoption

KubeCon + CloudNative Con Summary

Byung-Woo Jun

Byung will provide its summary soon.

2025: AI-Native Kubernetes - It’s no longer question about whether Kubernetes can run AI — the community has proven it can and made it practical and performant.
A focus is how do we run AI well – at scale, with governance and without waste.

Kubernetes AI day: GenAI & ML in the CloudNative Ecosystem by Zalando,
- GenAI autonomous Agents, cloud native agents
- ML Security, MLOps monitoring
CNCF AI Ecosystem & Working Groups (WG AI, WG Batch, WG Serving, WG Device Management, WG WASM)
Gateway AI inference extension (diff between web traffic, genAI traffic)
Cloud Native + Kubernetes AI Day summary, KubeConCloudNativeCon2025-London-Summary.pdf

TSC Strategy

Operations (40 minutes)

TSC Activities and Deadlines

LJ Illuzzi

Byung-Woo Jun

Next LFN Board meeting is May 7, 2025. Whats needed:

2025 Priorities
2025 Q1 accomplishments and work item status. i.e Oslo, Paris, Evolution, D&TF, etc.
Community member to speak and represent ONAP on the board meeting
- Byung-Woo Jun, will present ONAP updates to LFN Board: due date: April 28-29

Paris Release Status

Byung-Woo Jun

The next Paris release schedule is TSC approved on 05 Dec 2024 , Release Planning: Paris
- TSC approved the current Paris release schedule on December 5th
- An ArgoCD and Flux deployment to provide an alternative the helm deployment
- RAN Simulator enhancement
- Policy-OPA-PDP
- MAAS
- SDC Ruby upgrade - will be removed
- Project package upgrade
- SDNC/CCSDK - need to upgrade Java 21 and Maven ; PTL, SECCOM and ARCCOM will handle this
- not only SDNC, may be other components too. SECCOM will discuss
- Portal-NG upgrade?
Release Planning: Paris
Project Status in Paris Release
Paris Release Key Updates
Long Term Release Roadmap

Software Package Upgrade

SO-4130	SO PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR PARIS RELEASE	Seshu Kumar Mudiganti	Open	Unresolved
SDC-4690	SDC PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR PARIS RELEASE	Fiete Ostkamp	Open	Unresolved
MULTICLOUD-1507	MULTICLOUD PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR PARIS RELEASE	Andreas Geißler	Open	Unresolved
DCAEGEN2-3414	DCAE PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR PARIS RELEASE	Andreas Geißler	Open	Unresolved

Note: Andreas Geißler is looking for resource for DCAEGEN2.

Policy Frame and OpenSSF Tool Issues

Ramesh Murugan Iyer

open a ticket for LF IT for tool fixes, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-28024; Eric Ball
Policy ticket update to LF IT on the github, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27673; Matt said it is resolved

RelEng/Infrastructure

On hold until Dan and Eric have additional info/research.

Dan needs to provide additional info to Eric.

We need to have a tool to analyse the code and provide information about certain type of cryptography used. Pawel - to open a ticket for that at LF IT.

https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27835 ,

Need to add scanning for ONAP repos to provide information about certain type of cryptography used

Eric Ball
Latest comment from IT Support from 03/07-
Still not a lot of detail here, but I took a look for things that would fulfill this general description. Mostly, there are plenty of ways to find outdated crypto, since that's a security risk that many static analyzers can pick up. But in terms of findinganyinstances of cryptography use, I haven't seen anything that would fit the bill.
Tony Hansen
02/28-
We've been talking about post-quantum cryptography support in ONAP. We will need to make sure that everywhere in ONAP there is something cryptographic used, it is already using a post-quantum algorithm or can be modified or reconfigured to use a post-quantum algorithm.
So this requires us to identify everywhere in ONAP that uses any sort of cryptography. This includes encrypting files or streams, using certificates, and using cryptographic hashes.
Pawel and Amy can comment more.
Asked Eric Ball to have a quick sync-up meeting with Pawel, Amy, Tony for a speedy resolution.
Paweł Pawlak informed: Amy Zwarico shared info for package update...
Eric Ball to provide his findings around tools propossed by SECCOM

@Byung's note and email to Dan Timoney:

@Paweł Pawlak created the ticket, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27835, for adding a scanner for ONAP repositories to identify the type of cryptography being used.

During the ONAP TSC meeting today, Eric, Pawel, Tony, Andreas and I discussed the following steps:

Eric mentioned that he could not find any tools specifically for scanning curren cryptography usage
Tony suggested guidance
Amy Zwarico suggested using the Infosec Global (ISG) tool to identify the crypto used in ONAP software
Muddasar Ahmed suggested looking into SemGrep and CodeQL for code scanning for crypto functions
Eric plans to review and test the suggested tools
A key question is: which ONAP repositories should Eric starts with, instead of scanning all the ONAP repositories?
Andreas Geissler recommended starting with CCSDK/SDNC, since they are based on OpenDayLight, which likely contains relevant cryptographic logic.

@DAN, since you are familiar with the substructure of the CCSDK/SDNC repositories, could you please points out which specific repositories Eric should begin with?

RelEng/Infrastructure

~~Open Ticket for LFIT to get approval of TSC: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27876~~

~~"Security Masters" can be assigned to get access to the NexusIQ by the PTL and do not need TSC approval~~
~~→ Wayne Dunican should get access to NexusIQ~~
~~We don't need to vote every time.~~

RelEng/Infrastructure

GoLang Job issues

Kevin Sandi

Deena Mukundan

https://sonarcloud.io/summary/overall?id=policy-opa-pdp&branch=master

NexusIQ is ongoing; Kevin Sandi, any update? still waiting from the vendor; not much we can do...

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements

Byung-Woo Jun

work on architectural changes for the semi-standalone ONAP projects
- New architecture diagram is coming for ONAP semi-standalone evolution
ARCCOM is working on the ONAP marketing catch points and architecture for the Paris release.
- https://docs.google.com/document/d/1_MTqJDP8QyJwYUyxzDsCoxbUlJsb3Ec_S3xE4Q97HP4/edit?tab=t.0
PTLs, please plan for the ARCCOM reviews for your new features, requirements and enhancements for Paris.
More ONAP Streamlining documentation, ONAP Streamlining Evolution and its sub-wiki pages.
Runtime CI/CD collaboration and discussions with participating companies.

SECCOM

Paweł Pawlak

We need to check other ONAP components with GUI, such as UUI, SDC-FE, SO-FE.
Andreas provided the list of the Java versions per project. versions_reporting.html ONAP-Component-Java-Versions_Reporting..pdf
- AP: Dan Timoney, try it with SDNC to build basic image automatically regularly and update Docker file as needed. He will try it and let us know.
  - Dan will share his testing results with us.
  - Dan Timoney - recreate new documents; presentation to PTLs in April
- Dan Timoney will present the result to PTL next week.

OOM Update

Andreas Geißler

ongoing
ArgoCD deployment is working;
Connectivity issues between DT and nexus3
Matt: Check the possibly to push images to docker.io

Use of ONAP Components in O-RAN SC?

Byung-Woo Jun

CCSDK / SDNC is used in O-RAN SC OAM
O-RAN SC would be very selective about the code it adopts from ONAP.

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping

LJ Illuzzi

Byung-Woo Jun

Feedback from:
- KubeCon+CloudNativeCon
- KubeCon+CloudNative AI day - summary is done.
- Open Networking & Edge Summit - summary is provided
PTO
- LJ- 14 Apr 2025 to 18 Apr 2025
PTL Meeting (Apr 21) on Easter will be dropped

Zoom Chat Log

Zoom Meeting Recordings

Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative! Information as to why .
They are included here as a time stamp cross-reference for the recording only! The notes above this line and the actual recordings are authoritative.

Browser not supported