Page History

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

Review commitments for Frankfurt from DCAE standpoint

Frankfurt Release Requirements

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

Confluence: TLS support for CBS - Migration Plan

K8s plugin updates (DCAEGEN2-1550)

1. Cloudify deployments of service components should include following environments
• CONFIG_BINDING_SERVICE=<cbs_k8s_service_name>
• DCAE_CA_CERTPATH=/opt/dcae/cacert/cacert.pem  (this will be default unless overridden by component via blueprint)
• CBS_CONFIG_URL=https://config-binding-service/service_component_all/<scn> 
  • #scn → Unique Servicecomponent name

"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"

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