#AGREED- TSC Approved that Project can perform Self-Release for Guilin Maintenance
#AGREED the TSC approves the Honolulu release plan as per the November 20th draft, with adjusting M1 to occur on Jan 11
#AGREED the TSC agrees that the 5 best practices requirements presented by SECCOM today (i.e. , , , & ) become best practices on new containers for Honolulu.
TSC 2020-12-17 #AGREED proceed with deprecation of Resources and Repositories page as presented, leaving the current page in place with new pointers to the proper resources.
TSC approved to Disable jenkins jobs incl. SonarCloud, Daily CI + in OOM while keeping Helm Chart + document in RDT; repo not lockedfor the following projects in Frankfurt: Pomba, PNDA, other logging submodules and SNIRO Simulator
#AGREED TSC approves Rc1, Rc2 and Sign-Off as all occurring on Nov. 19th
#AGREED TSC meeting on Nov 26 will be cancelled due to the Thanksgiving holiday in the U.S.
Guilin RC0 exceptions have been closed
TSC agreed that the release note will only focus on the Guilin USe Case, Functional and non functional requirements -Guilin Release Requirements+ former use cases/functional reqs approved by the Integration Team? If an issue occurred on previous use cases/blue prints/functional reqs then we invite people to open a JIRA ticket against Guilin for assessment
TSC approved our new SO committer: Ramesh Parthasarathy - #7290 (onap.org)
October
TSC approved to cancel the TSC call on Oct 15th, 2020 (LFN DDF Fall Event) - #1853 (onap.org)
TSC approved kickoff date for Honolulu is end of day Oct 16th, 2020 i.e. Global requirements (functional and non functional requirements) to be available for the TSC to be reviewed and prioritized
TSC approved Configuration & Persistency Service (C&PS) to be an independent project - #1868 (onap.org)
TSC approved all the projects passing their RC0 with the conditions that OOM, SO and MSB will complete their remaining tasks by Thursday Oct 22nd, 2020 + Guilin NF requirements Green/Yellow. Guilin NF Red are moved to Honolulu.
TSC approved the use cases (REQ-347, REQ-345, REQ-342, REQ-325) and the following functional requirements (REQ-334, REQ318, REQ-319, REQ-321, REQ-322, REQ-327, REQ-352, REQ-324, REQ-331 and REQ-341) that they have met RC0 Criteria - #1881 (onap.org)
TSC approved that all functional requirements with the exception of REQ-339 have successfully passed RC0
TSC approved RC0 is conditionally approved with the SO "war room" being in place until the issues are resolved.
TSC approved moving RC1 to Nov. 5 and release Sign off to Nov. 19.
TSC approves any requirement marked as "Green" as "GO" for M4
TSC approved projects that have completed their M4 tasks and exceptions for SO, VNFSDK, SDNC, AAI, MultiCloud and MSB to be completed by RC0 or earlier.
TSC approves the 2021 budget and priorities as set in LFN 2021 ONAP Project Inputs_V1.pdf, with the addition of the #info notes in the Zoom chat
TSCapproves moving Guilin RC0 to Oct 12 and moving all remaining milestones by one week,with Sign-off will occur on Nov 12
August
TSC agreed that only GPL v3 should be removed from the containers for the Guilin Release, distributed by the ONAP Community
TSC approves any requirement marked as "Green" and "Yellow" as "GO" for M2/M3
TSC approved CLAMP, SDNC/CCSDK, Holmes projects as successfully passing their M2/M3 milestones.
During the TSC call (8/13), TSC approved the Guilin M2/M3 milestone including REQ-388, REQ-350 and projects that have completed their release management tasks with the condition that VID, VFC, VVP,UUI, MSB and Modeling finalized their architecture review within the next two weeks i.e. no later than August 27th, 2020
TSC approved the creation of new repositories for the Integration Team (testsuite/cds; integration/terraform; integration/simulators/5G-core-nf-simulator) - https://lists.onap.org/g/onap-tsc/message/6991
TSC approved to amend the Exception Process for waiver as follows: "A waiver request is submitted to the TSC using the approved template. Ask whether there are objections to a waiver. If any TSC member objects, then a review team will be formed and the current process followed".
TSC approved the Solution 2 proposal for Adding Committers to an existing project i.e. TSC Post review of Committers.
TSC approved the promotion of Multicloud, SDNC & VFC to the Mature state
TSC approved the release cadence proposal in principal with details and policy to be provided by the task force by Sept 17th
TSC approved the existing Guilin release schedule, that was approved on June 24th, remains in place.
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
The changes to the TCC positions; Removal of Infrastructure Coordinator, align 5G and Edge to the Requirements Subcommittee, Cloud Native to the CNF Taskforce, and AI/ML to the Control-loop subcommittee.
TSC approved Option 1 concerning Non Functional Requirements i.e. Approve all the non functional requirements for M1 so the project teams can try to improve during the Guilin timeframe until M4 (Code Freeze)
TSC approved M1 Guilin Milestone including REQ335-338
TSC approved with the recommended promotion of AAI, CCSDK, DCAE, DMaaP, ExtAPI, Modeling, OOF, Policy, SDC, SO & UUI from the "Incubation" to "Mature" project state.
TSC agreed with the recommendation that the following projects have not met the criteria for promotion at this time: CLAMP, CLI, Holmes, Portal & VVP
TSC agreed that there will be a vote on the Strong Copyleft licenses in containers at next week's TSC meeting
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
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.
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 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 (, ) - https://lists.onap.org/g/onap-tsc-vote/message/1591
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
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 lockedfor 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 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
TSC approved granting a waiver for the Portal project for 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
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 , , , and "Modeling: documentation of allotted resource model" as being in the Frankfurt release.
TSC descoped from the Frankfurt release.
TSC approved all projects that have met Frankfurt M2/M3 milestone requirements since last week.
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
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
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
REQ-140 IN PROGRESS ,