/
TSC 2025-01-16

TSC 2025-01-16

BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

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.

AttendedProxy (w/ @name)HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

DT
China Mobile
Ericsson
Individual
AT&T
CloudLinux/TuxCare

Guanyu Zhu (zhuguanyu)

Huawei


China Telecom



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 Cross-Organization Updates

MAC, SPC, TAC, EUAG, LFN Board



TCC / ONAP Liaison Updates



Task Force Updates



TSC Strategy

Byung-Woo Jun

TSC

From the Paris release, TSC needs to discuss ONAP focus areas and strategies / roadmaps

    • TSC members to add thoughts

Let's discuss more this year for Paris +

Byung-Woo Jun plans to present the brainstorm next week at the TSC meeting.

Brainstorm:

  • Ensure ONAP core components are focused and operate independently, from build to runtime
    • DT finishs Argo-CD based component independent deployment
      • Argo-CD is a DT choice, but ONAP can allow other CDs, e.g., Flux (need contributors)
      • DT plans to productize some of the selected ONAP core components early next year in their TNAP production environment
    • Declarative and Intent-based component operations by the Repository-based Network Automation : see the ideas from ONAP Architecture Evolution - Ideas (November 2023)
  • Make ONAP core components more autonomous and ready for use by both ONAP, LF and other external users
      • During New Delhi and Oslo releases, CPS and Policy achieved the OpenSSF Gold Badging status. Kudos to the team!
      • Continue to promote/facilitate other ONAP core components for the Gold Badging status (e.g., UUI, SDNC)
  • Incorporate more GenAI capabilities and use cases to the ONAP components, and promote the adoption of open-source LLM models and frameworks aligned with LF AI & Data and GenAI Commons
    • Collaborate with LF AI & Data GenAI Commons and Nephio GenAI for 5G and 6G
    • Open-source based models and controls
    • AI-Based Control Loop
    • AI Model-As-A-Service 
    • ETSI ISG NFV compliance for AI?
  • Foster inter-community collaboration with other LF communities, such as O-RAN and Nephio
    • SDNC enhancements (which is used by O-RAN OAM as is)
    • Resource-based Orchestration Pattern (leveraging CD and Operator)
    • Energy saving / monitoring 
  • Ensure the security of ONAP components and operations 
    • The latest security mechanism for communications (service mesh enhancements leveraging Istio and coming Ambient Mesh)
    • Deprecate unused sub-components and mitigate security vulnerabilities
  • Define a secure LFN CI/CD pipeline by leveraging OpenSSF-associated reference tools

Operations (40 minutes)








TSC Activities and Deadlines

LJ Illuzzi

PTL Updates

Dan Timoney

Andreas Geißler

Kevin Sandi

Byung-Woo Jun

    • Done; created new images and OOM patches with new SDNC and SO versions. 
  • Any more OOM update for Oslo?
    • some small issues with MariaDB, but fixed. Small patches on policy helm charts; the fix is part of Oslo.
    • OOM doc is done.
  • Thomas Kulik, any update for this? https://docs.onap.org/en/oslo/release/index.html 
    • All changes are done. Some repositories are missing; not sure we need branches. e.g., UUI, SO. SDC (no need), Portal-NG (wiill do branch) and A&AI (will do branch), DCAE2 (need branch). 
    • cherry-picks; compiling overall release note (Byung will send the note summary to Thomas by end of today).

Oslo Release Status

Byung-Woo Jun

LJ Illuzzi

Thomas Kulik

Andreas Geißler


    • What is the current status?
        • There is a branching issue.
        • TSC voted to postpone sign-off date to Jan16 (Chat vote)
    • Any documentation update will be done between the RC and Sign off (Jan 16)
      • ARCCOM
      • OOM
      • CPS
      • Policy
      • Portal-NG
      • CCSDK/SDNC
      • SO
      • UUI
      • ...
    • TSC approved a vulnerability exception for some projects; Package upgrades for vulnerability mitigation will be handled in Paris
    • SDC Ruby update is postponed to Paris
    • PTLs need to issue Release Candidate Jira tickets for their projects
    • Release Planning: Oslo

    • Project Status in Oslo Release

    • Oslo Release Key Updates,  thanks PTLs

Paris Release Status

Byung-Woo Jun
  • The next Paris release schedule is TSC approved on  , Release Planning: Paris 

    • TSC approved the current Paris release schedule on December 5th

    • An ArgoCD deployment to provide an alternative the helm deployment

    • RAN Simulator enhancement
    • Policy-OPA-PDP
    • MAAS
    • SDC Ruby upgrade
    • Project package upgrade
    • SDNC/CCSDK - need to upgrade Java 21 and Maven ; PTL, SECCOM and ARCCOM will handle this
  • Long Term Release Roadmap

GoLang Job issues

murali parthasarathy k

Kevin Sandi

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements

SECCOM

Paweł Pawlak

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping

LJ Illuzzi

  • KubeCon+CloudNativeCon, and Open Networking & Edge Summit, next April 2025 in London
  • LFN DTF - not yet; a week from next Monday, LFN will discuss the LFN DTF schedule.
  • Open Networking & Edge Summit Registration: https://events.linuxfoundation.org/open-networking-edge-summit-europe/register/
    • There are no community sessions for this event. It’s a 100% curated agenda. There will be keynotes by LFN and LFE, and strategy sessions.

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.