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

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

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)Gov. HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

AMDOCS
Individual Contributor
DT
Ericsson
WindRiver
STL
Bell Canada
Individual Contributor
AT&T
Huawei
China Telecom
Nokia
Orange
China Mobile

Agenda Items

Presented By

Presos/Notes/Links/

Release Status

  • Weekly release status report
  • Jakarta M4 scheduled for Mar 24
  • Significant risk to Jakarta schedule due to lack of progress in migrating ONAP projects to UNH lab.
    • Jorge Hernandez reports success in exercising OpenStack to setup and access networks, setup policies, etc.
  • Need approval to add  AAI-3448 - Getting issue details... STATUS  to list of excepted Jira issues in last week's conditional approval of Jakarta M3 to be completed by M4.
  • #AGREED AAI-3448 is added to the list of jiras that must be resolved by Jakarta M4.
  • Kohn release schedule proposal available 

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Tickets- Waiting on Community:
  • Migration Status / Upcoming Changes
  • UNH Lab 
    • Jorge Hernandez initial testing - installed a small ONAP install and  everything seems OK 

PTL Updates



Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements


TSC ASD Vote

LFN Cross-Organization Updates

MAC, SPC, TAC, EUAG, LFN Board


SPC - ONAP Strategic Planning Committee (SPC) Representative - Call for Nomination

 Jonne Soininen confirmed for our next TSC meeting  to share 2022 SPC goals

TCC / ONAP Liaison Updates



Thinh Nguyenphu

Martin Skorupski , N.K. Shankaranarayanan, John Keeney (Ericsson EST) O-RAN SC - request to fix copyrights issue about 3GPP


ETSI NFV is preparing an LS out to ONAP to inform ETSI NFV latest set of specifications:

CNF Taskforce and Modeling Sub-Committee ↔ ETSI workshop (March 22, 2022) announcement @ 14:00-15:00 C.E.T

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise


CNF Task Force meeting - Date/Time to be reconfirmed due to clock change

Ranny Haiby  Check with CNF Task about time/date for next meeting starting the week of March 28th, 2022)

Enterprise Task Force: Currently defining the requirements to support ONAP/SABRES POC

TSC Activities and Deadlines

  • Feedback from the LFN DTF: CNFs, ONAP/EMCO Alignment
  • ONAP Community Awards: Istanbul Release
  • 2022 ONAP Priorities / Action Plan 
    • Discussion about how MVP is defined.  It would be use case specific so may not be relevant across the board.
    • Different MVPs could potentially be defined based upon "what you want to do"
    • Continuing pursuing a standard process for sunsetting unmaintained projects.
  • Sylvain Desbureaux  please present findings related to OOM's migration to gitlab at   TSC meeting.


  • LFN Board follow-up actions -no update this week
  • Prepare TM Forum presentation (April 11th, 2022)

Upcoming Events & Housekeeping

  • LFN Developer & Testing Forum EU
    •  June 13-16, 2022, Porto, Portugal
    • In-Person
    • Topic Proposals: 
  • ONE Summit NA  Save the Date!
    • Nov. 15 & 16 2022 Seattle, WA, USA
    • In Person
  • LFN Developer & Testing Forum NA  Save the Date!
    • Nov. 17 & 18 2022 Seattle, WA, USA
    • In Person

<Available Slot>



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