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)
Salus RAI. https://www.project-salus.org

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

Approved this proposal by 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)
Discussed this topic with ONAP PTLs this Monday

Our proposals (Byung discussed them with Arpit, Ranny):

ONAP Organization Chart.
The ONAP projects will be semi-standalone, meaning they will 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, a uniform architecture, and strong security are maintained.
- The ONAP Documentation team will continue to provide official ONAP documentation for the time being.
The ONAP function will adopt a more descriptive namespace / prefix for external clients; the final decision will be up to the respective ONAP PTL.
OOM currently provides many useful services for ONAP projects. As a result, common services and OOM would be included by default.
- However, telecom operators may choose alternative integration options. For example, if they prefer to use their own security, secure communications and CD (ArgoCD, Flux), those 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 repos need to be separated by project - this requires further discussions with the PTLs
Currently, ONAP project functions are decoupled from security, secure communication and deployment, giving operators flexibilities.
ONAP projects will continue to be modularized, enabling sub-components to be selected at or after build time. This provides operators with greater integration flexibility based on their use cases.
ONAP projects should aim to minimize their dependencies to other projects.
- Dependencies for SDC, AAI and DCAE and MultiCloud will be analyzed.
- The respective ONAP PTLs will also analyze the interdependencies among the Portal-NG, UUI, SO, Policy, CPS and CCSDK/SDNC projects.

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

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..
- LJ Illuzzi, TSC provides three potential dates. will set up for virtual meeting event, zoom, registration... next week meeting...
- 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
- LJ Illuzzi, could you check if May 5 and May 6 are suitable for LFN?
  - Status: Wait for next week after London Event

TSC Strategy

Operations (40 minutes)

TSC Activities and Deadlines

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.

RelEng/Infrastructure

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

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 appoval
→ Wayne Dunican should get access to NexusIQ

RelEng/Infrastructure

GoLang Job issues

murali parthasarathy k

Kevin Sandi

Deena Mukundan

- Deena Mukundan, IT-27801; Kevin Sandi, please take a look at this; working on it. will merge this morning and will test it.;
  - not showing coverage; Kevin Sandi is looking for a different option; raising a ticket to sonarQube; ongoing
  - show coverage with a new solution.
  - Deena Mukundan, please test the solution; Kevin Sandi will push the solution sometime today.
  - https://sonarcloud.io/summary/overall?id=policy-opa-pdp&branch=master
- ~~NexusIQ ticket, Deena Mukundan, please raise a new ticket for the problems.~~
  - ~~IT-27927 Classification on vulnerabilities are not shown for policy-opa-pdp Nexus IQ~~
- ~~https://gerrit.onap.org/r/c/policy/opa-pdp/+/140495, merged~~
- → New Status: resolved

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements

Byung-Woo Jun

Will work on architectural changes for the semi-standalone ONAP projects
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

OOM Update

Andreas Geißler

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

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping

LJ Illuzzi

Byung-Woo Jun

Feedback from:
- KubeCon+CloudNativeCon
- Open Networking & Edge Summit
PTO
- LJ- 14 Apr 2025 to 18 Apr 2025
PTL Meeting on Eastern 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