Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 25 Current »

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 

Agenda Items

Presented By

Presos/Notes/Links/

Spark New Zealand - ONAP introduction

Spark New Zealand is in the process of evaluating ONAP through an internal POC based on OKD/OpenStack

They are looking for support from the community to have this evaluation pass and looking forward to contribute back to the ONAP community in the near Future.

LFN Cross-Organization Updates

OpenNess

EMCO Update

Release Status

Istanbul M1 

  • Release Planning: Istanbul
  • Istanbul Milestone Status 
  • Istanbul Impact View per Component
  • Recommend de-scoping  REQ-464 - Getting issue details... STATUS
    • Deferred from Honolulu
    • No update since Nov '19
    • No response from requirement owner regarding Istanbul M1 release management tasks
    • Requirement owner OOO until June 2
    • No objections
  • Process issue:  requirements created after publication of M1 relman tasks for req owners do not get assigned M1 tasks. (e.g.,  REQ-864 - Getting issue details... STATUS )
    • Do we need a deadline for submitting new requirements to the release?
  • #AGREED the TSC approves moving the Istanbul release from M0 to M1 with the exceptions of REQ-396, REQ-399 (best practices) to be clarified by May 27th and remaining project tasks for DMaaP, VNFSDK, SDC & UUI to be completed prior the M2.

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Tickets- Waiting on Community:
  • Migration Status / Upcoming Changes

PTL Updates

Congratulations to Michael Morris, our new SDC PTL

Call for Integration PTL - Re: Integration PTL elections : Call for Self-Nominations

Subcommittee Updates

Requirements

Thank you Swaminathan Seetharaman for your outstanding leadership regarding E2E Networking Slicing blueprint and also acting as our new O-RAN liaison !!!

Welcome 

@Ahila Ratna Shanker, LIN MENG  are our new ONAP E2E Network Slicing Leads

krishna moorthy is our new 5G SON Lead

TCC / ONAP Liaison Updates

O-RAN

Current Volunteers:  Timo Perala ,  Chaker Al-Hakim , SHANKARANARAYANAN N K

Task Force to identify a "Voice" and a backup "Voice" to update ONAP TSC on a monthly basis (question) - thank you for your engagement ! Operating Model to be share on TSC Call  

  • Magnus Buhrgard (Unlicensed) suggests that the existing ONAP / O-RAN  SC group be formalized as a task forceSwaminathan Seetharaman suggests following Magnus' suggestion but also have a formal liaison for the O-RAN Alliance itsTimo Perala there are currently 3 separate meetings that encompass the ONAP/O-RAN workRequest to existing team to decide upon the repreesentative

Task Force Updates
CNF, ONAP Enterprise,

O-RAN, Wiki 2.0


ONAP Enterprise - Next call on May 27th, 2021

TSC Activities and Deadlines

Jira Federation for ONAP (Approved)

TSC 2.0

Kick-off Honolulu Awards pretty soon

Progress on ORAN SC/ONAP Formal agreement

Upcoming Events & Housekeeping

PTL Call canceled on May 31, 2021

LFN Webinar Series

2021 LFN Developer & Testing Forum June

  -  

Register to  LFN Developer & Testing Forum June

  • presenters please watch for email from program committee on scheduling and details.

ONESummit - October 11 - 12 - Call for Proposal - Deadline: June 20th, 2021

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