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




NO MEETING ON  



Istanbul Release topics

DCAEGEN2-2943 - (SON-Handler FM notification fix) - Need to be checked with Integration team if can be included for Istanbul



Review Outstanding gerrit submission and bootstrap updates

RC Tasks - Release Process

Istanbul Container version - See below - 20210908DCAEMeetingNotes-IstanbulArtifactsTracker



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)
    • 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


Remigiusz Janeczek  will share example of envsubst issue for CBS SDK migration for DFC 

    • DFC/PM-Mapper config updates cannot be done via Configmap override; will require redeploy or update of application-config.json within POD
    • Enhancement - Provisioning flow to create a configmap based on resolved/merged config (which can be used for post-deploy update); resource cleanup to be considered. Separate Jira to be created for Jakarta rls - DCAEGEN2-2935


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  

  • dcaegen2/platform/plugins
  • dcaegen2/deployment - updated to remove CM container build
  • dcaegen2/platform/blueprints (bootstrap)

*Istanbul container will be final version for above repository (any critical issues raised after will be assessed case by case)




PMSH outstanding @Sagar shetty

https://gerrit.onap.org/r/c/dcaegen2/services/+/124704

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2819

  •  Overview on PMSH planned enhancements for Jakarata  - @Sagar Shetty Gerard Nugent 


DCAE repositories split

Discuss if subcomponents under https://git.onap.org/dcaegen2/services/tree/components should be split into separate individual repo

Current issues - CSIT management if migrated to dcae repo + docker tagging (conflict with master for python components)



Other ONAP features/changes with DCAE impacts for Jakarta

General discussion

  • Servicemesh support - DCAE component impact on below 
    1. Allow http support (early J release) - DCAE components that rely only on HTTPS will be impacted
    2. Components dependent on AAF cert 
    3. Secure topic/feed dependency - DFC, PM-Mapper, PNF-Reg, SliceAnalysis, BBS-Ep (question)
  • Impact from DMAAP-MR → Strimzi/Kafka
    • 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
  • STDOUT logging requirement - candidate for GR 
  • SECCOM proposal to change log structure for Security logging as Best Practice (To be reviewed/approved by TSC in coming weeks) - SecLog-TO-PTLs-v7.pptx


Jakarta release planning
Release Planning: Jakarta







Topics/Demos' for future meetings

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






...