Content Comparison

Vijay Kumar

Frankfurt Release Status  

• RC0 EPIC - DCAEGEN2-2108  - 
• DCAE Pair Wise Testing for Frankfurt Release 
• CSIT failures - https://jenkins.onap.org/view/dcaegen2/   
• Review current list of release artifact version  (screenshot provided at the bottom)
  

DCAE Blockers/High priority

• DCAEGEN2-2194  runtTime 1.0.2 exception and import error

• DCAEGEN2-2191 PH subscription error from Dmaap

• DCAEGEN2-2193  During Deployment of Pm Mapper and Data File Collector fails in R6 release

Open items from last week

• DCAEGEN2-2170  Switch DCAE MOD components to non-root user (related to DCAEGEN2-2121) 
• DCAEGEN2-2171 DL containers running as root(related to DCAEGEN2-2121)  - 4/1 - WIP
• DCAEGEN2-2173,DCAEGEN2-2181, DCAEGEN2-2175 (PMSH) - Fiachra Corcoran will priortize and send email
• DCAEGEN2-2067 VESCollector API/spec updates under documentation.
• DCAEGEN2-2141 - Documentation warning  
• AAF-1081 : Env issue; blocks DCAEGEN2-2042 Update DCAE certificates (Dashboard, PMSH SAN).
  • 4/1 - PMSH documentation to include workaround steps. 
• CLAMP-650 - CLAMP not supporting blueprints (PMSH) with postgres plugin (workaround will be to onboard policy separate and use dashboard/consul)
  • Workaround will not involve CLAMP; so this defect/fix to be checked and moved to Guilin if still issue - David Farrelly  

Vijay Kumar

Piotr Wielebski

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

3/11 - New k8plugin released (2.0.0) and corresponding CM container released. Platform updates completed. Need test of HV_VES with new plugin - Piotr Wielebski

4/1 - tested on HV-VES 1.4.0 - not working - Exception in thread "main" org.onap.dcaegen2.services.sdk.security.ssl.exceptions.ReadingPasswordFromFileException: Could not read password from /etc/ves-hv/ssl/jks.pass   

    - jks.pass is distributed only when use_tls is set to true; need to be checked if app expects cert as server?  Piotr Wielebski  

04/07 - Branching/tagging work to be started for all DCAE components/repo - expected to be completed by next week. Committer must ensure new submissions are cherrypicked into Frankfurt branch

•  dcaegen2/analytics/tca
•  dcaegen2/analytics/tca-gen2
•  dcaegen2/collectors/datafile
•  dcaegen2/collectors/hv-ves
•  dcaegen2/collectors/restconf
•  dcaegen2/collectors/snmptrap
•  dcaegen2/collectors/ves
•  dcaegen2/deployments
•  dcaegen2/platform
•  dcaegen2/platform/blueprints
•  dcaegen2/platform/configbinding
•  dcaegen2/platform/deployment-handler
•  dcaegen2/platform/inventory-api
•  dcaegen2/platform/plugins
•  dcaegen2/platform/policy-handler
•  dcaegen2/platform/servicechange-handler
•  dcaegen2/services
•  dcaegen2/services/heartbeat
•  dcaegen2/services/mapper
•  dcaegen2/services/pm-mapper
•  dcaegen2/services/prh
•  dcaegen2/services/sdk
•  dcaegen2/services/son-handler
•  dcaegen2/utils

Fiachra Corcoran Jack Lucas

aaf_agent (2.1.20) changed in Frankfurt generates cert as non-root; need to assess impact to dcae TLS init (currently uses 2.1.15).

DCAE change will be done post Frankfurt; new userstory to be created - Vijay Kumar

PMSH may need to support multiple instance per different usecase. The certificate generation should be supported at instance level (possible AAF dependency

2/20  -

JIRA cover broad aspect of standardizing DCAE component build process and docker tagging.

1. Nokia team proposal identifies best practice for docker tagging optimized-dockers-jvm.pdf. 
   1. Following components migrated to new docker tagging best-practice
      1. PRH
      2. PM-Mapper