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 branching
Vijay Kumar will target branching for all repository by
CI change
Repo branching (except dcaegen2 (doc repo)deferred to next week)
Update repo with nexus/raw reference to new path on master
As the default SA91 openAPI schema files are having issues, the default deployment for VESOpenAPI manager for Istanbul will be switched to SA88-Rel16 schemas (matches to default VESCollector container loaded schemas). The instructions for both VESCollector and VESOpenAPI manager RTD will be updated to reflect the same and include steps to override to SA-91-Rel16 if required. This will refer to the steps documented under oom/external-schema-repo-generator repo.
Submit updates to OOM repository to revert configmap in dcaegen2-services to SA88
Provide reference to oom/external-schema-repo-generator repo documentation for SA91 related configmap generation. Update DCAE VESCollector and VESOpenAPI manager document . - https://gerrit.onap.org/r/c/oom/utils/+/123794
Update DCAE VESCollector and VESOpenAPI manager document to reflect SA88 as default for Istanbul and include optional steps to load SA91 (based on #2)
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
; may need
to
integrate
align with new
SDK provided by DMAAP team
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
