...
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)? |
|
Track: XGVela Presenters/Moderators: Qihui Zhao |
| ||
Track: Cloud Native in Telecom Cloud Presenters/Moderators: Qihui Zhao, Ying Li |
|
| |
ONAP Track | Key Points | Challenges | Next Steps/Action Items |
OOM Status update: what's planned internally Presenters/Moderators: Sylvain Desbureaux, Krzysztof Opasiak | Review of the planned OOM changes : Support of Helm V3 Kubernetes V1.17 (or 1.18) Migrate to Seccom recommended Versions Update defaults (use Ingress, Storage Class, Hardened OS) | Might be breaking gating during changes, impact deployments | check if Helm V3 requires Kubernetes v1.17+ |
OOM Status update: consequences on other components Presenters/Moderators: Sylvain Desbureaux, Krzysztof Opasiak | 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 Container that do not contain ONAP code should not be hosted on Nexus No Root access to DB Application config should be fully prepared before starting the container Containers must crash properly when a failure occurs No more Nodeports AAF optional (component should work without AAF even in degraded mode) HTTPS is mandatory but should be configurable (disable in case of Service Mesh as this will be offloaded to Service Mesh) Container RootFS should be mounted as ReadOnly Commit message rules for OOM | AAF removal or optional / POC SMesh | SecCom to follow up and define what disabling AAF means |
Requirements Traceability: Initial Request through TSC Approval Presenters/Moderators: Alla Goldner, Chaker Al-Hakim, Pawel Pawlak, Pamela Dragosh, David McBride, Catherine Lefevre |
wiki: 2020 June vDTF ONAP Requirements Traceability: Initial Request through TSC Approval |
| |
vFWCNF vFW CNF use case evolution | |||
CNTT Track | Key Points | Challenges | Next Steps/Action Items |
Performance |
|
| |
Traceability Test Cases |
| ||
Use cases of SDN solution |
| ||
Field Trial Status |
|
...