2019 TSC Decisions

Owned by cl664y@att.com
Last updated: Jan 08, 2020
7 min read

January

1/3 TSC Call

  • TSC agrees to defer any VNF Certification discussion to the VNFRQTS Project.



1/10 TSC Call

  • TSC only approves the CDI projet as POC for the Dublin Release, under the Multicloud project umbrella

  • TSC approves the Committer promotion (AAF): @Sai Gandham



1/16

1/17 TSC Call

  • TSC approves the proposed M1 Security milestone checklist as presented by Amy Zwarico. oParent checklist is informational for the Dublin release.

  • TSC approves DataLake  projet as POC only for the Dublin Release under DCAE project umbrella



1/24 TSC Call



1/29


1/31 TSC Call

  • The Casablanca Maintenance Release has been signed-off on 1/31.

  • TSC approves the Dublin Release Plan (M1) for all the projects. Documentation/Integration are conditionally passed.

  • TSC approves v207 of the Dublin Release Requirements GREEN M1 scorecard items and conditional passed on YELLOW items. RED items will be descoped or move to POC depending on feedback collected on 1/31

February

2/4


2/13



2/21 TSC Call

  • TSC did not approve M2/M3 Modeling Checklist add-ons for the Dublin Release. Follow-up discussions with PTLs are required to consider them as part of El-alto release. Suggestion is to prototype these checklists with few projects.

  • Mariusz Wagner committer’s promotion has been approved by the TSC.



2/28 TSC Call

  • Dublin Functionality Freeze (M2) has been approved by the TSC

  • Integration Checklist has been approved by the TSC

  • Multi-VIM/Multi-Cloud Project Scope change has been approved by the Architecture subcommittee - https://lists.onap.org/g/onap-tsc-vote/message/834

March

3/4:



3/7 TSC Call

  • TSC approves the M3 Modeling Checklist as a non-blocking item -"Has the Project team provided links to Data Models (e.g, JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)?""

  • TSC approves the Modeling proposal - Modeling subcommittee reached consensus on "Non MANO set identifier definition in VNF/PNF onboarded package and registration in ETSI NFV"



3/13

  • The TSC adopts UTC as the official time zone for scheduling meetings and conducting business for all projects.  All ONAP calendar entries are created using UTC start times and not to created using any local time zones. https://lists.onap.org/g/onap-tsc-vote/message/837



3/14 TSC Call

  • Dublin API Freeze (M3) has been approved by the TSC

  • TSC Policy on ONAP Maintenance Release has been approved by TSC - ONAP Maintenance Policy



3/21 TSC Call

  • TSC approves moving the M4 milestone to April 11

  • TSC agrees only individual project releases of certificates and critical security fixes in 3.0.2 with impacted area testing only

  • TSC agrees that Deng Hui should continue to be our SDO external coordinator until a new structure/election will occur



3/28 TSC Call

  • TSC approves that the tsc mailing list ('onap-tsc@lists.onap.org') will be used as point of contact for Non-MANO artifact registration in ETSI

April

  • Apr 11, 2019 TSC agrees the ONAP Release Manager recommendations about M4 i.e. NO-GO, to be reviewed on 4/18

  • Apr 18, 2019 Dublin Code Freeze (M4) has been approved by the TSC with gating conditions

  • Apr 18, 2019 TSC Agree that any requirement (use case, functional requirement, non-functional requirement), currently marked in yellow/(red), not due to testing blockers/issues, will be moved to the POC section a.k.a no more be part of the official release, if no feedback provided to Jim by 4/22 EOD

  • Apr 18, 2019 TSC agree that RC0 will shift to May 2nd with the condition that a clear plan is built at RC0 to complete the release considering the reduced scope.

  • Apr 26, 2019 The list of Open Source External Coordinators has been approved by the TSC - https://lists.onap.org/g/onap-tsc-vote/message/917

  • Apr 26, 2019 ONAP El-Alto Schedule/Focus & ONAP Frankfurt Release Milestones have been approved by the TSC  -https://lists.onap.org/g/onap-tsc-vote/message/919

May

  • May 9, 2019 TSC approved the Dublin Architecture deck (v4.0.10)

  • May 11, 2019 TSC does not require themselves to approve their weekly TSC meeting minutes - https://lists.onap.org/g/onap-tsc-vote/message/967

  • May 16, 2019 TSC approved new Policy Committers: Ram Krishna Verma and Jim Hahn

  • May 16, 2019 TSC approved new Technical Community Coordinators: Edge Computing: Ramki Krishnan- VMware; Cloud Native: Sylvain Desbureaux- Orange; Infrastructure: Xinhui Li- VMware

  • May 17, 2019 TSC approved the ONAP Pen Test Results Early disclosure process https://lists.onap.org/g/onap-tsc-vote/message/952

  • May 23, 2019 TSC approved the special repository requested by the Security Subcommittee

  • May 23, 2019 TSC approved new CLI Committer: Itohan Ukponmwan

  • May 24, 2019 TSC approved new Technical Community Coordinators: 5G: Vimal Begwani; AI (ML/DL); Lingli Deng; Network Management: Magnus Buhrgard

  • May 29, 2019 TSC approved Sonar Waiver requested by AAF, SDC and Multi-Cloud - https://lists.onap.org/g/onap-tsc-vote/message/973

