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
30 mins	Cross-project discussion		This meeting is reduced to 30 minutes Rotating host volunteer for this week: Paweł Pawlak / Byung-Woo Jun
	CLM Jenkins jobs are failing	Paweł Pawlak Amy Zwarico	~~Nexus-IQ was not stable, Jira was opened: IT-26799 CLM Jenkins Jobs Failing.~~ ~~The ticket is closed now. According to Amy, if needed, she will reopen a new ticket.~~ ~~Progress - not all jobs are failing. Pawel's access to CLM reports was lost - Jira was opened for that: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26825~~ ~~The ticket is closed now. Need to double-check it with Pawel~~ ~~CLM jobs were removed for deprecated projects. For details, see TSC meeting, TSC 2024-06-27~~
	Oslo Release update	Byung-Woo Jun Ramesh Murugan Iyer	Oslo related Wiki under creation by Byung, Release Planning: Oslo Project Status in Oslo Release O-parent removal from Oslo?? Ericsson presented their O-parent removal experience last TSC meeting Preparing for its instruction documents for other PTLs See Adheli's Removal of O-Parent from Policy, Removal of O-Parent from Policy Will open Jira ticket(s) for O-parent removal from other projects in Oslo, as needed Each PTL needs to open a Jira ticket for O-Parent removal from their projects For the projects without PTLs, SECCOM will open a Jira ticket ARCCOM: open for requirement/architecture reviews
	Deprecated project	Ramesh Murugan Iyer Byung-Woo Jun	Policy-GUI deprecation in Oslo release has been initiated by Ramesh Policy team confirmed that "Policy-gui is currently not being used by any external components in ONAP. And policy-gui is dependent only on the policy-parent repo as its parent ." ARCCOM approved its deprecation, ONAPARC-804 - Getting issue details... STATUS OOM confirmed that it has no dependencies - checked On July 18th, TSC approved its removal (we passed #6) Need to proceed rest of the transition steps, Project State: Unmaintained
	Project Maturity	Byung-Woo Jun	ONAP component mature state, Mature State Projects Now, we are handling ONAP component individually under ONAP Streamlining, exposing the components to users. CPS is the first case that TSC approved the mature state after ONAP Streamlining. Should we keep the projects under the list as "mature", or should we certify them again? Several components are deprecated. According to TSC 2.0 doc, Mature state is "Project is fully functioning and stable, has achieved successful releases." Several projects in the list are deprecated/archived. To approach a broad audience, should we consider the "Core" state for some selected projects?? Gold badging is a separate process from the project maturity in LFN? CPS got the gold badging Policy is working on it? Policy team got editing permissions for gold badging wiki pages - WIP What other components do we want to get the gold badging? Follow the http://tlhansen.us/onap/onap.html tool for gold badging
	LF IT Support		Pending tikect opened by Marek: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25573 Kevin Sandi - a workaround solution will be tried; Marek / Matthew - automatic building solution is needed; escalate this? Kevin/Matt/Kevin - create a ticket and try a solution (maybe Github action helps? PoC??) Some action plans and updates next week Kevin and Marek are working on it, testing and deployment. will report its status - 90% is working; WIP; scheduled for next week update Kevin: Jenkins' sandbox; security patching is working fine; downtime would be 30 mins; will notify the downtime by email to ONAP community - WIP Thomas Kulik - issues with Portal-NG and other documentation - IT-26899 Project is not created in RTD - Kevin; found a root cause; almost done, pushed the fixes; Marek: Verifying of fixing; will follow up when Thomas Kulik and Fiete Ostkamp back - next week report; related to RTD pipeline? need further testing Ticket opened by Tony: IT-26848 - Tony is checking on it, still has issues; Kevin will work on it; Thomas will check; should not block any? will work; report its staus next week
	Open Source Security / SECCOM	Byung-Woo Jun	CISA report on memory safe code: joint-guidance-exploring-memory-safety-in-critical-open-source-projects-508c.pdf, The-Case-for-Memory-Safe-Roadmaps-508c.pdf 2 actions: OpenSSF- add/update their gudelines; Tony Locally for ONAP: impact assessment and reviewing if there are opportunities to remove those languages. Added memory safe code guidance to the architecture security review template, ONAP Component Architecture Review Template Future alternative of ONAP networking option (Andreas Geißler ): ONAP "Networking" Options (>=Kohn)
	OOM	Andreas Geißler	https://gerrit.onap.org/r/c/oom/+/138260
	Testing Environment
	Testing Improvement
	CSIT Review
	ToolChain Improvement
	Documentation
	Other Improvement suggestion	Andreas Geißler	Plan to migrate ONAP components to use RFC8040. SDNC and SO decided to move it to Oslo. ---- As backup Dan is working on Biermann but not progressed. ODL is not supporting it. Restconf stack is based on RFC draft. Preferred approach is to move to RFC8040 (Alternative 1). Originally proposed back in the Kohn release Plan for the New Delhi release Andreas Geißler DT has someone working on the SO piece to try and port to RFC8040 ONAP components will be moved to RFC8040 in New Delhi Alternative 2: keep maintaining Biermann interface. may support either London or Montreal as a long term release Alternative 3: rollback to version before Argon. ~~Alternative~~ ~~4 (the most drastic): stay where we are for now and begin to work with moving off from ODL.~~ As we have no solution, we can not move to ODL Potasium.
	Subcommittee Updates for PTLs	Paweł Pawlak Amy Zwarico	Recommended packages upgrades are available on the restricted Wiki. Jiras to be created per project. Oslo/wiki/spaces/SV/pages/16094458 Need to check NG Portal status CLM jobs. Any update? - no solution for now: 6/24/2021: PortalNG reports in spreadsheet on protected wiki page - New Delhi Package Updates - Security Vulnerabilities - Confluence (onap.org) Ticket opened by Fiete: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26527 (ticket is closed) ongoing; Jessica and Fiete are discussing this. We are missing NG Portal UI CLM job. List of the ONAP components to be disabled prepared by Andreas: OOM New Delhi Release On April 18th, TSC approved the list. Ticket opened by Fiete for UI CLM scan: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26882 - not a maven based project - an issue? To be further eleborated with Jess.
	Sharing Best Practices
	Others
IF TIME ALLOWS ....
15 mins	Release status

5 mins	Upcoming Events		TBD
10 mins	Remaining Action Items

Zoom Recordings

GMT20240722-125916_Recording_1920x1140.mp4

GMT20240722-125916_Recording.transcript.vtt

Agenda

Zoom Recordings

Zoom Chat Log

Browser not supported