TSC 2020-11-12

Owned by cl664y@att.com
Last updated: Nov 24, 2020
4 min read


2020 TSC Recordings

2020 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.

Attendance 

AttendedProxy (w/ @name)Gov. HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

Alla.Goldner

AMDOCS

djhunt

IBM

Andreas Geißler

DT

Lingli Deng

China Mobile

Bin Yang

WindRiver

Murat Turpçu 

Turk Telecom

cl664y@att.com proxy: ChrisC

AT&T

Former user (Deleted)

Reliance Jio

Ciaran Johnston

Ericsson

Olivier Phenix

Bell Canada

Davide Cherubini

Vodafone

Ranny Haiby 

Samsung

Dong Wang

China Telecom

Seshu Kumar Mudiganti

Huawei

Eric Debeau

Orange

Srinivasa Addepalli

Intel

Fernando Oliveira

Verizon

Timo Perala

Nokia

Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

45

Release Status

David McBride


  • Honolulu
    • Schedule proposed
      • Please review and send feedback to David McBride .  Be prepared to vote on the schedule on Nov 19. 
      • PTLs: Please complete survey regarding PTL availability in December.
      • Note: Krzysztof Opasiak says that release requirements may be approved when ready any time between M0 and M2.
    • TSC Initial Feedback on Requirements
      • Honolulu Release Requirements - 3 Use cases; 13 functional requirements (2 submitted post deadline) and 12 non functional requirements (1 submitted post-deadline)
      • M1 approval field was used to provide some feedback - only 4 functional requirements are candidate to be approved
      • Any new requirement submitted after Oct 16th, 2020 (Honolulu Deadline Submission) will be reviewed for the Istanbul release except Guilin requirement left-overs
      • Missing Honolulu Impact View per Component and a lot of information to understand the requirements, company commitments etc. - Please use the Requirement Template
      • Missing company commitments, specially for non functional requirement (30 mins PTL practice might not cover all the needs)
      • REQ-428 - Is it aligned with the Modeling Subcommittee?
      • Request to adopt a phasing approach for the Use Cases to avoid large number of components impacted within a release
      • Automated Test Cases are required for the Use Cases - have you factorized this as part of your company's engagement?
      • EUAG priorities? No new use case but continuity of former use cases i.e. 5G SON, Network Slicing, CCVPN, CNF
  • ACTIONS - No later than Nov 12th, 2020:
    • Subcommittees to follow up with the respective requirement owners and ensure that the remaining information is provided 
    • How does the TSC want to proceed with the first 4 approved requirements?
    • Guilin left-overs - start to meet Requirement Subcommittee for review

5

RelEng/Infrastructure

Jessica Gonzalez

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

5

PTL Update



5

Subcommittee Update

Arch, Ctrl-Loop, Modeling, Seccom, Requirement

Chaker Al-Hakim

ARC Review Schedule for Honolulu

10

TSC Activities and Deadlines

cl664y@att.com

#AGREED the TSC meeting on Nov 26 will be cancelled
 due to the Thanksgiving holiday in the U.S.

5

Upcoming Events

Linux Foundation
  • LFN Developer & Testing Forum - Feb 1 - 4 (tentative)
    • Awaiting final confirmation by the LFN TAC

Action Items

  • Krzysztof Opasiakprovide overview of milestone requirements for new release process at  PTL call and Nov 19 TSC call
  • David McBride set meeting for Tuesday,   to review feedback on schedule.  Include Chaker, Krzysztof, Seshu, Vijay, and Dan.

Zoom Chat Log

05:49:41 From Kenny PAUL (LFN) : #topic rollcall
05:57:54 From Fernando (Fred) Oliveira : #info Fred Oliveira, Verizon
06:00:16 From Dong Wang (China Telecom) : #info Dong Wang, China Telecom
06:00:33 From Christophe CLOSSET (at&t) : #info Christophe Closset, proxy, AT&T
06:01:21 From ALLAGO : #info Alla Goldner, Amdocs
06:01:23 From Jason Hunt : #info Jason Hunt, IBM
06:01:28 From Timo Perala (Nokia) : #info Timo Perala, Nokia
06:02:08 From Ranny HAIBY (Samsung) : #info Ranny Haiby, Samsung
06:02:09 From Olivier PHENIX (Bell Canada) : #info Olivier Phenix, Bell Canada
06:02:10 From Eric Debeau : #info Eric Debeau, Orange
06:02:13 From SaiSeshu MUDIGANTI (Huawei) : #info Seshu, huawei
06:03:08 From Andreas GEISSLER (DT) : #info Andreas Geissler, DT
06:03:10 From Ciaran Johnston (Ericsson) : #info Ciaran Johnston, Ericsson
06:03:38 From bin.yang@windriver.com : #info Bin Yang,Wind River
06:03:46 From Murat Turpcu (Turk Telekom) : #info Murat Turpçu,TTG
06:05:29 From Srini Addepalli : #info Srini Addepalli, Intel
06:06:15 From Kenny PAUL (LFN) : #topic release manaqgement
06:07:45 From Ning So : #info, Ning So, Reliance Jio
06:09:34 From Kenny PAUL (LFN) : #AGREED The TSC approves Rc1, Rc2 and Sing-Off as all occurring on Nov. 19th
06:10:18 From Kenny PAUL (LFN) : @ning - thanks
06:18:47 From SaiSeshu MUDIGANTI (Huawei) : SO-3378
06:21:17 From Kenny PAUL (LFN) : @Alla - I've assigned you are the waiting room gate keeper
07:16:04 From Dan TIMONEY (AT&T) : I think what’s not clear at this point to me at least is what is expected of the PTL at M1 and M2 in this new process. For example, do we still have to complete release planning template? Hopefully we can clarify that at the meetings next week
07:21:28 From Krzysztof Opasiak : @Dan You are perfectly right. That's actually the main item that I plan to cover on Monday
07:22:46 From Krzysztof Opasiak : but in general for M1 there should be only Global Requirements comitment (chosen from approved best practices i.e don't run as root, log to stdout etc)
07:23:16 From Chaker AL-HAKIM (Futurewei) : https://lf-onap.atlassian.net/wiki/display/DW/Honolulu-R8+Architecture
07:23:20 From Krzysztof Opasiak : for M2 all "requiremetns" that are going to be worked on in this release cycle should be reviewed and agreed with ptl
07:23:48 From Krzysztof Opasiak : for M3 everything (functional) should be completed and delievered to OOM
07:24:06 From Kenny PAUL (LFN) : #AGREED the TSC meeting on Nov 26 will be cancelled
07:24:49 From Krzysztof Opasiak : at this point if there is anything left to be implemented in some feature it just gets delayed to the next release and we branch out and people may continue their development in Master
07:27:20 From Kenny PAUL (LFN) : link to Honolulu functional Arch. revires https://lf-onap.atlassian.net/wiki/x/0QH7
07:27:37 From Kenny PAUL (LFN) : ...
07:28:09 From Kenny PAUL (LFN) : The top level Arch review landing page for Honolulu : https://lf-onap.atlassian.net/wiki/x/rd36
07:30:42 From Dan TIMONEY (AT&T) : Thanks Krzysztof … put another way, what I want to clarify next week is what will be on the checklist for each milestone that the PTLs are required to work, so we can plan accordingly …