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

« Previous Version 3 Next »

Bridge

New time (Effective from 03/14/2019 - until DST Ends)

Thursday, 9.00 – 10.00 AM EDT/13.00 -14.00 PM UTC

Bridge - zoom.us/j/824147956 

Recording:

TBA

Attendees:

Host: Vijay Kumar




Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links
1
Project Status

START RECORDING

PARTICIPANT LIST

2
El-Alto Commitments

Release candidate

EarlyDrop  (Code completion and artifact released by August 2, 2019) 5.0.0

  • ConfigbindingService
  • CloudifyManager
  • Bootstrap
  • Plugins (k8s, Dmaap)
  • ServiceChangeHandler
  • InventoryAPI
  • DFC
  • PM-Mapper
  • Deployment Handler

Branching will be done with released component by tomorrow; master branch can be used for Frankfurt work (need minor version updated to avoid conflict with El-Alto patch/bug fixes)


Second/Final El-Alto drop 5.1.0

Docker containers that are finished to be released Aug 30

  • k8s-dcae-cleanup-container
  • configbindingservice (cherry picked to el-alto?)
    • only in master

Code completion and artifact released by Sep 6, 2019

  • BlueprintGenerator (DCAEGEN2-1700)
  • TCA
  • VESCollector
  • SDK
  • RESTConf
  • Dashboard
  • HV-VES
  • PRH
  • PM-Mapper (minor updates)
  • DFC
  • SON-Handler
  • Mapper

Branching/tagging & new CI-job for el-alto COMPLETED for above components


Branching for following completed (same as Dublin)

  • TCA
  • VESCollector
  • SDK
  • RESTConf


 3
Frankfurt features 

Review commitments for Frankfurt from DCAE standpoint

Frankfurt Release Requirements

 4
 DL Handler

DL Handler advancement from POC done in Dublin

  • Integration with DMaaP
  • K8s integration pending

DCAEGEN2-1849 - Getting issue details... STATUS

 5
Security vulnerabilities

  DCAEGEN2-1808 - Getting issue details... STATUS

 6
VES spec 7.1.1 updates Review planned updates for VES 7.1.1
7
CBS TLS in SDKPiotr Wielebski

ticket: https://gerrit.onap.org/r/#/c/dcaegen2/services/sdk/+/94266/

Confluence: TLS support for CBS - Migration Plan

"Library Enhancement (CBS java sdk - DCAEGEN2-1552, CBS python util - DCAEGEN2-1551)

  1. Verify if the new environment setting for TLS (below) added by K8s plugin is visible within POD.
    • CONFIG_BINDING_SERVICE=<cbs_k8s_service_name>
    • DCAE_CA_CERTPATH=<path>
  2. If DCAE_CA_CERTPATH is defined, use the cacert for establishing secure end-point to interface with CBS (port 10443)
    1. An optional CBS_CONFIG_URL will be exposed providing the exact URL to be used for configuration retrieval. Application/Libraries can use this URL directly instead of constructing URL from HOSTNAME (which refers to ServiceComponentName) and CONFIG_BINDING_SERVICE env's.  By default, this URL will use HTTPS CBS interface
  3. If TLS env is undefined, use R4 service name and port (10000) to interface with CBS (HTTP)

Note: Libraries should stop using Consul service discovery to find CBS; instead rely on kubernetes DNS name (exposed via env CONFIG_BINDING_SERVICE) and port 10000 for HTTP and 10443 for HTTPS. Service registration on Consul will not be done for CBS TLS service"

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. 
  2. 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;










  • No labels