Page Comparison

START RECORDING

PARTICIPANT LIST

• 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  - 10/21 - DONE
• Sign-Off - DCAEGEN2-2954  Targetted 11/18  11/22 - DONE
• Istanbul Release Requirements
• Istanbul Impact View per Component
• 0: Integration Weather Board for Istanbul Release
• Pairwise testing  - DCAE Pair Wise Testing for Istanbul Release + include E2E slicing usecase test reference - COMPLETED
• 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

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

Vijay Kumar 

• Release Planning: Jakarta
• R10 M1 -DCAEGEN2-2979 - Due  02 Dec 2021 
• ARC - ONAPARC-724 (Scheduled for 01/11/2022)

Vijay Kumar 

-- Topic discussion deferred to next week – 

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

Vijay Kumar 

• 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  - DCAE Services - Logging Evaluation
• 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 Best Practice Proposal for Standardized Logging Fields

Henry Yu 

Dong Wang 

Ahila P 

DCAE requirement/impact assessment

Slides: CCVPN support for Intent-based networking and closed-loop

References:   https://wiki.onap.org/display/DW/Jakarta+release+-+functional+requirements+proposed+list

•   REQ-XXXX Smart Intent Guarantee based on Closed-loop in R10
•   REQ-XXXX CCVPN support for Intent-based networking and closed-loop - Jakarta Enhancements

Comments/To DO

• Syncup with Slicing usecase team to identify dcae component impact and flow 
• Document AAI api info and DCAE processing impact details 
• Determine if existing configuration model can be reused for supporting this usecase
• Next step - Once REQ approved by ARC/Usecase, create DCAE EPIC with specifics and review updates with DCAE team.

Shabnam Sultana 

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