Component owner expected to add specific installation-helm.rst (similar to https://gerrit.onap.org/r/c/dcaegen2/+/124070) to explain the properties/override specifric to application
Release notes and Deployment notes (common) has been updated
Discuss DCAE transformation planned items for J release - DCAEGEN2-2773
Priorities
Switch components to latest SDK version
OOM charts updates to disable Cloudify/handlers (CBS may be exception depending on above item)
Iteration 1 (once OOM branching is done)- Disable all cloudify/handlers under dcaegen2
Iteration 2 (M3/Jakarta)- Move VESOpenAPI and CBS? to dcaegen2-services
Integration testsuite migration
Helm flow support through MOD
DMaap Provisioning optimization
Pub/sub credential handling alignment - OKAY to proceed
Topic/Feed cleanup on undeploy -
Topic cleanup to be split into separate Jira and assessed later ; Feed cleanup OKAY to proceed.
Impacted by AAF removal, Strimzi Operator introduction
Part of helm migration, CLoudify/platform repo/build/deployment will be disabled in Jakarta. ollowing repositories will be locked and jobs disabled on or after FOllowing repositories have been marked as RO (CI will be removed around M1)
dcaegen2/platform/plugins
dcaegen2/deployment - updated to remove CM container build - OPEN
dcaegen2/platform/blueprints (bootstrap)
dcaegen2/platform/configbinding
BBS-Eventprocessor (dcaegen2/services) - Builds and sub-component repo will be removed post ARC meeting/review (M2).
*Istanbul container will be final version for above repository (any critical issues raised after will be assessed case by case)
Current issues - CSIT management if migrated to dcae repo + docker tagging (conflict with master for python components)
11/0102/2021 - Automated Repo Creation via INFO.yaml10/26/2021 - Gerard Nugent /Ericsson team prefer to split PMSH into separate repo. Vijay Kumar will share the process/timeline on next meeting; KPI-Ms, Slice-Analysis will continued existing shared repo. Gerard Nugent to notify when ready to split repo.
Other ONAP features/changes with DCAE impacts for Jakarta
Pub/sub API change - may need to integrate with new SDK provided by DMAAP team; all DCAE MS will have impact to align with new SDK.
SDK client lib need to have backward compatibility with MR (controlled via ENV/deployment property)
Mapping service - Alternate solution proposed by Fiachra Corcoran /DMAAP team could be candidate solution; avoid technology dependency and can be handled generic across all MS without much impact
Provisioning API will change - DCAE helm template job MR provisioning template/scripts to be revisited under Strimzi/Operator