TSC 2024-08-29

TSC 2024-08-29

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

Passcode: 209247

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.

Attended

Proxy (w/ @name)

Holiday

Did Not Attend

Attended

Proxy (w/ @name)

Holiday

Did 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/

 

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

@Keguang He 

@Sandra Jackson 

@Byung-Woo Jun 

  • China Mobile has a plan for Model as a Service (MaaS) utilizing large models

  • China Mobile needs publicly accessible GPU-enabled virtual machines for development

  • Can LFN provide or assist in acquiring a necessary public cloud infrastructure? @Sandra Jackson , could you contact LFN for this?

  • @Sandra Jackson check what resources LF have for testing (UNH? AWS)

TCC / ONAP Liaison Updates

 

 

Task Force Updates

 

 

 

 

 

 

 

 

Operations (40 minutes)


TSC Activities and Deadlines

@Paweł Pawlak @Byung-Woo Jun @Dong Wang @Keguang He

@Muddasar Ahmed  @Thomas Kulik 

  • 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 core component contents, as needed

  • @Thomas Kulik, shared the tool https://lf-onap.atlassian.net/wiki/x/TJn8 More update from Thomas... 

  • for now, we can start the documentation for ONAP Streamlining.

Release Status

@Byung-Woo Jun 

@Andreas Geißler 

@Thomas Kulik 

  • Oslo release wiki pages:

    • Release Planning: Oslo

    • Project Status in Oslo Release

    • Oslo Release Key Updates

      • ONAP PTL, please fill up the project key updates promptly - by end of September

      • @Dan Timoney plans to update the key updates wiki page for CCSDK and SDNC

      • As needed, schedule requirement and architecture reivews with ARCCOM (@Byung-Woo Jun )

        • @Dan Timoney plans to schedule CCSDK and SDNC requirement and architecture reviews soon

    • DT supports Argo CD-based deployment support the resolution? @Andreas Geißler , @Marek Szwałkiewicz 

      • WIP (DT is working on it)

    • Oslo Documentation - @Thomas Kulik , updated the wiki page. Thanks!

    • ONAP logo change update, @Thomas Kulik , https://gerrit.onap.org/r/q/%22new+onap+logo%22+-status:merged ; use the new ONAP logo where applicable...

    • @Thomas Kulik , any update ? @Fiete Ostkamp , worked on SDC for outdated Ruby

RelEng/Infrastructure

@Sandra Jackson @Jessica Gonzalez 

@Kevin Sandi 

@Tony Hansen 

  • Lfx zoom meetings need backup owners for vacation and other occasions - WIP

  • @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.

    • We need to discuss the next steps further

    • TSC vote: 

      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.

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

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.

PTL Updates

@Paweł Pawlak 

@Byung-Woo Jun 

  •  DMaaP DR deprecation is approved by TSC on July 25th - almost  done

    • ONAPARC-805 - Global Requirements for DMaaP DR Removal in Oslo IN PROGRESS 

    • Proceeding rest of the transition steps, Project State: Unmaintained

    • The entire DMaaP will be deprecated, replaced by Kafka/Strimzi

    • @Andreas Geißler , please remove DMaaP from OOM

    • https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27045 was created to remove DMaaP Jenkins job, CLM scan and sonarcloud report.

      • @Kevin Sandi is the assignee for this ticket.

    • Some companies are still using DMaaP DR in Jakarta; informed them to use Strimzi/Kafka since 1) DMaaP is deprecated since New Delhi and  2) ONAP supports the current release and -1 release. 

  • CCSDK A1 controller committer permission for John Keeney

  • SonarCloud report for Portal-NG UI; wait for nextus iq; any update? Matt has credential before; Jess will check with him

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements

@Byung-Woo Jun 

  • The Architecture diagram for Oslo, Oslo-R15 Architecture Diagram

  • Oslo Architecture main wiki pages, Oslo-R15 Architecture/ArchCom Wiki Page ; see its sub directories for project architecture pages

    • Updated Oslo project component architecture descriptions

  • Wait for Oslo requirement and architecture review requests (e.g., UUI GenAI requirements from @Dong Wang and @Keguang He ). Most likely by end of August or in September.

 

China Telecom Input

@Dong Wang 

  • Dong Wang (China Telecom) plans to present China Telecom's vision for ONAP (e.g., Gen AI, Data Service and others) on September 12th. 

 

IaC Scanning for security

@Byung-Woo Jun 

  • ONAP uses sonarCloud for static code analysis

  • Since we are applying more CI/CD-based builds and deployment, we may need to consider IaC scanning mechanism to securely deploy ONAP functions

  • This could be part of LFN governance support. TBD

  • This topic will be discussed further at the ONAP SECCOM

  • @Jessica Gonzalez  will check and return to us

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping

@Sandra Jackson 

@Byung-Woo Jun 

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.