Versions Compared

Old Version 45

changes.mady.by.user Rabi Abdel

Saved on

compared with

New Version 46

changes.mady.by.user Catherine Lefevre

Saved on

Key

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

...

 Cross Community Track

Key Points

Challenges

 Next Steps/Action Items

Track: Shift to Release Train

Presenters/Moderators: Catherine Lefevre 

›The Challenges from LFN Projects

›Release Cadence in Other Open Source projects

>Shift to Release Train & Brainstorming

Wiki notes: Shift to Release Train 2020-06-23

›How can we release more frequently, smaller scope without impacting the SW quality?

›How can we change the waterfall-ish development model?

›How can we get enough details about candidates requirements prior the release?

›How to manage the release in case of people turn-over?

›How to handle the scope and maintain a balance between Usecase/Functional reqs (attractive) and Non functional reqs (less sexy)?

  •   Identify a set of projects that could prototype the Release Train approach
  •  

     “Release cadence transition proposal” on June 25th, 2020 @ 11am UTC

Track: XGVela

Presenters/Moderators: Qihui Zhao


  •   Alignment with CNTT/CNCF TUG and O-RAN/ONAP in order to define their role as part of XGVela
  •  Introduction of XGVela to the TAC team

Track: Cloud Native in Telecom Cloud

Presenters/Moderators: Qihui Zhao, Ying Li

Image Added Image Added

  • Plan to align with CNTT RA-2 (Kubernetes)

  •  Alignment with CNTT/CNCF TUG and O-RAN/ONAP in order to define their role as part of XGVela
  •  Introduction of XGVela to the TAC team




 ONAP Track Key Points Challenges  Next Steps/Action Items
OOM Status update: what's planned internally

Review of the planned OOM changes :

Support of Helm V3

Kubernetes V1.17 (or 1.18)

Migrate to Seccom recommended Versions



OOM Status update: consequences on other components

Review of the required changes on components helm charts VS requirements

presentation of changes, use of templates, adding appender to Logback to support STDOUT as additional output







  CNTT Track Key PointsChallengesNext Steps/Action Items
Performance
  • Great Discussion around performance and it's relation to CNTT.
  • Discussion to be continued with Al Morton, Trevor, and Mike B during CVC using Al proposed 4-tier structure.

  • Continue discussion in CVC.
  • Map 4-tier structure to CNTT.
Traceability Test Cases
  • Great progress demonstrated by Cedric Ollivierto cover RA-1/RC-1 Requirements






...