Lingli Deng

Murat Turpçu 

David McBride

Review of RC2 - NO GO; Next Review planned on June 1st, 2020 including offline status

• Requirements/Use Cases E2E Testing:
  • 30 out of 32 are completed
  • 1 out out 32 are at 90% completion
  • 1 out of 32 are below 90% completion
• Integration Dashboard
• Integration Test Blocking Issues
• Frankfurt Milestone Status
• Successfull 72H Stability Test Run over the weekend

Next Steps:

• Need to check which use cases are missing between Frankfurt Release Requirements and 2: Frankfurt Release Integration Testing Status - missing #45, 43 etc.

      These have disappeared from v145 of 2: Frankfurt Release Integration Testing Status

      Some of the use case/requirements tests have been "re-numbered"

Investigations confirmed no issue for former #43, #45 - Traceability investigation will be continued

Item #43 was associated with REQ-76. At some point, #43 was renumbered as #37. You can see this if you examine v. 112 of the integration test status page and find #43, then compare that to #37 in the current version.

Item #45 was associated with REQ-17. At some point, #45 was renumbered as #39. You can see this if you examine v. 112 of the integration test status page and find #45, then compare that to #39 in the current version.

•  Need to get additional information from the Integration Lead based on Morgan Richomme  e-mail - https://lists.onap.org/g/onap-tsc/message/6429 => Still Missing ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM Fernando Oliveira , Byung-Woo Jun

• Get all final dockers for RC2 from Project Teams - Frankfurt Readiness dashboard
• "Verify readiness of release artifacts" to be assigned to Morgan Richomme  who will give the greenlight
•  Finalize the Release Note
  •  SECCOM Hero (Krzysztof Opasiak ) will provide inputs for the Security section for each project
• Update the Architecture content in Readthedocs => To be produced by Architecture subcommittee (Doc team can help to update the content in readthedocs).
  • The following projects were not part of the Frankfurt release - it should be documented: 
    • Logging/POMBA
    • DCAE/Holmes
    • CLI
  • Chaker Al-Hakim - Doc Community will meet to discuss the new Architecture diagram (RTD)
  • Chaker Al-Hakim - Need to provide the new diagram to Brandon Wick based on RTD discussions

TSC Vote required

 David McBride

cl664y@att.com

Guilin Release Requirements - Candidates List is now frozen (REQ-382)

•  4 Use Cases
•  22 Functional Requirements
•  29 Non-Functional Requirements
•  2 POCs

Guilin Impact View per Component

• Requirements → Architecture → TSC review 
  • Alla.Goldner to confirm these requirements have been reviewed except requirements from SECCOM, Control Loop for the release but it would be great to catch up. For the next release, ALL REQS should follow the flow "Requirements → Architecture"
  • Chaker Al-Hakim then to review these approved reqs with the Architecture subcommittee and update the Arch Review field accordingly

 Action: Chaker Al-Hakim , Alla.Goldner , Paweł Pawlak , Pamela Dragosh, David McBride - work together to improve the upfront process based on Guilin Lesson Learnt i.e. Single Backlog of requirements; Identify during the requirements review what is subject to Architecture review or not, etc.

• Companies contributing to UseCase/Functional requirements are asked to support project teams to implement non-functional requirements as M1 entry criteria.
• Developers/Testers identified (how many people?)
• Requests/Feedback from PTLs:
  • Limited Committers
  • Enough information to understand the code change
  • Acceptance criteria 
• TSC priority currently set to 4 (until TSC prioritization is completed) except the requirements already voted by TSC as Frankfurt Waiver.

• Project LifeCycle Review completed by M1. 

  • https://wiki.onap.org/display/DW/ONAP+Project+and+Component+Lifecycle

  • https://wiki.onap.org/display/DW/Project+Maturity+Review+Template

  • : https://wiki.lfnetworking.org/pages/viewpage.action?pageId=25364127&preview=/25364127/28738708/ONAP%20Proj%20Lifecycle%20and%20Review%2015Jan2020%20v1.pdf

 Trevor Lovett

Takamune Cho

Shankaranarayanan Puzhavakath Narayanan

 Congratulations to our new Committers:

•  VNFRQTS: Alan Weinstock  - https://lists.onap.org/g/onap-tsc/message/6409
•  APPC: Rupinderjeet Singh  - https://lists.onap.org/g/onap-tsc/message/6422
•  OOF: krishna moorthy - https://lists.onap.org/g/onap-tsc/message/6435

cl664y@att.com

• 2020 TSC priorities - Review ONAP Focus

  • Implement the "Requirements" Subcommittee - Completed
  • Role of ONAP to support CNFs:  ONAP CNF Task Force
  • CNTT/ONAP Partnership:  OVP PH2 (Cloud Native)
  • Review Release Cadence (Ongoing) 
  • Implement Project Review/Lifecycle (Ongoing) + A.P. from TSC 4/16
  • Promote "What we have done" (Not yet started)
  • Deliver Frankfurt and Guilin 

• SPC review
  • SPC Presentation: 01 Jun 2020 - Alla.Goldner will represent the ONAP TSC

Kenny Paul