Versions Compared

Key

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

...

S.NO Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST


  •  Review Open action-items


Istanbul Release topics


Review Outstanding gerrit submission and bootstrap updates

RC0 Tasks


Istanbul Container version - See below - 20210908DCAEMeetingNotes-IstanbulArtifactsTracker



Review Outstanding bugs 

Istanbul Integration Blocking points

Jira Legacy
serverSystem Jira
jqlQueryproject = DCAEGEN2 AND fixVersion = "Istanbul Release" AND type = Bug AND resolution = Unresolved ORDER BY priority DESC, updated DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176




Jakarata - Helm migration 

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)
  • Integration testsuite migration
  • Helm flow support through MOD 
  • DMaap Provisioning optimization


Former user (Deleted)  will share example of envsubst issue for CBS SDK migration for DFC 



3gpp OpenAPI Rel17 schema issue (Istanbul) - 

DCAEGEN2-2893 DCAEGEN2-2894 DCAEGEN2-2895

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.
  1. Submit updates to OOM repository to revert configmap in dcaegen2-services to SA88 
  2. Provide reference to oom/external-schema-repo-generator repo documentation for SA91 related configmap generation. 
  3. 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

General discussion

  • Servicemesh support 
    1. Allow http support (early J release) - identify DCAE components that rely on HTTPS only
    2. Check components which needs AAF cert
    3. Secure topic/feed dependency?


Notes from prev meeting - 

  • Impact from DMAAP-MR → Strimzi/Kafka
    • Pub/sub API change - all DCAE MS will have impact; may need to integrate with new SDK provided by DMAAP team
    • Provisioning API will change (impact job provisioning template/scripts)














Topics/Demos' for future meetings

<Topics can be added below by presenters as they are ready>






...