2021-10-26 DCAE Meeting Notes

S.NO

 Time (est)

 Topics

 Requester/Assignee

 Notes/Links

START RECORDING

PARTICIPANT LIST

NO MEETING ON Oct 12, 2021 

Istanbul Release topics

@Vijay Kumar

• 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/14  - Targetted 10/21

• Sign-Off - 11/04 

• Istanbul Release Requirements

• Istanbul Impact View per Component

• 0: Integration Weather Board for Istanbul Release

• Architecture

  • https://lf-onap.atlassian.net/wiki/display/DW/ARC+DCAE+Component+Description+-+Istanbul-R9

  • https://lf-onap.atlassian.net/wiki/display/DW/DCAE+R9+M2+Architecture+Review

• Security updates - Istanbul DCAE  - DCAEGEN2-2768: SECCOM - DCAE Vulnerability updates for IstanbulClosed

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

Outstanding patch for Istanbul 

• https://gerrit.onap.org/r/c/oom/+/125328 (sonhandler version update)

Review Outstanding gerrit submission and bootstrap updates

@Vijay Kumar

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 notes and Deployment notes (common) has been updated - https://docs.onap.org/projects/onap-dcaegen2/en/latest/index.html

Istanbul Container version - https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html#deliverables

Jakarata - Helm migration 

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

  • 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-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 Oct 22, 2021 

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

To DO

DCAE repositories split

@Vijay Kumar 

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)

10/26/2021  - @Gerard Nugent /Ericsson team prefer to split PMSH into separate repo. @Vijay Kumar  will share the process/timeline on next meeting

Other ONAP features/changes with DCAE impacts for Jakarta

@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 POC (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>

@Vijay Kumar

NA

@Tony Hansen

NA

@Jack Lucas

NA

@Former user (Deleted)

NA

@Former user (Deleted)

NA

@Former user (Deleted)

NA