Versions Compared

Old Version 20

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user Kenny Paul

Saved on

Key

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

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

Passcode: 209247

2020 2021 TSC Recordings

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

...

Alla.Goldner

AMDOCS

djhunt

IBM

Andreas Geißler

DT

Lingli Deng

China Mobile

Bin Yang

WindRiver

Murat Turpçu 

Turk Telecom

cl664y@att.com

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/

20

PTL Updates

Kenny Paul 

Srinivasa Addepalli

EMCO

  • OPENness governance -   
    • public github repo
    • ONAP would submit requests to Intel Product Management
    • New OPENness code published to the repo only once a quarter after it passes all of Intel's gates
  • Folks can see the benefits and importance of something like EMCO
  • EMCO's use in the LFN demo was noted
  • Discussion of use model
  • No gap analysis has been performed
  • https://github.com/open-ness/EMCO
  • Concerns raised over:
    • Primary concern is EMCO being under the  company managed governance model of OPENness
      • strong desire for having a transparent and impartial governance model
      • strong preference for this to be an LF project
    • ONAP being the primary user of ONAP vs. something like MariaDB
    • New project - not mature and little influence
    • Don't like the idea approach of forking code
  • If there is a usecase that can leverage EMCO it needs to run through the Arch and Requirements subcommittees
    • Identify the gaps
    • identify 

Next Steps :

#1 Srinivasa Addepalli to consider option #5 EMCO as part of LF Edge Community?

#2 Chaker Al-Hakim , Srinivasan Selvam to determine from an Architecture perspective the added values of EMCO for ONAP (specially for our Cloud Native Journey), highlighting what feature will EMCO enrich, close the gaps.

#3 Call to Requirement Owners who wants to consume EMCO into ONAP use cases to meet Requirement subcommittees (Alla.Goldner , Timo Perala ) to prepare Istanbul release (based on ongoing EMCO/ONAP POC) 

#4 Alla.Goldner, Timo Perala, Chaker Al-Hakimto present their conclusions to the TSC 

#5 TSC to determine next steps i.e. consumption model of EMCO or not.

Note: #1, #2 and #3 to be implemented in parallel

60

TSC 2.0

Kenny Paul
cl664y@att.com

Deferred from the February DTF in order to ensure the attendance of TSC members from Asia

View file
nameONAP TSC 2.0-v2.pdf
height150

Priorities driving TSC Composition

  • Alla.Goldner company diversity & influence - company should pick the candidate
  • djhunt Level of TSC contribution - would like to see a more strategic focus
  • Olivier Phenix - company should pick the candidate
  • Ranny Haiby - company should pick the candidate - would like to find a way to separate the release management triage as the primary function from strategy
  • Timo Perala  - company should pick the candidate. Also need to see active TSC participation
  • Ciaran Johnston - would like to see contributions and need to see expectations.
  • Seshu Kumar Mudiganti - separate triage from strategy
  • cl664y@att.com company rep is important but need to also be focused on community, not just company.
  • #AGREED continue TSC 2.0 discussion to next week - move all other topic other than the actual M3 vote on Honolulu


10

Release Status

David McBride

Honolulu Release (M3 Feature Freeze - Feb 25th, 2021)

  • Honolulu Milestone Status
    • Any feedback concerning M3 Jira task (PTL & Req Owner)?
    • Explain what it is expected during M2/M3 transition (but not tracked as a task) i.e. assess/update your risks
  • Exception to be submitted no later than March 4th, 2021 to SECCOM? 
  • Review CII badging form for OOM project  
  • Checkpoint on the remaining Architecture Review - Completed?

Guilin Maintenance


RelEng/Infrastructure

Jessica Gonzalez


PTL Updates

DOC

cl664y@att.com

Thanks Sofia Wallin for her great contribution, serving as Doc PTL over the last 2+ years


Task Force Update
CNF


  • OVP/ONAP: CNF Badging

TSC Activities and Deadlines

cl664y@att.com

2021 TSC priorities

LFX Insights discussions on March 4

Guilin Awards Announced March 4

2021 Internships - COMING SOON

...