Table of Contents |
---|
Bridge
[dcaegen2] Team ONAP11, TUESDAY UTC 14:30 (09.30 AM EST)
ONAP Meeting 11 is inviting you to a scheduled Zoom meeting.
...
All attendees must set their Zoom name in First-name FAMILY-NAME (company) format
Recording:
TBADCAE_Weekly_02222022_video1808287059.mp4
Attendees:
Host: Vijay Kumar (AT&T)
Discussion Topics:
...
S.NO | Time (est) | Topics | Requester/Assignee | Notes/Links | ||||||||
Note to Moderator | START RECORDING PARTICIPANT LIST | |||||||||||
Istanbul Maintenance release | DCAEGEN2-3022 - Log4j vulnerability (2.0-beta9 to 2.14.1)
Recommendation from SECCOM was 2.16.0 in December; new CVE has been identified and 2.17.1 is the new target recommended version for now* 02/22/22 - All DCAE patche merged in OOM; main rls approved on 02/17; DCAEGEN2-3077 continued to being worked in OOM 02/15/22 - DCAEGEN2-3077 - Fix for blueprint upload issues (on gerrit); OOM submission will be done by EOW; other vulnerability patches still pending OOM review/merge 02/08/22 - Istanbul patch (https://gerrit.onap.org/r/c/oom/+/126806) under review (pending successful gating); new TSC signoff targetted 2/17 02/01/22 - Gerrit submission for OOM/doc pending to be reviewed/merged; TSC targetting 2/10 sign-off 01/25/22 - OOM merge pending ; cherry-pick oom/istanbul. Doc for maintenance rls will be done this week (will include log4j & son-handler) 01/20/22 - All impacted component updated to 2.17.1 and released; OOM update pending 01/04/22 - Upgrade impacted DCAE components to 2.17.1 once SECCOM/TSC confirms 12/17/21 - VESCollector, RESTConf, VES-Mapper impacted; new containers released using 2.16.0 | |||||||||||
Jakarata Release Updates | Completed
Ongoing
| |||||||||||
Jakarata - Helm migration | Discuss DCAE transformation planned items for J release - DCAEGEN2-2773 Priorities
To Do
| |||||||||||
DCAE MOD Demo for Helm flow support | Brief overview on underlying MOD component changes, dependencies introduced for Helm flow support in jakarta , followed by demo | |||||||||||
HV-VES Questions | Discuss open items/question VES and HV-VES topics names can be different;; Property name (for topic) naming convention to be adopted going forward as helm limits underscore; Fiachra Corcoran suggesting using CamelCase. Test integration issues discusssed (related to earlier discussion OOM Meeting Notes - 2022-02-16) | |||||||||||
Topics/Demos' for future meetings | <Topics can be added below by presenters as they are ready> | |||||||||||
...