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

Incognito

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






Lightweight ONAP

Byung-Woo Jun 

ONAP Streamlining Phase 2 - Requirements, documentation, roadmap - work in progress

  • Leveraging individual core ONAP network automation functions, create lightweight ONAP solutions
  • create documentation (user guide, APIs, architecture, trouble-shooting), focusing how to use individual ONAP network automations
  • Use case of O-RAN / Nephio connections

O-Parent Dependency Removal

Adheli (Ericsson)Ericsson Policy Framework team is sharing O-Parent dependency removal experience
Operations (40 minutes)


TSC Activities and Deadlines



UUI/OOM Update 

Keguang He 

Andreas Geißler 

  • New Delhi UUI update
  • OOM Update for New Delhi
  • Any issue for Sign off

Release Status

Byung-Woo Jun 

  • New Delhi RC dates May 23) and Sign Off June 13
  • Project Milestone Status, New Delhi Milestone Status (work in progress)
  • New Delhi project branch ("newdelhi") creation for components with the following rules:
    • Code branch still goes with the marketing (e.g., newdelhi) 
    • If a project does not have any change (e.g., not active, no PTL), there is no branch change; if necessary, create dummy branches
    • Likewise, helm chart versioning is needed for active projects only. If there is no project change, they can stay at the old helm chart versions
      • The new OOM scripts (thanks to Andreas) support this

TSC vote for New Delhi Release Sign off (June 13)


Oslo  Release Planning: Oslo. (Kick off : May 30)

New Delhi documentation plan

RelEng/Infrastructure

Sandra Jackson (Deactivated) 

PTL Updates



  • Recommended packages upgrades are available on the restricted Wiki. Jiras are created per project. 

    Need to check NG Portal status CLM jobs. Any update? Jessica Gonzalez , ongoing.


Ticket opened by Fiete: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26527

    • ongoing; Jessica and Fiete are discussing this.

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements


  • ARCCOM updated the New Delhi Architecture overview - DOC-823 - Getting issue details... STATUS
  • ARCCOM plan for Oslo (lightweight ONAP with AI/ML) - Work in progress
  • Preparing for Oslo documentation plan - easy to use, user guide for Lightweight ONAP, trouble-shooting...  taking input from Keguang He, Dong Wang, Muddasar Ahmed...





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