Bridge

[dcaegen2] Team ONAP11, Wed UTC 14:30

https://zoom.us/j/824147956

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 824 147 956
International numbers available: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmekdG0WHlAnv3Zp

Recording:

DCAE_Weekly_03182020.mp4

Attendees:

Host: Vijay Venkatesh Kumar



Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status


3/18




DCAE Blockers/High priority

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

  • DCAEGEN2-2120 - Dashboard error on blueprints from inventory (requires fix on runtimeapi and bp-gen + Dashboard + Bootstrap blueprints)
    • Dashboard and Bootstrap released. Bp-gen/RuntimeAPI - Testing in-progress
  • DCAEGEN2-2129 - Public HTTP exposure from DCAE (CBS/30415) - Impact remote K8S cluster deployment - Reopened
    • CBS closed
    • VES pending Integration team (OJSI-116)
    • HV-VES - pending Nokia update



DCAE Outstanding Jira & MED priority bugs

Open items from last week

2
DCAE bootstrap updates

Blueprints delivery

  • PMSH  - Merged  (1.12.2)
  • SON_handler - Merged
  • RESTConf - Merged (EL-Alto version) (1.12.3 - Release pending)
  • DL-Handler  - WIP (image released)
  • Heartbeat - Merged (EL-Alto version)  (1.12.3 - Release pending)
  • VES Mapper - Merged (EL-Alto version)  (1.12.3 - Release pending)
  • BBS_Eventprocessor - Merged  (1.12.2)
  • DFC - Merged

Reference : https://lists.onap.org/g/onap-discuss/message/20046  Blueprint management for Frankfurt - DCAEGEN2-2041




RC0 PREP

Documentation status

3
VES 7.1 Release

3/18, 3/11 - Documentation updates is pending - DCAEGEN2-2067

4
CBS TLS in SDK

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 plugin released (2.0.0) and corresponding CM container released. Platform updates completed. Need test of HV_VES with new plugin - Piotr Wielebski

5
Repo Branching 

Repository branching for Frankfurt

  • 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
6
Demo planning
  • Demo to scheduled for PMSH and TCA-gen2 -  Targetted for 04/01/2020 
  • Demo for MOD - Either 04/01/2020 or  












Certificate for components/instance (wild card support)>Frankfurt

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

2/20  - DCAEGEN2-2084 - Getting issue details... STATUS to track this request for DCAE; AAF dependency will be discussed post Frankfurt and corresponding AAF Jira to be created






Frankfurt Artifacts Release versions


Open Action Items



Seeking Community support

Topic/JIRACurrent Status Planned Work
Docker build consistentency ( DCAEGEN2-1579)

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
Need volunteer from community to support
  • Standardize pom/jjb template for all dcae component (java and python)
    • Plugin list alignment with oparent
    • Python build dependency on script to be reduced;




Page viewed times