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 |
| ||||||||||||||||
Oslo Release update |
| |||||||||||||||||
Doc |
| |||||||||||||||||
OOM |
| |||||||||||||||||
CCSDK | Byung-Woo Jun |
| ||||||||||||||||
doc | Thomas Kulik |
| ||||||||||||||||
Deprecated project |
| |||||||||||||||||
Update Jiras Oslo Package | Oslo task: [REQ-1592] PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA Epic: https://jira.onap.org/browse/REQ-439 AAI: [AAI-3941] AAI PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASE - ONAP JIRA CCSDK: [CCSDK-4042] CCSDK PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASE - ONAP JIRA CPS: [CPS-2342] CPS PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASE - ONAP JIRA DCAE: [DCAEGEN2-3414] DCAE PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA Multicloud: [MULTICLOUD-1507] MULTICLOUD PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA Network Controller: [SDNC-1844] NETWORK CONTROLLER PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA Policy: [POLICY-5103] POLICY PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASE - ONAP JIRA PortalNG: [PORTALNG-114] PORTALNG PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA SDC: [SDC-4690] SDC PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA SO: [SO-4130] SO PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA UsecaseUI: [USECASEUI-840] UUI PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASE - ONAP JIRA | |||||||||||||||||
LF IT Support |
| |||||||||||||||||
Open Source Security / SECCOM | Byung-Woo Jun | CISA report on memory safe code:
| ||||||||||||||||
Testing Environment | ||||||||||||||||||
Testing Improvement | ||||||||||||||||||
CSIT Review | ||||||||||||||||||
ToolChain Improvement | ||||||||||||||||||
Documentation | ||||||||||||||||||
Other Improvement suggestion | Plan to migrate ONAP components to use RFC8040.
---- 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:
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. | |||||||||||||||||
Subcommittee Updates for PTLs |
- no solution for now:
List of the ONAP components to be disabled prepared by Andreas: 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.
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)
| ||||||||||||||||
Others | Paweł Pawlak | ONAP Licensing scans: https://lfscanning.org/reports/onap/onap-2024-06-0592bdfc-78a5-4fa8-a9fd-a7de581457ec.html | ||||||||||||||||
IF TIME ALLOWS .... | ||||||||||||||||||
15 mins | Release status | |||||||||||||||||
5 mins | Upcoming Events |
| ||||||||||||||||
10 mins | Remaining Action Items |