TSC 2019-10-10

BRIDGE: https://zoom.us/j/661303200

Attendance -84%

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

Attendance is taken purely upon #info in Zoom Chat 

Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

JIRA Tasks

35

Release Status - El Alto

Documentation Status Sofia Wallin

RTD

Pair wise

Is it the latest status?

0: Integration Weather Board for El Alto Release

Brian reported that everything is GREEN regarding this test case - Action: wiki page to be updated accordingly

Integration Status

Blockers: 1: El Alto Release Integration Test Blocking Issues

Test cases: 2: El Alto Release Integration Testing Status

72H Stability Run will be kicked off as soon as latest SO/Policy containers are available (Target: Saturday, Oct 12th, 2019)

FINAL Containers no later than Friday, Oct 11th End of your Day !!

Detailed Test Status

https://lf-onap.atlassian.net/wiki/display/DW/Integration+Meeting+Minutes

http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2019/onap-int.2019-10-09-13.03.log.html

Security items:

License Scan Review

  • Steve Winslow Will publish license scan results within the week. TSC recommendation delivered  

El-Alto Messaging:

  • Project Teams/Owners: to update the Dublin Highlights deck
  • Action (Jim): Deck to be posted somewhere on the wiki

El Alto Remaining Milestones

  • Completion of Integration Testing: Oct 3rd, 2019 → Oct 17th, 2019
  • El-Alto Sign-Off on: Oct 10th, 2918 → Oct 24th, 2019


45

Release Status - Frankfurt

Release Planning: Frankfurt

Feedback from UseCase Subcommittee: https://lists.onap.org/g/onap-tsc/message/5452 

Feedback from Security Subcommittee: Frankfurt Release Requirements

Feedback about S3P requirements - djhunt , Paweł Pawlak

TSC Prioritization Criteria:

  • Be reviewed by Use Case’s subcommittee
  • Be Approved by the Architecture Team a.k.a only  Purple and Black
  • List of Dev committed to impacted PTL per use case, per requirement a.k.a these columns should be filled up
  • Impacted PTL approval per use case, per requirement a.k.a this column should be filled up
  • Integration Lead to be identified per use case, per requirement
    • Drive the automated testing and provide status to the Integration team

    • Confirm confidence enough testers to automate test(s) and perform it

Require Information - Frankfurt Release Requirements no later than Tuesday, Oct 15th EOD

Note - Items in Green are continuity from previous releases 


The following activities are implemented outside the normal cycles by the project teams:

#1 Completion of Self-Serve releases (Jessica Gonzalez )

#2 Dockerhub migration (cristinapauna )

#3 Move OOM Helm Charts ownership to project team (Mike Elliott )

#4 Ingress Controllers (Krzysztof Opasiak)


5

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Tickets- Waiting on Community:
  • Migration Status / Upcoming Changes
  • Super-committer usage policy proposal
    • Active window: After RC0 until Sign-off before scheduled release
    • no access to CI-management (LF only)

5

PTL Update

Integration PTL election underway


10

Subcommittee Update

Contol Loop

Control Loop Chair Elections - Pamela Dragosh

SECCOM Paweł Pawlak

Control Loop Sub-committee Elections 2019



Security evaluation scope identified: OJSIs solving, CII Badging responses, Vulnerabilities tables


5

TSC Activities and Deadlines

#1 Review ONAP Release Cadence

  • Task force driven by Chaker Al-Hakim
  • Target Implementation: Guilin
  • Initial Inputs: TSC-20 - Review and build an action plan regarding feedback/lesson learned raised by the community Open
  • 15-20 mins slot weekly on PTL Call

#2 Finalize Project Life cycle - Chaker Al-Hakim

#3 Review ONAP Marketing Messaging - cl664y@att.com

TSC-137 - Review the ONAP Release Cadence Delivered

5

Incoming Events

  • ONAP/CNTT F2F Event in January 14-16th, 2020 - Budapest (TBC)
  • ONAP event before or after ONS North America - Los Angeles (TBC)
  • ONAP event before or after ONS North Europe - Antwerp (TBC)
  • TSC Election as soon as TSC agrees on the next TSC composition


Action Items

  • Action: Andreas will discuss this with the Documentation project
  • Action: wiki page to be updated accordingly by Brian
  • Action (Jim): Deck to be posted somewhere on the wiki

Zoom Chat Log 

07:59:46 From Chaker Al-Hakim : #info Chaker Al-Hakim, Futurewei
08:00:21 From bin.yang@windriver.com : #info Bin Yang, Wind River
08:00:25 From ALLAGO : #info Alla Goldner, Amdocs
08:00:56 From Andreas Geissler : #info Andreas Geissler (DT)
08:01:00 From Ning So : #info Ning So, Reliance Jio
08:01:08 From Jason Hunt : #info Jason Hunt, IBM
08:02:51 From Stephen Terrill : #info, Stephen Terrill, Ericsson
08:03:05 From Catherine Lefèvre : #info, Catherine Lefevre, TSC Chair
08:03:17 From Srini : #info Srini Addepalli, Intel
08:03:21 From Catherine Lefèvre : New proxy, please enter your attendance in the chat - thanks
08:03:57 From Murat Turpcu,Turk Telekom : #info Murat TURPCU,Türk Telekom
08:04:11 From Pawel Pawlak (Orange) : #info Pawel Pawlak, Orange, proxing Eric Debeau
08:04:52 From Milind Jalwadi : #info Milind Jalwadi, TechMahindra
08:04:58 From Timo Perala (Nokia) : #info Timo Perala, Nokia
08:08:38 From Yan Chen : #info Yan Chen, China Telecom
08:08:43 From Davide (Vodafone) : #info Davide Cherubini, Vodafone
08:09:56 From Sofia Wallin to Jim Baker (LFN) (Privately) : Sorry for being late. The doc meeting ended a bit late
08:26:21 From Catherine Lefèvre : Great progress Team - Well Done !
<Brian pasted junk here>
08:30:41 From Brian Freeman (AT&T) : https://gerrit.onap.org/r/#/c/oom/+/96173/
08:31:05 From Catherine Lefèvre : Way to go ONAP Community - Keep going, we are nearly there with El Alto
08:44:16 From Pamela Dragosh : If we are going to require a subset of projects like Portal/Dmaap/AAF to provide artifacts early, then there needs to be a sufficient amount of time for them to do so by M2/M3.
08:58:39 From Cristina Pauna : Sorry, I need to drop the call at the top of the hour. The update for the dockerhub migration is that we didn't have time in the PTL meeting this Monday to discuss the proposal so it was sent on the email list: https://lists.onap.org/g/onap-discuss/topic/dockerhub_migration_and/34447632?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,34447632 The proposal is to generate the release tag only by the release Jenkins job (now it's also generated by the staging job). I will not be able to join the PTL meeting next week, so I will go to the OOM and CSIT meetings next Wednsday to discuss it. I will come back next week at the TSC meeting with the result.
09:18:04 From Catherine Lefèvre : @Mike Elliot and @Kezysztof
09:18:12 From Catherine Lefèvre : can you check at my notes on the wiki
09:18:23 From Catherine Lefèvre : want to be sure I have captured correctly takss-thanks
09:18:30 From Catherine Lefèvre : The following activities are implemented outside the normal cycles by the project teams: ..
09:18:31 From Catherine Lefèvre : thanks