PTL 2025-01-06

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

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: @Byung-Woo Jun / @PaweÅ‚ Pawlak

TSC Activities

@louis li

@Byung-Woo Jun

ONAP Annual Report to LFN

 

@Tony Hansen

  • https://gerrit.onap.org/r/c/dcaegen2/collectors/ves/+/138052;

    • Release dcaegen2-collectors-ves container failed

    •  

  • IT-27455, @Kevin Sandi is working on it; @Andreas Geißler will check it, too

  • 08:58:30 [ERROR] PublisherTest.publishEvent_shouldSuccessfullyPublishSingleMessage:81 expectation "expectNext(MessageRouterPublishResponse{successful=true, failed=false, items=List({"message":"message1"})})" failed (expected value: MessageRouterPublishResponse{successful=true, failed=false, items=List({"message":"message1"})}; actual value: MessageRouterPublishResponse{failReason=Topic topic not present in metadata after 60000 ms., successful=false, failed=true, items=List()})

  • @Kevin Sandi , PTLs need to check the error message; is it for DCAE only?

  • @Andreas Geißler :

Security

@Amy Zwarico

@Byung-Woo Jun

Note: We will handle this again early next year with SECCOM; January 14, 2025

  • Will discuss this again at the SECCOM (initial discussion at SECCOM; and early next year with PTLs); January 14, 2025

PTLs reported vulnerability reports are not accurate

  • NexusIQ reports and scripts have discrepancies - Fiete Ostkamp

  • May be a process issue - PTLs update based on the reports at the beginning of the release

  • Action items:

    • are PTLs willing to fix new vulnerabilities found up to code freeze? PTLs can fix new findings in NexusIQ

    • At the PTL meeting this Monday, Amy and PTLs discussed how to process vulnerability reports

    • The current assumption is that PTLs access the Nexus for the vulnerability reports and decide when to apply the fixes

    • @Amy Zwarico provided the initial Nexus access demo on December 2nd

    • CLM link, https://jenkins.onap.org/view/CLM/

    • @Amy Zwarico will provide another demo how to access Nexus to PTLs next Monday (12/09)

  • PTLs can add more people for the Nexus access (but maybe there are some license limitations; check with LF IT);

  • @Amy Zwarico , give a Nexus access demo, can we give PTLs more current views?

  • @Toine Siebelink , CPS has a fortnightly community meeting during which we already check some quality report. I think we will start including this Nexus IQ report in that cycle...

Oslo Release update

@Byung-Woo Jun 

 

  • December 12th RC date was approved by TSC on December 12th

  • Oslo sign off date is January 9th. 

    • What is the current status?

  • Any documentation update will be done between the RC and Sign off (Jan 9)

    • ARCCOM

    • OOM

    • CPS

    • Policy

    • Portal-NG

    • CCSDK/SDNC

    • SO

    • UUI

    • ...

  • TSC approved a vulnerability exception for some projects; Package upgrades for vulnerability mitigation will be handled in Paris

  • SDC Ruby update is postponed to Paris

  • PTLs need to issue Release Candidate Jira tickets for their projects

  • Release Planning: Oslo

  • Project Status in Oslo Release

  • Oslo Release Key Updates,  thanks PTLs

SDNC - SO integration testing is still ongoing - @Andreas Geißler , it is possible we can support both Biermann and RFC8040 if Dan/Sanket does not respond before this Thursday.

@Ramesh Murugan Iyer , Policy needs to be updated XACML pdp image update? Please let us know before this Thursday.

Paris Release Update

@Byung-Woo Jun

  • The next Paris release schedule is TSC approved on 05 Dec 2024 , Release Planning: Paris 

    • TSC approved the current Paris release schedule on December 5th

    • An ArgoCD deployment to provide an alternative the helm deployment

    • RAN Simulator enhancement

    • Policy-OPA-PDP

    • MAAS

    • SDC Ruby upgrade

    • Project package upgrade

  • Long Term Release Roadmap

Argo CD Update

@Marek Szwałkiewicz

GoLang Job Issues

@murali parthasarathy k

@Deena Mukundan

@Kevin Sandi

OOM, SDNC, SO Update

@Andreas Geißler 

@Dan Timoney

  • update needs for policy and cds (java 17 version) - image update; DT will provide update.

  • any update for the Oslo release

  • SDNC-SO testing status for RFC-8040

  • UUI patch image changes; any feature update? @Keguang He needs to confirm.

 

  • In Oslo, 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.

    • @Andreas Geißler , working with Sanket and Dan.

 

RAN-SIM (Target Oslo)

@Vishal Varvate

@Andreas Geißler

  • @Andreas Geißler helped @Vishal Varvate where RAN Simulator enhancements will be checked in for Oslo

  • @Vishal Varvate, plans to share the enhancement features and scopes with @Byung-Woo Jun this week.; We have not yet received the feature summary.

  • Postponed to Paris

Update Jiras

Oslo Package

@Amy Zwarico 

@Paweł Pawlak 

@Toine Siebelink


** Moved this task to Paris **

Byung-Woo Jun, for those projects without PTLs, we fileed vulnerability exception. Those package update will be revisited in Paris. TSC approved it on December 12th.

@Toine Siebelink updated the following: (Thanks!!!).

  • Assignee, please check the tickets

  • For the ticket without assignees, we need to find new assignees

Epic: https://jira.onap.org/browse/REQ-439
Oslo task: REQ-1592: PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR OSLO RELEASETo Do

 

key summary assignee status resolution
Loading...
Refresh

  • @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. Matt gave us update…

  • The Github2Gerrit is under IT-27340; about to merge; Matt, let us know;

  • https://sonarcloud.io/summary/overall?id=onap_cps-ncmp-dmi-plugin

LF IT Support

@Kevin Sandi

  • *** note: please check if the following issues are still open ***

  • IT-27455, @Kevin Sandi is working on it.; in progress

RelEng/Infrastructure

@Kevin Sandi

Note: Postponed to Paris

  • @Kevin Sandi, Github action ticket (Kevin Sandi) - bypassing -1 for option jobs : any update? Jira ticket for tracking RELENG-5602

    • If patches are fixed today, Kevin can start testing.

New bypassable workflow is in place and working. There are a couple of improvements I’m working on to avoid deprecation notices and use the correct voting github action.

It is working, but @Toine Siebelink , will create a new ticket for a new policy on checking the RTD links toward @Kevin Sandi ; @Thomas Kulik , reported there are many broken ONAP wikis; treat every warning as a warning??

@Toine Siebelink , created a new ticket, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27475 .

  • Any update? @Kevin Sandi will work on it later; backlog; Postponed to Paris

Testing Environment

 

 

Testing Improvement

 

 

CSIT Review

 

 

ToolChain Improvement

 

 

Documentation

 

 

Other Improvement suggestion

 

 

 

Sharing Best Practices

 

 

IF TIME ALLOWS ....

15 mins

Release status

 

 

5 mins

Upcoming Events

@LJ Illuzzi

 

10 mins

Remaining Action Items

 

 

Zoom Recordings

 

Zoom Chat Log

 

Â