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 2 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:


Attendees:

Host: Vijay Kumar




Discussion Topics:



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

Vijay Kumar

START RECORDING

PARTICIPANT LIST

2
E2E Network slice impact

 LIN MENG Swaminathan Seetharaman

REQ-146: Usecase review/ DCAE impact

DCAEGEN2-1878 - Getting issue details... STATUS


3
Frankfurt features 

Vijay Kumar  

Review commitments for Frankfurt from DCAE standpoint

4
VES spec 7.1.1 updates

 alok411

Review planned updates for VES 7.1.1

AttServiceSpecification-VesEventListener-v7.1.1 - AG1 DRAFT.docx

VES Event Registration Specification 3.2.1 Draft.docx

  • Impacts VES Collector to use new VES schema file (CommonEventFormat_30.1.1.json)

Provide any feedback by 10/24 to alok411. Targeting formalize/release of VES updates by EOM; will be work with VNFSDK and Modelleing for release.

5
CBS TLS in SDKPiotr Wielebski

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


"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

 6
Notice: Meeting time change
New meeting time effective from 11/07/2019 (until 03/05/2020) 

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

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