June

July

  • Jul 8, 2019 TSC approved the sign-off of the ONAP Dublin Release - https://lists.onap.org/g/onap-tsc-vote/message/1076

  • Jul 11, 2019 TSC approved the The TSC approves a $50K expenditure against the budget for lab improvements (Testing & ToolChain)

  • Jul 11, 2019 TSC approved the Supercommitter proposal Super Committers

  • Jul 11, 2019 LFN Code of Conduct will replace ONAP Code of Conduct (CII Badging)

  • Jul 11, 2019 TSC approved new OOM Committers Sylvain Desbureaux, Bartlomiej Grzybowski & Milan Verespej; new SDC Committers Inna Manzon, Tomasz Golabek, Piotr Darosz and Ojas Dubey; Brinda Santh Muthuramalingam (CCSDK) and Yuanhong Deng (Modeling)

  • Jul 18, 2019 TSC approved new Committers - Bartlomiej Grzybowski & Milan Verespej, Samsung (OOM) and Ojas Dubey, Amdocs (SDC)

  • Jul 18, 2019 TSC agreed to turn on JScript code scans to establish a baseline for code coverage

  • Jul 18, 2019 TSC approves enabling CLA enforcement beginning on July 25, 2019

  • Jul 25, 2019 TSC agreed to continue with the content of M1 for El Alto Early Drop

August

September

  • Sep 2, 2019TSC agreed that @Davide Cherubini will take over from @Susana Sabater (Vodafone TSC reserved seat). Davide was previously acting as Vodafone TSC deputy.

  • Sep 19, 2019TSC approved El-Alto Waivers requested by OOF, CCDSK, AAF, MultiCloud, Policy and Portal

  • Sep 19, 2019TSC approved the latest ONAP Architecture principles

October

November

  • Nov 7, 2019 TSC approved the Milestone Exception Process  - https://lists.onap.org/g/onap-tsc/message/5592

  • Nov 7, 2019 TSC approves the warning threshold will be increased to 50% as soon as Releng can address like-for-like output in Sonar Cloud

  • Nov 14, 2019 All projects listed in green on (v. 58) of Frankfurt Milestone Status are approved for M1 (i.e AAI, AAF, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration, Modeling, MUSIC, MSB, MutliCloud, OOM, Policy, SNDC, SDC, SO, VF-C, VID, VNFReqs, VVP, VNFSDK )

  • Nov 14, 2019 TSC approved the NO GO as documented in (v. 63) of Frankfurt Milestone Status (i.e. NO GO- no impact on use cases/requirements: CLI, HOLMES, LOGGING => Re-use El Alto containers except if any blocking issue are identified during the Frankfurt testing cycle by the Integration Team. Any other finding (security, non blocking issue) should be documented in the Frankfurt Release Note)

  • Nov 14, 2019 TSC approved the Committer promotion (OOF): @Arthur Martella - https://lists.onap.org/g/onap-tsc/message/5631

  • Nov 15, 2019 TSC approved the Committer promotion (UUI): @xu ran - https://lists.onap.org/g/onap-tsc/message/5641

  • Nov 15, 2019 TSC approved the Committers' promotion (CCSDK): @nullop , @Kapil Singal (Deactivated) - https://lists.onap.org/g/onap-tsc/message/5635

  • Nov 20, 2019 The TSC approved implementing the Milestone Exception Process beginning with Frankfurt M2  https://lists.onap.org/g/onap-tsc-vote/message/1298

  • Nov 21, 2019 TSC approved the Committer's' promotion (SDC): @Ilana Paktor -https://lists.onap.org/g/onap-tsc/message/5686

  • Nov 21, 2019 TSC approved M1 Frankfurt Release Milestone (Release Planning) - https://lists.onap.org/g/onap-tsc/message/5685

  • Nov 21, 2019 TSC approved the recommendations of the Release Manager for approving the usecases and requirements as found in v.404 of Frankfurt Release Requirements

  • Nov 21, 2019 TSC approved M1 approval as YES for Network slicing considering SO, ExtAPI  UUI scope only for E2E Network Slicing. OOF is provisionally approved for E2E Network Slicing and will be reviewed at M2

  • Nov 21, 2019 TSC approved Plug and Play as meeting the M1

  • Nov 21, 2019 TSC approved that DCAE will be a prototype as per REQ-239 for the SECCOM Communication Matrix

  • Nov 26, 2019 TSC approved the Committer's' promotion (DCAE): @Joseph O'Leary - https://lists.onap.org/g/onap-tsc/message/5715

December