Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • 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

ONAP Streamlining Documentation Enhancements 4733707d-2057-3a0f-
    • Pawel shared the report with SECCOM; Pawel will double-check it.


Fiete Ostkamp ,

Duration

Agenda Item

Requested byNotes / Links
30 mins

Cross-project discussion


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. 

      • 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
        • #Agree LFIT will complete the recommended migration. The downtime will be several hours but the wiki will be in read only mode. 
        • Shared this recommendation with PTLs and others at the PTL meeting - informed PTLs
      • 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
      • LFN Previous event is removed, https://wiki.lfnetworking.org/x/GAAF
      • What is the current status/plan?
      • LFN wiki: https://lf-networking.atlassian.net/wiki/
      • Jessica Gonzalez, update the migration status; completed; Thanks to Jessica Gonzalez and LF IT team !!!
      • Can we increase the max 250GB?? Jessica Gonzalez may talk to Steven;
      • Action Point: the biggest attachments are TSC, SECCOM, PTLs... Paweł PawlakByung-Woo Jun will take a look for this.
      • upload the YouTube (contact Casey)
      • https://www.youtube.com/playlist?list=PL0bkBeEamheBtymZPaF0nKw54bxJMmprR ; CPS YouTube
  • 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.We need to double confirm with Jessica  
  • 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

Doc 
Paris Release updateByung-Woo Jun
  • this week TSC will discuss about the next release name; 
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 
  • 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

Policy

Update Jiras

Oslo
  • WIP; will schedule its review with ONAP SECCOM.
RAN-SIM

Vishal Varvate

Andreas Geißler

  • possible enhancement contributions 
  • Plan to discuss the enhancement features and scopes and use cases

Update Jiras

Oslo Package

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

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.


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


  • 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

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:

  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)

Andreas Geißler wiil check with Sankar (SO) if he can use the client library. 


Subcommittee Updates for PTLs

  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:

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 ,
Jira Legacy
serverSystem Jira
serverId
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySECCOM-276
.
Jira Legacy
serverLinux Foundation Jira
serverId786ecce4-c7f8-3725-b80d-ceab920b9b14
keyIT-26882
; 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)  

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-4691

  • WIP

IaC scans

Paweł Pawlak 

Byung-Woo Jun
  • Fiete is workin on it.

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

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

  • Done; ARCCOM approved it
  • 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



    ...