PTL 2024-09-30

Owned by Byung-Woo Jun
Last updated: Sept 30, 2024
8 min read
  • PTL Recordings
  • Antitrust Policy Notice

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 byNotes / Links
30 mins

Cross-project discussion


RelEng/Infrastructure

Jessica Gonzalez Paweł Pawlak 

Byung-Woo Jun 

  • 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)

    • Teams want to keep some of the important demo video.
    • TSC vote on August 29th: 

      TSC recommends all ONAP community members to add links with zoom meeting recording from Dashboard to ONAP Wiki's meeting summaries, so we could avoid an issue of high volume attachments with meeting recordings.

      • TSC approved the recommendation on August 29th 2024
      • Plans to share this recommendation with PTLs and others at the next PTL meeting.
    • working with LF IT, started June 13th and removed July 3rd; try to recover some of videos; Jessica will send email to Toine for more details.
    • 239GB current size, which is still big for migration; investigating if we can store large files to another storage; bring up options to TSC and TSC will make a decision
    • Any progress?
  • Did we remove A1 Policy Mgt / CCSDK Jenkins Jobs from London release? Kevin Sandi confirmed it, which is OK.
  • 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.
  • 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 , will work on it; WIP

Oslo Release update

Byung-Woo Jun 

Paweł Pawlak 


Doc 

Byung-Woo Jun 

  • 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
OOM 

Andreas Geißler 

  • An ArgoCD deployment to provide an alternative the helm deployment. Marek Szwałkiewicz , Andreas Geißler , DT is working on it.; will decide where DT applies..
  • 2 images failing on smoke tests - Marek is working on it.  For TSC meeting voting for Python 2 dependencies removal.

    • Voting for Python 2 dependencies removal from ONAP. - not valid anymore


    • Andreas Geißler , will check with Marek and let us know...
    • Marek Szwałkiewicz , WIP; Matt needs a ticket for a check; update next week

Policy

Ramesh Murugan Iyer 

Update Jiras

Oslo Package

Amy Zwarico 

Paweł Pawlak 

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

Matt Watkins , will update next week

Fiete Ostkamp , is there any automated tool for dependency checking from Gerrit? Matthew will provide its update. 

LF IT Support

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.

    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

Byung-Woo Jun Paweł Pawlak 

CISA report on memory safe code: 


  • 2 actions:

    1. OpenSSF- add/update their guidelines; Tony - Tony will check with OpenSSF ; tony is waiting for their response
    2. 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. PTL, please take a look at it.

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

Andreas Geißler  Dan Timoney 

Plan to migrate ONAP components to use RFC8040.

  • 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:

  1. 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.
  2. Complete the work needed to migrate our internal interfaces from the Bierman format to RFC 8040.
  3. 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)

Tomorrow at ARCCOM, Dan will provide features reqruiements. 

Subcommittee Updates for PTLs

Paweł Pawlak 

Amy Zwarico 

  1. 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:


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 elaborated with Jess.

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.

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

  • WIP

IaC scans

Paweł Pawlak 

Byung-Woo Jun 

Reference: https://www.checkov.io/1.Welcome/What%20is%20Checkov.html


Others

Paweł Pawlak 

ONAP Licensing scans: https://lfscanning.org/reports/onap/onap-2024-06-0592bdfc-78a5-4fa8-a9fd-a7de581457ec.html


ARCCOM review

Byung-Woo Jun 

Dan Timoney 

  • ARCCOM review tomorrow (October 1st) for CCSDK/SDN. Please join us.

    • Briefly, the issue is that there are differences between the version of the RESTCONF interface that was originally defined in the Internet Draft written by Biermann et al, and the version that was officially defined in RFC 8040.  These differences, unfortunately, are not backwards compatible.  For a while, OpenDaylight supported both versions, but at this point OpenDaylight no longer supports the Biermann variant. 

      We mitigated that issue within ONAP by taking a copy of the OpenDaylight code for the Biermann version and maintaining it ourselves.  The agreement was that this was a temporary solution only, which would be phased out. 


      Our  plan in CCSDK/SDN is as follows:


      1. New Delhi will be the last release in which both versions of the RESTCONF interface (Biermann and RFC 8040) are supported.  We plan to treat New Delhi as a Long Term Support (LTS) release, and will provide security patches as needed so that users that are unable to migrate to RFC 8040 are not left without a supported release.
      2. Starting with Oslo, only the RFC 8040 version of RESTCONF will be included in our CCSDK and SDNC packages.


      Since the removal of the Biermann interface is a fairly significant, breaking change, I am proposing that – consistent with semantic versioning – both CCSDK and SDNC will change major versions in Oslo.  CCSDK artifacts for Oslo will be numbered 2.0.x, and SDNC artifacts will be numbered 3.0.x.

IF TIME ALLOWS ....
15 minsRelease status






5 minsUpcoming Events


10 minsRemaining Action Items



Zoom Recordings


Zoom Chat Log