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. 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 Byung-Woo Jun opened a ticket for LFN IT to remove Jenkins jobs for deprecated projects, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26907 Need to provide a deprecated repo list to LF IT (Jessica) - WIP
	New Delhi Release Status	Byung-Woo Jun	New Delhi Release is signed off on June 13th New Delhi RC date change (May 16 → 23) and Sign Off (June 6 → 13) Release Planning: New Delhi TSC vote for new dates: TSC approved it on May 16 Project Milestone Status, New Delhi Milestone Status Project RC Jira tickets wiki, R14 Release Candidate JIRA Tickets New Delhi Architecture Diagram, New Delhi-R14 Architecture Diagram Oslo related Wiki under creation by Byung, Release Planning: Oslo O-parent removal from Oslo?? Ericsson presented their O-parent removal experience last TSC meeting Preparing for its instruction documents for other PTLs
	Oslo	Byung-Woo Jun	For Oslo plan, Documentation on how to aggregate core ONAP functions for greater solutions, including deployment and trouble-shooting a question around use of Github docs for project / code (e.g., readme.md) collect PTL feedback
	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 What other components do we want to get the gold badging? Policy is working on it.
	LF IT Support		Fix (Python dependency specification) needs to be done on every project side. check with Thomas Kulik Matt shared documentation patches (verification failures needs to be fixed): https://gerrit.onap.org/r/q/owner:thomas.kulik%2540telekom.de+-status:abandoned+-status:merged Progress achieved, Lukasz help expected for K8s for Multicloud by end of next week. Ticket to be opened by Thomas Kulik - those repositories have no owners which blocks Documentation projects 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 Thomas Kulik - issues with Portal-NG and other documentation - IT-26899 Project is not created in RTD
	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 are created per project. /wiki/spaces/SV/pages/16094458 Need to check NG Portal status CLM jobs. Any update? - no solution for now 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.
	Sharing Best Practices
	Others
IF TIME ALLOWS ....
15 mins	Release status

5 mins	Upcoming Events		TBD
10 mins	Remaining Action Items

Zoom Recordings

GMT20240617-125229_Recording_2560x1440.mp4

GMT20240617-125229_Recording.transcript.vtt

PTL 2024-06-24

Agenda

Zoom Recordings

Zoom Chat Log