| Duration | Agenda Item | Requested by | Notes / Links |
|---|
| 30 mins | Cross-project discussion |
| - This meeting is reduced to 30 minutes
- Rotating host
|
RelEng/Infrastructure | | - Toine Siebelink, requested removal of GHA vote on Jenkins jobs (for CPS)-Done
- Jessica Gonzalez, The issues that were blocking Toine were a combination of:
1- Doc links that were failing due to the migration of Jira and the fact that the links were not redirecting properly
2- More than one INFO.yaml files being modified at once (which is not something CI supports)
3- There was also the checkov action that was failing but it was silent (non voting). However Toine thought it was a blocker.
1 and 2 cannot be overridden by a PTL. 3 was never a blocker but it was failing silently. 1 and 2 were blocking Toine.
Right now he is unblocked and his changes are merged as of this morning. Thanks, Jessica, Kevin and LF IT teams - Byung-Woo Jun:
- #2 is required for security reasons.
- #1, if PTLs want to override this, we can discuss.
- For now, if you experience any build failures, please issue LF IT tickets right away to Jessica and LF IT team.
- additional questions from Toine:
- Geolocation timezone support
- should not block build, e.g., github action should NOT block project build; too unstable
- put vote+1 from the GHA job, or alternatively give the PTLs the option to vote +1
- Action: Jessica Gonzalez, will check with Andrew to check if the script can bypass; She will let us know ASAP; Thanks, Jessica!! See the above 3 issue summaries.
- https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27302 - waiting for customer
- Action Points: #1 was placed to enhance documentation quality. Depending on pain points, Thomas Kulik can provide a possible solution. Lee will send email to Thomas for pain points and we will bring up the email thread to TSC this week for a decision for #1.
- TSC approved: TSC agrees to allow project committers to bypass a -1 verification for Docs link or RTD checks and/or optional job from CI allowing them to make the change submittable. Additionally, any failures in documentation arising from bypassing the CI verification will be the responsibility of whatever committer bypassed the -1 vote.
Jessica Gonzalez , cleaning up ONAP confluence pages, attachments; so far 260GB, target: 220GB;TSC needs to set up a policy around the attachment length (6 months and can be 4 months) - the process is done.
- Kevin Sandi , removing gerrit plugins as a possible solution; update the ticket with findings and will check them with Tony; any update? Fixed; Thanks Jessica and Kevin; verify Tony; Byung plans to check it with Tony at the ONAP SECCOM this week; Tony said it is still failing; Kevin Sandi and Tony Hansen will discuss it offline.
- We need to double confirm with Jessica that Zoom recordings links are available infinitely on PCC Project Control Center (Dashboard?) https://openprofile.dev/ 5 years storing policy proposed - Jess to check with PCC team.; indefinite time
- Youtube account to be considered for ONAP. Kenny to be contacted for that as there are some ONAP recording available (https://www.youtube.com/@onapproject9232).
- share videos somewhere and LF IT will support them somehow? Casey Cain
- Contact Casey Cain for YouTube uploading
- Fiete issued a ticket, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27296 for sonacloud broken job; Matthew and Kevin will work on it;
-
|
Oslo Release update | | |
| Paris Release update | Byung-Woo Jun | |
| Doc | | - ONAP Streamlining Documentation Enhancements for Oslo:
- Defining ONAP Core components and extensions (e.g., lightweight ONAP, optional components)
- Core component functions
- Installation guide, including ArgoCD-based deployment options
- configuration guide
- User guide
- Use cases by operators and vendors
- reference architecture (component, interface, security, function...) for lightweight ONAP
- PTLs will be contacted for their help as needed.
- Byung-Woo Jun , started the documentation for ONAP Streamlining here, ONAP Streamlining Evolution; WIP; target date: end of October
|
| OOM | | |
| | |
| | Matt Watkins , will update next week
Fiete Ostkamp , is there any automated tool for dependency checking from Gerrit? Matthew will provide its update. Matt/kevin will check; may use portal-ng as a test project/candidate; Fieta will a LF IT ticket toward Matt/Kevin. ; Matt put a couple of patches, still working on it. |
| Paweł Pawlak Jessica Gonzalez | Pending ticket 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? Waiting for feedback from Marek
- 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
- wait for argo-cd deployment update. will revisit...
- wait for Marek's return
- Marek is working on it.
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 - Kevin / marek: WIP; update in two weeks.
- Kevin / Marek are working on it. wait for Argo CD finish
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; Let us know. - Kevin Sandi , working on it; removing gerrit plugins as a possible solution; update the ticket with findings and will check them with Tony; WIP
|
| Open Source Security / SECCOM | | CISA report on memory safe code:
Istio Ambient Mode will be GAed in November 2024, according to Solo.io |
| Testing Environment |
|
|
Testing Improvement |
|
|
CSIT Review |
|
|
ToolChain Improvement |
|
|
| Documentation |
|
|
Other Improvement suggestion | | Plan to migrate ONAP components to use RFC8040. and will Keep the New Delhi CCSDK/SDNC as LTS (long term support) for Biermann APIs. In Oslo, only RFC8040 will be supported. Dan Timoney, reviewed the above CCSDK/SDNC plan with ARCCOM and ARCCOM approved it.
SDNC and SO decided to move it to Oslo.
----
According to Dan,
Our original plan had been to migrate to the OpenDaylight Potassium release in New Delhi and to retire the Biermann API at that time. We were not able to complete those upgrades in time for the New Delhi release, so we ended up remaining on OpenDaylight Argon release with our Biermann adaptor.
For Oslo, our plan is to:
Complete the upgrade to Potassium originally planned for New Delhi. This work is almost complete – I expect to finish within the next week or so.Complete the work needed to migrate our internal interfaces from the Bierman format to RFC 8040.If time permits, upgrade to OpenDaylight Calcium release.
We have been advised that the OpenDaylight Calcium release is a major upgrade, with a significant amount of breaking changes. So, I would say there is significant risk that the Calcium upgrade might not complete in time for Oslo. My plan would be that we would release an initial Oslo version of CCSDK and SDNC that is based on OpenDaylight Potassium release to OOM as soon as it is a available so that we avoid a last minute impact. Once that is complete, I’ll create our oslo branches and use our master branch to begin work on the Calcium port. If that port is completed in time to make Oslo, great – we’ll cherry pick it to the oslo branch and include it. If not, then our Oslo code base remains stable on Potassium and the Calcium port will complete in the Paris release.
One more word on releases: my plan going forward is that the New Delhi release will be considered a “long term support” (LTS) release for CCSDK and SDNC. That is to say, we’ll provide security updates and other critical fixes as needed for that release so that any clients that find themselves unable to migrate to RFC 8040 for whatever reason will still have support, with the understanding that they will remain on the OpenDaylight Argon release.
Dan Timoney , is working on this to remove Biermann API; he will update its status. Once it is done, please let the SO team (Sankar) know. Thanks.
Potassium upgrade is almost completed by Dan to be followed by Calcium upgrade (current ODL version)
Andreas Geißler wiil check with Sankar (SO) if he can use the client library.
|
Subcommittee Updates for PTLs | | Recommended packages upgrades are available on the restricted Wiki. Jiras to be created per project. Need to check NG Portal status CLM jobs. Any update?
- no solution for now:
Fiete Ostkamp , Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
; will check them Matt Watkins , will follow up. Please let us know the outcome. |
Sharing Best Practices |
|
|
| Technical debt | Fiete Ostkamp | Chef dependency in SDC related to Ruby conflict (2.0 is pretty old)
 SDC-4691
-
catalog-be docker build is failing due to ruby dependency conflict
Open
|
| Other Technical discussions |
| - Muddasar Ahmed, SPDX 3.0 is not yet ISO standard; they plan to work on it;
- LF TAC: two special seats (security and blueprint); maybe one additional seat for AI?? ; wip
- Byung-Woo Jun AI model openness; LF AI & Data; Model Openness Framework; WIP
|
| IaC scans | | |
| IF TIME ALLOWS .... |
| 15 mins | Release status |
| |
|
| | |
| 5 mins | Upcoming Events | | |
| 10 mins | Remaining Action Items | |
|