Versions Compared

Old Version 4

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version 5

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2023 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

...


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.

Equinix - ONAP Consumer perspective

LFN Cross-Organization Updates

MAC, SPC, TAC, EUAG, LFN Board


D&TF Feedback

TCC / ONAP Liaison Updates



Task Force Updates









Operations (40 minutes)


TSC Activities and Deadlines



Release Status

David McBride 

Weekly Update

London Release - RC milestone decision



Panel

#VOTE:  Does the TSC approve the RC milestone (aside from AAI, DCAE, and OOM), with the following exceptions which are to be resolved by Sign Off?

  • DOC-820, OOM-3179, SDNC-1805, SDNC-1806, SDNC-1807, REQ-1509



RelEng/Infrastructure

Matt Watkins IT-25429 Review of ONAP CI Threat Model and Security Controls

PTL Updates



Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements

Byung-Woo Jun 

ARCCOM Update: 

  • ONAP Streamlining further discussion with Andreas Geissler, e.g., wrapping up each ONAP component individually and plugging in CD, as a low-hanging fruit of ONAP Streamlining. It seems that DT internally configured ONAP for wrapping up the components individually and applied their CD. Andreas and Byung plan to discuss it further and propose a plan to ONAP TSC (target release: Montreal).
  • OOM features for Montreal was reviewed and approved by ARCCOM. Andreas Geissler presented the OOM features. 
  • Next week, N. Shankar plans to present ONAP/OSC SMO PoC framework: joint use case to improve architecture alignment and OSC/ONAP collaboration for SMO-based solutions.

Events & Meetings

(5 minutes)

Upcoming Events & Housekeeping



...