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 10 Next »

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.

AttendedProxy (w/ @name)HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

DT
China Mobile
Ericsson
Individual
AT&T
Incognito
Huawei
Windriver
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

  • SECCOM: Announcement for ONAP releases prior to London:
    • All ONAP releases prior to London are broken because AAF certificate is expired. Users should select London+.
    • Action Point:
      • TSC/DOC/ARCCOM/OOM should publish this on the ONAP wiki, release note, etc.
  • Task Force Updates








Operations (40 minutes)


TSC Activities and Deadlines



Release Status



RelEng/Infrastructure



PTL Updates

  • Shared the OOM Helm chart versioning plan for New Delhi with PTLs. OOM (Andreas Geissler) provides Helm chart versioning flexibilities to projects, by following ONAP Streamlining. For more details, PTL 2024-01-22
  • Rotating hosts for the PTL meeting are needed. 

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements





Andreas Geißler 


Amy Zwarico 

  • ARCCOM: Huawei (Guanyu Zhu) presented the requirement and architecture for the 'Incident API requirements in R14', 1) collecting incidents from network, 2) analyzing and aggregating based on AI and others and 3) providing uniform and consolidated incident reports. ARCCOM approved this.


  • OOM: Tata Communication (Mateusz) installed ONAP Montreal/London and made improvements
    • OOM plans to make OOM enhancements including Tata input to New Delhi (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