661303200

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

Attended	Proxy (w/ @name)	Gov. Holiday	Did 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	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	Honolulu Release Schedule	Krzysztof Opasiak Chaker Al-Hakim Liam Fallon Timo Perala Eric Debeau	Review and Vote of the Honolulu schedule based on the release cadence proposal. Release Cadence - Honolulu Release Proposal Note: any new project must still be presented to the TSC as per ONAP Technical Community Document#3.3ProjectLifecycle proposal is designed to address the fact that that deve and test resources are highly variable due to member priorities and therefore not consistent and/or guaranteed from release to release. Key to slides NF=Non-Functional Requirements RC=Release Candidate GR=global requirements (a best practice that should be applied to whole code base during the release) BF=bug fixing #AGREED the TSC approves the release cadence proposal in principal with details and policy to be provided by the task force by Sept 17th Task force (Krzysztof Opasiak, Chaker Al-Hakim. Liam Fallon, Timo Perala, Eric Debeau, David McBride to work with the release manager to provide the next level details no later than the TSC Call on17 Sep 2020
15	Guilin Release Status	David McBride	Maintenance Releases have been published: El Alto 5.0.2 and Frankfurt 6.0.1 Guilin - On Track M2/M3 Conditions are now met i.e. Architecture Review of all the project are now completed - Well Done ! Release Planning: Guilin #AGREED the existing Guilin release schedule that was approved on June 24 remains in place. Next Steps: Prepare M4 milestone (Code Freeze) – September 10^th, 2020 M4 Milestone Status M4 Scorecard to be updated by the Requirement Owners Review the Guilin Scope David McBridedistribute a new release string to the PTLs for Guilin 27 Aug 2020
5	RelEng/Infrastructure	Jessica Gonzalez	Job improvements: Docker merge: jobs now support "stream" tagging. Tag gets applied with the same value as the job's stream variable. Use "container-tag-method: stream" in your docker merge job. Sonar scans: Sonar job supports different JDK versions for build and for the scanner. Helpful for projects not compatible with JDK11 Use "java-version: openjdk8" for example for the build. The scanner is hardcoded to use JDK11 after the build completes.
10	Subcommittee Update Requirement	cl664y@att.com	Request from John Keeney (Ericsson EST) adding support for the O-RAN A1 interface in https://wiki.onap.org/pages/viewpage.action?pageId=84644984 In order to support the O-RAN A1 Application Protocol we use verbatim some code (schemas) defined in “O-RAN.WG2.A1AP-v01.01” from https://www.o-ran.org/specifications https://www.o-ran.org/adopter-license https://www.o-ran.org/s/O-RAN-Alliance-Adopter-License-Agreement.pdf Need for a an ONAP/O-RAN Liaison is important based upon the consumption of ONAP components suggested liaison- Swaminathan Seetharaman Alla.Goldner reach out to Swaminathan Seetharaman 03 Sep 2020 https://wiki.o-ran-sc.org/display/OAM/OAM+Architecture Will need a meeting of the ONAP legal committee - Kenny Paul to set up 28 Aug 2020
5	TSC Activities and Deadlines	cl664y@att.com	Student Project Liaison: Abbas Fazal 2020 Elections: Subcommittees: https://lists.onap.org/g/onap-tsc/message/6547 2020 TSC priorities - Review ONAP Focus Implement the "Requirements" Subcommittee - Completed Role of ONAP to support CNFs: creation of ONAP CNF Task Force - Completed Implement Project Review/Lifecycle - Completed Review Release Cadence - Completed Deliver Frankfurt (Sign-Off on 6/11) and Guilin CNTT/ONAP Partnership: Part of OVP PH2 (Cloud Native) Promote "What we have done" (Ongoing)
5	Upcoming Events	Kenny Paul	Open Networking & Edge Summit North America 2020 September 28 & 30, 2020 (Virtual Event) Registration is only $50. Register here. Note: Linux Foundation, LFN, and LF Edge Members are eligible to receive a 20% discount. Please email events@... to request the member discount code. Using a virtual events tool called INXPO ONAP and Cloud Native panel discussion LFN Fall Technical Meetings October 13 - 15, 2020 View the event wiki here and register here. There is no cost to attend Topic Proposals https://wiki.lfnetworking.org/x/9QhoAg Link to presentation template (pptx) will be limited to 4 hrs per day for 3 days recommendations based upon experience with June event reserving sessions for discussions versus presentations only 2 parallel sessions ensure cross-community sessions do not conflict with project community sessions cross-community: xgvela, opnfv/cntt, feedback from end-users Suggest "ONAP Theme" Honolulu release working sessions Global Requirements Track ONAP demo track TSC/Subcommittee Volunteers Ranny Haiby, Timo Perala , Chaker Al-Hakim , Seshu Kumar Mudiganti

Zoom Chat Log

