Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Bridge

Meeting time effective from 11/07/2019 (until 03/05/2020) 

Thursday, 10.30 – 11.30 AM EST/3.30 -4.30 PM UTC

Bridge - zoom.us/j/824147956 


Recording:


Attendees:

Host: Vijay Kumar



Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status




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

Frankfurt Defect Status

High priority bugs -

type key summary assignee reporter priority status resolution created updated due
Loading...
Refresh

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

Sonar cloud migration WIP, need to be completed by 02/20 - DCAEGEN2-2065 - Getting issue details... STATUS

https://sonarcloud.io/organizations/onap/projects?search=dcaegen2





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


2
DCAE bootstrap optimization

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

Plugin/type file distribution and upload -DCAEGEN2-2040

3
VES 7.1 Release

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; notify Pawel/Damian


3
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

10/24 - Option3 preferred; Nokia team will analyze the impact for k8s plugin updates.

11/21 - SDK changes WIP; DCAEGEN2-1938  Plugin changes under assessment

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

 4
Java 11 Migration

Discuss java11 migration & identify components to be targeted for Java11 migration/support in Frankfurt

DCAEGEN2-1884

11/21 - Integration Team working on oparent update & alpine base image; DCAE JIRA's for components will be created/assigned once dependencies are met

2/6 - BBS Ep wip for java11 migration. Frankfurt java 11 components list - PRH, HV_VES, SDK, VES, BBS-Ep

5
DMaap HTTP → HTTPS Dominic Lunanuova

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






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;




There were errors rendering macro:

  • An unknown error occurred.






  • No labels