2020-02-13 DCAE Meeting Notes

START RECORDING

PARTICIPANT LIST

• Release artifacts via self-release working with committers by M4 - Service Component owners
• Share current list of release artifact version - Vijay Venkatesh Kumar

Outstanding gerrit  - https://gerrit.onap.org/r/#/q/status:open+age:1week++dcaegen2

Frankfurt Defect Status

High priority bugs - https://jira.onap.org/browse/DCAEGEN2-2039?filter=12205

Sonar coverage - https://sonar.onap.org/projects?search=dcaegen2&sort=-name

2/13 - Sonar cloud migration completed DCAEGEN2-2065 - Getting issue details... STATUS  https://sonarcloud.io/organizations/onap/projects?search=dcaegen2. Following components are not meeting compliance

• SDK - Piotr Wielebski
• TCA-gen2 - LUKAI
• PMSH - Joseph O'Leary

Deployment documentation (WIki) - DCAE R6 Service Component (On-demand) deployment Instruction

2/13 - On-demand component/installation steps should be documented into the wiki by M4

Blueprint management for Frankfurt - DCAEGEN2-2041 - Merged- https://gerrit.onap.org/r/#/c/dcaegen2/platform/blueprints/+/101079/

2/13 - All component owners should move their corresponding blueprints into "blueprint" repo as noted on the jira.

1/23, 1/9 - VES 7.1.1 not released yet (based on VNFREQ doc); new json schema integration on VESCollector on-hold.

1/30 - DCAEGEN2-2048 created for Frankfurt VESColector update (Impacts VES Collector to use new VES schema file (CommonEventFormat_30.1.1.json)

2/6  -  DCAEGEN2-2067 - Getting issue details... STATUS created for VESCollector API/spec updates under documentation;

2/13 - Need volunteer to support DCAEGEN2-2067 documentation updates

Review recent discussion on : https://gerrit.onap.org/r/#/c/dcaegen2/services/sdk/+/94266/ and identify next step

Confluence: TLS support for CBS - Migration Plan

Current implementation relies on trust.jks being available. Following options to be explored

• Option 1: Work/address issue around using cacert.pem for CBS connection (original proposal)
• Option 2: Enabled use_tls: true for all DCAE MS deployment (in blueprint) to ensure all AAF cert/trust and distributed (regardless of the MS/component being setup as server or not)
• Option 3: Modify K8s plugin to include trust.jks distribution by default along with cacert.pem

Note: Current SDK change https://gerrit.onap.org/r/#/c/dcaegen2/services/sdk/+/94266/ relies on Option#2

12/5 - SDK changes completed; Plugin change pending (need impact assessment on https://gerrit.onap.org/r/#/c/dcaegen2/platform/plugins/+/98857/ ) + pending review/test on https://gerrit.onap.org/r/#/q/project:dcaegen2/platform/plugins

2/6 - TLS init container updates completed (2.1.0); Plugin WIP,  SDK - Test only

2/13 - Plugin changes submitted/under-review

DMaap HTTP port will be disabled (MR)

• HTTP Ports
• Port: 3904, Nodeport: 30227
• HTTPS Ports
• Port: 3905, Nodeport: 30226

DBCL 

• Dmaap plugin

DCAE Impact

• Platform - ServiceChangeHandler and PolicyHandler
• SDK - Dmaap Client (verified for BBS)
  • Dependent on plugin change (DCAEGEN2-1938) for cacert distribution in different format
• DCAE MS
  • Upgrade to Dmaap Client SDK
  • Blueprint impact
  • Testing
  • Switch to secure topics via DMaap plugin integration

2/13, 2/6, 1/23, 1/9 - DMAAP 3904 support continued for Frankfurt; will be cut-off in Guilin release. EPIC for DCAE impacts for Guilin (DCAEGEN2-2015)

• New Operation policy will be configured in Policy-Apex module.
• CL structure discussed with Liam (Policy); actors not clear

VES Structure alignment can be assessed for Guilin

DCAEGEN2-1643 - Change submitted; under-review. This will require updates to the component spec for application leveraging new properties.

• Standardize pom/jjb template for all dcae component (java and python)
  • Plugin list alignment with oparent
  • Python build dependency on script to be reduced;