06:58:10 From Fernando (Fred) Oliveira : #info Fred Oliveira, Verizon
06:59:37 From Ranny Haiby (Samsung) : #info Ranny Haiby, Samsung
07:00:16 From Srini Add : #info Srini Addepalli, Intel
07:00:27 From Ciaran Johnston : #info Ciaran Johnston, Ericsson
07:00:51 From Dong Wang (China Telecom) : #info Dong Wang, China Telecom
07:00:52 From Eric Debeau : #info Eric debeau, Orange
07:01:06 From Ning So : #info Ning So, Reliance Jio
07:01:13 From Andreas Geissler : #info Andreas Geissler, DT
07:01:14 From Murat Turpcu,Turk Telekom : #info Murat Turpcu, Turk Telekom
07:01:35 From Catherine Lefevre : #info, Catherine Lefevre, ATT
07:01:38 From Timo Perala : #info Timo Perala, Nokia
07:02:47 From Jason Hunt : #info Jason Hunt, IBM
07:02:57 From Olivier Phenix (Bell Canada) : #info Olivier Phénix, Bell Canada
07:04:31 From Sai Seshu : #info Seshu, huawei
07:10:09 From Jason Hunt to Kenny Paul (LFN)(Privately) : Hi Kenny - I’m here. :)
07:10:21 From Kenny Paul (LFN) to Jason Hunt(Privately) : thanks
07:10:30 From Kenny Paul (LFN) to Jason Hunt(Privately) : sorry
07:14:55 From Jason Hunt : A key might help here. NF=Non-Functional Requirements, RC = Release Candidate, BF=?, GR=?
07:16:24 From Krzysztof Opasiak : GR=global requirements (a best practice that should be applied to whole code base during the release)
07:17:04 From Krzysztof Opasiak : BF bug fixing
07:17:25 From Jason Hunt : Thanks Krzysztof
07:17:38 From Jason Hunt : is this the extent of the documentation for the new process?
07:20:31 From Catherine Lefevre : So GR reqs is composed of S3P reqs, non functional and best practices
07:24:31 From Catherine Lefevre : @Kenny, can you please track the action for the Task Force i.e. Task force to work with the release manager to provide the next level details on Sept 17th TSC Call?
07:26:41 From Sai Seshu : +1
07:28:19 From Catherine Lefevre : great job Release Cadence Taskforce !
07:29:09 From Kenny Paul (LFN) : #AGREED the TSC approves the proposed release cadence proposal in principal with details and policy to be provided by the task force by Sept 17th
07:29:17 From Kenny Paul (LFN) : Or earlier ;-)
07:29:51 From Catherine Lefevre : David has a good sense of humor !!
07:30:36 From Krzysztof Opasiak : thank you everyone! I need to drop. see u next week
07:30:49 From Catherine Lefevre : take care KRzy !
07:34:44 From Kenny Paul (LFN) : #topic guilin schedule
07:38:42 From Kenny Paul (LFN) : #vote Does the TSC want to keep the existing Guilin release schedule that was approved on June 24? +1, 0 -1
07:39:03 From Catherine Lefevre : #vote +1 - keep
07:39:04 From Ranny Haiby (Samsung) : #vote +1
07:39:05 From Andreas Geissler : #vote +1
07:39:05 From Ciaran Johnston : #vote +1
07:39:06 From Eric Debeau : #vote +1
07:39:06 From Jason Hunt : #vote +1
07:39:08 From Srini Add : #vote +1
07:39:09 From Ning So : #vote +1
07:39:09 From Fernando (Fred) Oliveira : #vote +1
07:39:09 From Dong Wang (China Telecom) : #vote +1
07:39:10 From Timo Perala : #vote +1
07:39:13 From Sai Seshu : #vote +1
07:39:19 From Olivier Phenix (Bell Canada) : #vote +1
07:39:56 From Kenny Paul (LFN) : #endvote
07:41:02 From Kenny Paul (LFN) : #AGREED the existing Guilin release schedule that was approved on June 24 remains in place.
07:43:15 From Kenny Paul (LFN) : sorry for the background noise from me.
07:47:42 From Catherine Lefevre : tag for Guilin release: 7.0.0.
07:49:04 From Kenny Paul (LFN) : #topic RelEng
07:51:02 From Kenny Paul (LFN) : #topic O-RAN licensing
07:52:38 From Kenny Paul (LFN) : #topic October event
07:52:41 From Kenny Paul (LFN) : https://wiki.lfnetworking.org/x/9QhoAg
07:52:46 From Kenny Paul (LFN) : proposals
07:52:49 From Kenny Paul (LFN) : ^^
08:06:07 From Alla Goldner : #info Alla Goldner, Amdocs
08:06:19 From Alla Goldner : sorry for being late
08:12:48 From Kenny Paul (LFN) : #topic ORAN licensing
08:20:12 From Timo Perala : @Kenny: could you remove the bullet "cross-community: xgvela, opnfv/cntt, feedback from end-users" from "Suggest 'ONAP Theme'" and move it under "recommendations based upon experience with June event" in "Upcoming Events" agenda topic. Thx.

ONAP Meeting Info

TSC 2020-08-27

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

Attendance

Agenda Items

Honolulu Release Schedule

Guilin Release Status

RelEng/Infrastructure

Subcommittee Update

TSC Activities and Deadlines

Upcoming Events

Zoom Chat Log