Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

2024 TSC Recordings

2023 TSC Decisions

Anti-Trust Policy

We will 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.

AttendedProxy (w/ @name)HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

Andreas Geißler

DT

Keguang He 

China Mobile

Byung-Woo Jun 

Ericsson

N.K. Shankaranarayanan 

Individual

Dan Timoney 

AT&T

Paweł Pawlak 

Individual

Dan Xu 

Huawei

Seshu Kumar Mudiganti

Windriver

Dong Wang

China Telecom



Agenda Items

Presented By

Presos/Notes/Links/



Strategy (45 minutes)

ONAP takeaways


We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements.

LFN Cross-Organization Updates

MAC, SPC, TAC, EUAG, LFN Board



TCC / ONAP Liaison Updates



Task Force Updates









Operations (40 minutes)


TSC Activities and Deadlines



Release Status

Byung-Woo Jun 
  • Oslo related Wiki under creation by Byung, Release Planning: Oslo
  • O-parent removal from Oslo
    • Ericsson presented their O-parent removal experience last TSC meeting
    • Prepared for its instruction documents for other PTLs
    • Will open Jira ticket(s) for O-parent removal from other projects in Oslo, as needed
      • should we create a global requirement or should each PTL create its Jira ticket for O-parent removal?
  • ARCCOM: open for requirement/architecture reviews

RelEng/Infrastructure

Sandra Jackson (Deactivated) 

Paweł Pawlak 

Byung-Woo Jun 

  • ONAP SonaCloud reports/scans still include some deprecated projects (e.g., MSB, DMaaP MR) - LF IT


    • Need the main New Delhi pages for links - RTD doc; Thomas


Pending tikect 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?
  • 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

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 - 

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; Thomas will check; should not block any? will work; report its staus next week

PTL Updates

Ramesh Murugan Iyer 

Byung-Woo Jun 

  • Policy-GUI deprecation in Oslo release has been initiated by Ramesh
    • Policy team confirmed that "Policy-gui is currently not being used by any external components in ONAP. And policy-gui is dependent only on the policy-parent repo as its parent ."  
    • ARCCOM approved its deprecation, ONAPARC-804 - Policy-GUI deprecation in Oslo CLOSED
    • OOM confirmed that it has no dependencies - checked
    • At the TSC meeting July 11th, TSC handles it by email vote.
      • AP: Sandra will send email vote to TSC for Policy-GUI deprecation. (due date: July 24th).
      • TSC vote 
  • Project Gold Badging
    • CPS got the gold badging
    • Policy is working on it? Policy team got editing permissions for gold badging wiki pages
    • What other components do we want to get the gold badging? PTLs need to follow the http://tlhansen.us/onap/onap.html tool for gold badging

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements, OOM

Dong Wang 

Keguang He

Byung-Woo Jun 

Andreas Geißler 


  • Two new UUI requirement/architecture reviews for Oslo will be done in end of July / August.
  • Initiated DMaaP DR deprecation, which means ONAP deprecate the entire DMaaP from Oslo, ONAPARC-805 - Getting issue details... STATUS
    • OOM - needs to analyze its dependencies
    • TSC - needs to approve DMaaP DR deprecation and the entire DMaaP from Oslo



OOM Update

Andreas Geißler 

  • General OOM update for Oslo:  an alternative for ArgoCD-based deployment, in addition to the current deployment 

Open Source Security / SECCOM / ARCCOM

Byung-Woo Jun 

Andreas Geißler 

Paweł Pawlak 

CISA report on memory safe code: 

Other related articles: https://stackoverflow.blog/2024/03/04/in-rust-we-trust-white-house-office-urges-memory-safety/ 


  • 2 actions:

    1. OpenSSF- add/update their guidelines; Tony; WIP
    2. ONAP - impact assessment and reviewing if there are opportunities to remove those languages.

      1. Added memory safe code guidance to the architecture security review template, ONAP Component Architecture Review Template

  • Future alternative of ONAP networking option (Andreas Geißler ):

    • ONAP "Networking" Options (>=Kohn)
    • Istio Control  Plan is written in GO, but Envoy Proxy is written in C++; this could be one of the reasons that ambient mash could be interesting - TBD

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping


Zoom Chat Log 


Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative!   Information as to why .
They are included here as a time stamp cross-reference for the recording only!  The notes above this line and the actual recordings are authoritative. 


  • No labels