Versions Compared

Old Version 21

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version 22

changes.mady.by.user cl664y@att.com

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

15

Release Status

Frankfurt

David McBride

Review of RC2

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"

  •  Need to get additional information from the Integration Lead based on Morgan Richomme  e-mail - https://lists.onap.org/g/onap-tsc/message/6429
  • 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
  •  Next RC2 review during PTL Call on 6/1 - bank holidays in Europe so offline status will be required
  •  Finalize the Release Note
    •  SECCOM will provide inputs for the Security section for each project

TSC Vote required

#1 Descope "Document current component upgrade strategy" from Frankfurt. Part of Documentation SOW for Guilin.

#2 Assess convergence of RC2/Sign-Off dates

 30

Release Status

Guilin

 David McBride

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

  •  4 Use Cases
  •  22 Requirements
  •  29 Requirements
  •  2 POCs

Guilin Impact View per Component

  • Requirements → Architecture → TSC review 
  • Project LifeCycle Review completed by M1. 
  • 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.

 10

 Project Lifecycle Review

Logging

cl664y@att.com

ONAP Logging Proposal_V6.pdf

10

PTL Update

Documentation

Sofia Wallin

Retention policy for previous ONAP release documentation (release notes)

  • Maintaining a cumulative list of bug fixes for each release viewed as compromise to carry forward.
  • Archiving old RTD content would require a new process to be developed

10

Subcommittee Update

Architecture

Chaker Al-Hakim

ArchCom Planning and Preparations for the Guilin 

https://lists.onap.org/g/onap-tsc/message/6241

Architectural Review Requirements & Process

 5

PTL Update

 Committer's Request

 Trevor Lovett

Takamune Cho

Shankaranarayanan Puzhavakath Narayanan

 Congratulations to our new Committers:

5

TSC Activities and Deadlines

cl664y@att.com

  • SPC review
    • SPC Presentation:  

5

Upcoming Events

Kenny Paul

LFN Developer and Testing Forum: June 22nd-25th -  Virtual Event.  LFN Joint

New Dates Open Networking & Edge Summit North America 2020  September 28 & 29, 2020 at the JW Marriott LA Live in Los Angeles, CA.  

  • F2F go/no-go will be made by August 1, 2020
  • ONAP TSC Abstract “ONAP and Cloud Native” was approved.

Upcoming LFN Webinar Series:

  • June 18, 9:00 AM PT: What’s New in ONAP Frankfurt - Register Here.

15

Proposal to improve code management"

Sylvain Desbureaux Morgan Richomme

Seshu Kumar Mudiganti Krzysztof Opasiak

ChrisC Marc-Alexandre Choquette

Proposals to impove the code management in ONAP:

  • best practice to comment Gerrit patch
  • code merge only when 2 pair of eyes OK
  • no code merge for WIP
  • repo management

Update of Code Review

...