Page Comparison

START RECORDING

PARTICIPANT LIST

•  Review Open action-items

NO MEETING ON 12 Oct 2021 

• Release Planning: Istanbul
• R9 M1 - DCAEGEN2-2757 - DONE
• R9 M2 - DCAEGEN2-2783 - DONE
• R9 M3 - DCAEGEN2-2841 - 08/27  09/02 - DONE
• R9 M4 - DCAEGEN2-2896   09/16 - DONE*
• R9 RC - DCAEGEN2-2923    10/1414  - Targetted 10/21
• Istanbul Release Requirements
• Istanbul Impact View per Component
• 0: Integration Weather Board for Istanbul Release
• Architecture
  • https://wiki.onap.org/display/DW/ARC+DCAE+Component+Description+-+Istanbul-R9
  • https://wiki.onap.org/display/DW/DCAE+R9+M2+Architecture+Review
• Security updates - /wiki/spaces/SV/pages/16093268  - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2768

• Istanbul Integration Blocking points

Vijay Kumar

RC0 RC Tasks - Release Process

• Pairwise testing  - DCAE Pair Wise Testing for Istanbul Release + include E2E slicing usecase test reference - COMPLETED
• Documentation 
  • 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 note updates - notes and Deployment notes (common) has been updated - https://gerritdocs.onap.org/rprojects/conap-dcaegen2/dcaegen2en/+/124433
• Release branching 
  • Vijay Kumar  will target branching for all repository by 01 Oct 2021   - DONE
    • CI change
    • Repo branching
    • Update repo with nexus/raw reference to new path on master
• Documentation (dcaegen2) branching to be completed 05 Oct 2021  - DONE

Vijay Kumar 

• • latest/index.html

Vijay Kumar 

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)Helm
  • Integration testsuite migration
  • • 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

  
  

  Former user (Deleted)  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-2935cleanup to be considered. Separate Jira to be created for Jakarta rls - DCAEGEN2-2935

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

Vijay Kumar 

Vijay Kumar 

General discussion

• Servicemesh support - DCAE component impact on below 

1. 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

• 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

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