2026-03-26 TSC Minutes

2026-03-26 TSC Minutes

BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94485091581?password=d137ff35-df4b-42b2-923d-cf8698b8c6f9

 

Passcode: 209247



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

Attended

Proxy (w/ @name)

Holiday

Did Not Attend

Attendance is taken purely upon #info in Zoom Chat 

@Fiete Ostkamp

DT



@Keguang He 

China Mobile

@Byung-Woo Jun 

Ericsson



@N.K. Shankaranarayanan 

Individual

@Dan Timoney 

AT&T



@Paweł Pawlak 

Individual

Guanyu Zhu (@zhuguanyu)

Huawei



@Shubham Kumar

NgKore Foundation

@Dong Wang

China Telecom







 

 

 

 

 

Antitrust Policy Notice



Agenda Items

Presented By

Presos/Notes/Links/

Status



Agenda Items

Presented By

Presos/Notes/Links/

Status



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 Board Meeting



Next meeting is May 20, 2026

 

TSC Election

@Casey Cain

No TSC Chair nominations to date. Nomination period extended to 04/09. Updated timeline below.

The ONAP Technical Community Document states TSC Chair and Co-Chair elections must take place:

image-20260122-124905.png
  • TSC Chair Elections Timeline - setup when there is a nomination

  • TSC Vice Chairs Elections Timeline - setup when there is a nomination

Once Chair and Co-chair seats are filled update onap.org: https://onap.org/about/tsc

 

ongoing

Jenkins to Github Actions Migration

&

Gerrit Repo Analysis Report

@Kevin Sandi

@Matt Watkins

@Fiete Ostkamp

 

  • 4 repos failing of 4 CI pipeline - Matt

    • Need PTL helps to merge the changes and resolve the issue

    • This week: documentation updates

    • Next week - deployment pipeline

  • CLM - Fiete raised a ticket - snapshot artifacts are missing

    • Need cleanup for java artifacts, docker snapshots need cleanup

  • PTLs to review the repo release

    • very slow movement, need to speed up this - Kevin

  • Matt- Deployment pipeline underway

    • Ramesh - Can individual projects provide requirements to help IT wit job migrations

  • Matt- Actions work completed. Pipeline work underway

  • Docs validation failures (Matt and Tom have lead). Docs jobs policy changes need to be re-looked at the adjusted. Matt/Tim to provide a readout on next meeting.

  • Matt, needs help from TSC to gain approvals @Matt Watkins to add specific request details for TSC vote. Need TSC approval for GitHub work flow policy change

  • @Matt Watkins https://lf-onap.atlassian.net/browse/DOC-831 from 12/17; Docs jobs: Python 3.8 usage, sphinxcontrib-swaggerdoc removal to permit 3.12 (and later)

  • @Kevin Sandi , asked PTLs to review the active repos list.

  • Gibhub Action Migration

    • WIP; working on dependencies (Dependabot and Github2Gerrit).

    • Plan to complete this sometime next year.

  • @Matt Watkins , testing is ongoing; some complications on gerrit and github action interdependencies; closed the gaps; continue to work on next week; getting close to the final version.

    • hopefully, by end of December? Maybe by early next year because more work to do.

ongoing

TCC / ONAP Liaison Updates





 

Release Process

 

Need to revise release RC process. Community to add details. No additional context yet.

 

Task Force Updates





 

TSC Strategy



Shankar- LFN TAC from 02/04- The Laboratory for Advanced Cybersecurity Research and Georgia Tech Research Institute presented on AI/ML for Threat Detection involving ONAP and 5G slicing.

LFN TAC Priorities: https://lf-networking.atlassian.net/wiki/x/AYC4M

 

Operations (40 minutes)









TSC Activities and Deadlines

@LJ Illuzzi

  • On the Feb 26, 2026 TSC meeting, the TSC voted to approve changing the meeting to bi-weekly.

@Casey Cain to discuss a potential time change with Casey. Need to send an email for proposed time.

 

Quebec Release Status

 

  • Release Planning: Quebec

  • RC: move to Mar 12, 2026

    • Dan- Changes on helm charts needed

    • Final images pushed. Gating environment still exists.

      • Fiete - CI runs can’t yet be validated

    • Dan- final imagines in place.

    • Fiete- gating environment broken, test failing

  • Release Sign off: Feb 19, 2026

  • TSC vote: approvedQuebec Release Key Updates , will use this as the central wiki page for the key updates

Done

Quebec Blog

 

 

Rabat Release

 

ongoing

Project Update

PTLs

PTLs can discuss technical issues at the TSC meeting

  • CPS:

  • OOM:

  • Policy: Network observability (Fiete)

  • Portal-NG:

  • SO:

  • UUI

  • CCSDK/SDNC: Dan- Deciding whether to upgrade to OpenDaylight Titanium or Vanadium release.  Will depend on when RC1 of Vanadium is available

    • Shifting to OpenDaylight Titanium

  • SDC:

  • AAI:

  • DCAE

  • MultiCloud:

  • CDS

ongoing

RelEng/Infrastructure

 

 

 

 

 

 

 

 

 

 

 

SECCOM



 

 

OOM Update

Fiete Ostkamp

 

 

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping

@LJ Illuzzi

 

 

TSC Rotation

 

 

TSC Rotation to set agenda and facilitate TSC meeting

TSC Member

Date

Dan Timoney

 

Guanyu Zhu

Feb 26, 2026

Keguang He

Mar 12, 2026

Shubham Kumar

Mar 26, 2026

Fiete Ostkamp

09 Apr 2026

N. K. Shankaranarayanan (Shankar)

23 Apr 2026

 

https://lf-onap.atlassian.net/wiki/x/PQTs

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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.