Ongoing Vote(s):
- REQ 396 - 399
July
TSC reviewed and prioritized REQ-339, REQ-385 as RANK #3 (PTL GO/NO GO)
TSC reviewed and prioritized REQ-345 as RANK #3 (PTL GO/NO GO)
TSC reviewed and prioritized REQ-386 as RANK #0 (Special GO)
TSC reviewed and prioritized REQ 335-338 as RANK #3 (PTL GO/NO GO)
TSC reviewed and prioritized REQ329 – NO GO (RANK #4) but highly recommended to kick-off the activities as a POC
TSC approved our new Multi-Cloud Committer - Eric Multanen - https://lists.onap.org/g/onap-tsc/message/6676
June
TSC approved the following priorities #1 Completion of Frankfurt and #2 Kick-off Guilin release, does the TSC approve an El-Alto Maintenance release just after Frankfurt Sign-Off TSC 2020-06-04
TSC approved to cancel the TSC Call on June 25th, 2020 (LFN Event/Public Holiday in China) - https://lists.onap.org/g/onap-tsc-vote/message/1635
TSC approved the Logging Project Path Forward Proposal (v6) - https://lists.onap.org/g/onap-tsc-vote/message/1637
TSC approved the initial 'TSC MUST HAVE' Non-Functional requirements for the Guilin Release - https://lists.onap.org/g/onap-tsc-vote/message/1639
TSC approved our new AAI Committer - William Reehil - https://lists.onap.org/g/onap-tsc/message/6506
TSC approved the creation of a new repository for the Integration Team (robot-utils) - https://lists.onap.org/g/onap-tsc/message/6521
- Resolved: That the TSC approves for the Frankfurt release, as exceptions to the Intellectual Property Policy in the ONAP charter, the non-Project Licenses described in the license scan report attached to the email https://lists.onap.org/g/onap-tsc-private/message/1020 distributed to the TSC on May 28, 2020; excluding the exceptions described as not requested or required in the attached report.
- #AGREED: the TSC signs-off on the Frankfurt release based on the following conditions
#1 Feedback from PTLs about new issues CCSDK-2425, CCSDK-2399 and Policy-2631 by June 12th EOD - work around on top of RC2 dockers and/or new patch post-Frankfurt Self-Release
#2 UseCase/Functional reqs owners to confirm by Monday June 15th that they maintain their requirements or not, accepting the risk that final regression on RC2 dockers will continue after the sign-off
TSC 2020-06-18 #AGREED anybody can build a POC. It is always appropriate to share the intent of the PoC with the TSC early to facilitate inclusion in a future release.
- What's important is to follow the guidelines to prevent breaking what has already been committed to that release.
- A PoC should not be incorporated into the CURRENT release. Approval for an inclusion exception from the TSC is required if a PoC decides they want to be converted to be CURRENT release content
- There is no deadline to list a PoC into the release requirements page ( Guilin Release Requirements cited as an example)
- PoCs cannot generate any regression issues.
- Successful PoCs from a PREVIOUS release require a commitment of resources and integration team review if requesting incorporation into the CURRENT release.
- TSC approved the recommendations from the Infrastructure Coordinator about the creation of a new AAI repository (sparky_ext) - https://lists.onap.org/g/onap-tsc/message/6591
- TSC approved the Guilin Roadmap - https://lists.onap.org/g/onap-tsc-vote/message/1660
TSC finalized the prioritization for the Guilin Release scope - https://lists.onap.org/g/onap-tsc-vote/message/1680
May
TSC approved to cancel the TSC call on May 21st, 2020 (Ascension Day) - https://lists.onap.org/g/onap-tsc-vote/message/1512
TSC approved the ONAP Guilin Release - Initial Phases - https://lists.onap.org/g/onap-tsc-vote/message/1519
TSC approved Frankfurt RC1 milestone - https://lists.onap.org/g/onap-tsc-vote/message/1554
TSC approved our new Integration Committer - Paweł Wieczorek - https://lists.onap.org/g/onap-tsc/message/6341
TSC approved our new Integration Committer - Andreas Geissler -https://lists.onap.org/g/onap-tsc/message/6342
TSC approved our new Integration Committer - Krzysztof Kuzmicki - https://lists.onap.org/g/onap-tsc/message/6344
TSC approved our new VNFRQTS Committer - Junfeng Wang - https://lists.onap.org/g/onap-tsc/message/6347
TSC approved the proposed replies to 3GPP Liaison Statements addressed to ONAP - https://lists.onap.org/g/onap-tsc-vote/message/1553
New Frankfurt RC2 date, May 26th, has been approved by the TSC - https://lists.onap.org/g/onap-tsc-vote/message/1573
- The TSC approved of proceeding with using El Alto containers for ESR for the Frankfurt release only and granting a waiver for the security issues (option #1 from Jimmy’s email) in case of the non-root pod can't be solved by May 18th EOD. If it is can not be solved by May 19th morning then the TSC approves option #1 with the conditions that ESR cross-components impact will be identified and fixed prior as a maintenance patch on top of Frankfurt release".
- TSC approved the recommendations from the Infrastructure Coordinator about the creation of a new repository (testsuite/pythonsdk-tests related to smoke tests leveraging onap_pythonsdk framework) for the Integration Team - https://lists.onap.org/g/onap-tsc/message/6408
- TSC approved the recommendations from the Infrastructure Coordinator about the promotion of Alan Weinstock as VNFRQTS committer - https://lists.onap.org/g/onap-tsc/message/6409
TSC approved the recommendations from the Infrastructure Coordinator about the promotion of Rupinderjeet Singh as APPC committer - https://lists.onap.org/g/onap-tsc/message/6422
- TSC approved to grant a waiver for the Frankfurt release regarding GPL within the containers, considering that these will be solved as part of the Guilin Release ( - REQ-380Getting issue details... STATUS , - REQ-379Getting issue details... STATUS ) - https://lists.onap.org/g/onap-tsc-vote/message/1591
- TSC approved the recommendations from the Infrastructure Coordinator about the promotion of krishna moorthy as OOF committer - https://lists.onap.org/g/onap-tsc/message/6435
TSC 2020-05-28 TSC agreed to descope "Document current component upgrade strategy" from Frankfurt AND Descope CII Badging requirement from Frankfurt AND combine the RC2 and Sign-off milestones
April
- TSC approved the tasks and prioritization for the Documentation S0W - https://lists.onap.org/g/onap-tsc/message/6120
- TSC approved to cancel the TSC Call on 4/23 due to the LFN Virtual Event
- TSC approved Control Loop Sub Committee's request: creation of a repo for storing some common code for prototyping potential Guilin release requirements.
- TSC approved to Disable jenkins jobs incl. SonarCloud, Daily CI + in OOM while keeping Helm Chart + document in RDT; repo not locked for the following projects in Frankfurt: Pomba, PNDA, other logging submodules and SNIRO Simulator
- TSC did not approve CLI project to be added to the Frankfurt release
- TSC approved Frrankfurt RC0 (Pair-Wise testing completion) with conditions. David McBride confirmed that remaining conditions have been met on 4/17 -https://lists.onap.org/g/onap-tsc/message/6156
TSC approved the OOM request about a new repository for readiness check container - https://lists.onap.org/g/onap-tsc/message/6176
TSC approved our new VNFSDK Committer - Bogumil Zebek - https://lists.onap.org/g/onap-tsc/message/6230
March
TSC confirmed Olivier Phénix as the replacement for the reserved seat vacated Alexis de Talhouët https://lists.onap.org/g/onap-tsc-vote/topic/71636263#1426
Requirements, Use Cases [ marked as ] GREEN [ in Frankfurt Release Requirements ] Approved by TSC [ (applies to v552 https://wiki.onap.org/pages/viewpage.action?pageId=81397959 ) ] TSC 2020-03-05
TSC agreed that the following projects have successfully completed the requirements for Frankfurt M4: CLAMP, ExtAPI, Modeling, Policy, VID, VVP, VNFReqs https://lists.onap.org/g/onap-tsc/topic/71404800#5940
TSC confirmed Dong Wang as the replacement for the reserved seat vacated by Huang ZongHe https://lists.onap.org/g/onap-tsc-vote/topic/71728172#1465
- TSC approved of the following projects for Frankfurt M4: AAI, DCAE, SDNC, VFC, SO, MultiCloud
- TSC approved the following requirements REQ-140 IN PROGRESS , REQ-37 IN PROGRESS , REQ-150 IN PROGRESS , REQ-84 IN PROGRESS REQ-118 IN PROGRESS , REQ-129 IN PROGRESS , REQ-76 IN PROGRESS , REQ-174 IN PROGRESS , REQ-215 TO DO , REQ-219 IN PROGRESS & REQ-227 IN PROGRESS as documented in v572 of the Frankfurt Release Requirements.
- TSC approved on 3/12/2020 the following SECCOM/PTL requests for the Frankfurt release: Best effort on OJSI tickets for Frankfurt, except for REQ-231 is mandatory with some exceptions
o Projects not participating in Frankfurt
o Projects impacted by AAF
o Non-ONAP components
o Additional exceptions considered on a case-by-case basis
- TSC approved the following ONAP mentorship submissions:
- [ intern proposal Modeling/etsicatalog ] approved with provisions to change spec to 2.7.1 from 2.5.1 and recommended alignment with the CNF task force
- [ intern proposal ETSI NFV APIs conformance test for OVP ] approved as written
TSC approved the “ONAP Automation Testing - Portal/SDC” and the “ONAP Security Requirements – SDC” [ intern ] projects to be part of the 2020 Mentorship Program https://lists.onap.org/g/onap-tsc-vote/topic/71934281#1483
- TSC approved granting a waiver for the Portal project for - REQ-64Getting issue details... STATUS for the Frankfurt release
- TSC agreed to the following- 1) list from SECCOM, [ owned by SECCOM ] 2) plan forward, [ owned by Release Manager ] 3) resume project review "MVP", [ owned by Chaker Al-Hakim & Jason Hunt ] 4) ensure that all issues are OK by RC0. [ evaluation owned by the Integration team ]
- TSC agreed new repository creation request for the bbs use case
- Frankfurt Release – M4 Code Freeze was successfully completed after the approval by the TSC of the remaining projects and requirements:
- TSC approved the following projects for M4: APPC, CCSDK, Integration, MSB, OOF, OOM, SDC, UUI, VNFSDK, PORTAL, MUSIC, AAF
- TSC approved the following requirements for M4: - REQ-267Getting issue details... STATUS , - REQ-223Getting issue details... STATUS , - REQ-231Getting issue details... STATUS , - REQ-235Getting issue details... STATUS , - REQ-239Getting issue details... STATUS & Document current upgrade strategy
- TSC descoped - REQ-64Getting issue details... STATUS from the Frankfurt release and waiving - OJSI-190Getting issue details... STATUS and requires the vulnerability to be published in the release notes.
- TSC agreed that - PORTAL-849Getting issue details... STATUS is a blocker for the Frankfurt release
- TSC approved moving the RC0 date to April 2nd
- TSC approved both repos are approved pnf-simulator and mdons use case
- TSC approved archiving the doc/tools repo
February
- TSC approved the response to the 3 requests from 3GPP as outlined on slide 3 of the "TCC Generic Network Management_Prague_3GPP SA5_LS.pdf" deck as attached to these minutes.
- TSC approved that the following requirements - REQ-140Getting issue details... STATUS , - REQ-134Getting issue details... STATUS , - REQ-76Getting issue details... STATUS , - REQ-174Getting issue details... STATUS and "Modeling: documentation of allotted resource model" as being in the Frankfurt release.
- TSC descoped - REQ-136Getting issue details... STATUS from the Frankfurt release.
- TSC approved all projects that have met Frankfurt M2/M3 milestone requirements since last week.
- TSC approved SonarCube decommission on Feb 20
TSC approved our new OOM Committer - Krzysztof Opasiak
- TSC agreed that - REQ-235Password removal from OOM HELM charts In Progress - REQ-227Complete the OJSI backlog In Progress are approved for Frankfurt
- TSC agreed that - REQ-263Perform Software Composition Analysis - Vulnerability tables Done - REQ-247Coverity integration In Progress descoped from Frankfurt
The TSC confirmed Fernando Oliveira as the replacement for the reserved seat vacated by Viswanath Kumar Skand Priya https://lists.onap.org/g/onap-tsc-vote/topic/71406067#1382
The TSC agreed that Frankfurt Release – M2/M3 milestone was successfully completed
The TSC approved the proposed exception process https://lists.onap.org/g/onap-tsc/topic/71404800#5940 & https://lists.onap.org/g/onap-tsc-vote/message/1410
The TSC approved the ReadTheDocs versus Wiki usage policy https://lists.onap.org/g/onap-tsc-vote/topic/71405726#1381
- TSC approved that code coverage criteria for M4 is removed AND migration to SonarCloud must be completed by RC0 and the test coverage value should be at 55%
- The TSC stipulate that migration to Portal SDK 2.6 (by any impacted projects) is a pre-requisite for meeting the M4 milestone delivery for the Frankfurt release https://lists.onap.org/g/onap-tsc-vote/message/1369
- TSC agreed to use the proposed updates from @Lingli for the LF Board update
January
TSC approved the Committer's' promotion (VVP, VNFSDK): Trevor Lovett - https://lists.onap.org/g/onap-tsc/message/5817
Emergency AAF Committer Promotions of Pawel Baniewski , Gerard Nugent , John Franey timebound to the Frankfurt release https://lists.onap.org/g/onap-tsc-vote/message/1358
Consensus that AAF dependencies should be deprecated in the Guilin or Honolulu releases, but any formal discussion on this topic was tabled for a future TSC meeting. https://lists.onap.org/g/onap-tsc-vote/message/1358
Renaming of the “Usecase Subcommittee” to be the “Requirements Subcommittee” https://lists.onap.org/g/onap-tsc-vote/message/1360
cancel/maintain the TSC call on January 23rd, 2020 (lunar new year) https://lists.onap.org/g/onap-tsc-vote/topic/69956823#1351
- TSC agreed that the following projects passed Frankfurt M2/M3 (post 1/21 Review) DCAE, DMAAP, EXTAPI, INTEGRATION, MUSIC, OOF, POLICY, SO, VID
- TSC agreed that the following requirements are approved GeoLocation Model (and standards harmonization), ETSI Alignment Support, SECCOM HTTPS communication vs. HTTP, Document current upgrade component strategy are approved for Frankfurt
- TSC approved the migration of the Doc repo away from using git submodules to using intersphinx linking instead - Docs migration tracker
- TSC approved our new DCAE Committer - Kornel Janiakhttps://lists.onap.org/g/onap-tsc/message/5889
- TSC approved our new VF-C Committers- hongyu zhao , Yuanhong Deng - https://lists.onap.org/g/onap-tsc/message/5890