2020-02-20 DCAE Meeting Notes

 Time (est)

 Topics

 Requester/Assignee

 Notes/Links

START RECORDING

PARTICIPANT LIST

MISC

2/20 - Survey for new meeting day/time proposal  https://doodle.com/poll/tinqc7c3bpbdzirg open until 2/28

https://lists.onap.org/g/onap-discuss/message/20046

1

Project Status

@Vijay Kumar

• DCAE R6 M1 Release Planning 

  • DCAE R6 M1 Release Planning#TeamInternalMilestone

• CSIT failures - https://jenkins.onap.org/view/dcaegen2/

• M4 Jira reviews

• Release artifacts via self-release working with committers by M4 - Service Component owners

• Review current list of release artifact version - 20200420DCAEMeetingNotes-FrankfurtArtifactsReleaseversions
  
  

M4 compliance

Frankfurt EPIC progress  : https://jira.onap.org/browse/DCAEGEN2-1972?filter=11704

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

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

2/20

2/13 - Sonar cloud migration completed DCAEGEN2-2065: sonarcloud migration supportClosed https://sonarcloud.io/organizations/onap/projects?search=dcaegen2. Following components are not meeting compliance

DCAE Blockers

DCAEGEN2-2088 : PRH error after PNF relocation (BBS) - WIP

DCAEGEN2-1862 :Docker build for DesignUI Tool - Closed

DCAEGEN2-2039 : Cert failure with hv-ves - To be rebased and check

DCAEGEN2-1856 : Dashboard Error reported on blueprint upload using api - Closed

DCAEGEN2-2043 : Tca-gen2 config refresh - Closed

AAF-1081 : Env issue; blocks DCAEGEN2-2042 Update DCAE certificates (Dashboard, PMSH SAN)

DCAEGEN2-2063 : no docker builds for BBS-eventprocessor

DCAEGEN2-2090 - Datalake container no docker builds

<Jira created> - CLAMP not supporting blueprints (PMSH) with postgres plugin

Frankfurt Defect Status

High priority bugs - https://jira.onap.org/browse/DCAEGEN2-2039?filter=12205

M4 Documentation

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

2/13 - On-demand component/installation steps should be documented into the wiki by M4

2

DCAE bootstrap optimization

@Vijay Kumar

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

2/20 - All Frankfurt version to be released and blueprint updates submitted by 2/27

2/13 - All component owners should move their corresponding blueprints into "blueprint" repo as noted on the jira.

https://lists.onap.org/g/onap-discuss/message/20046

3

VES 7.1 Release

 @alok411

VES 7.1.1 release

Reference document (reviewed on earlier meeting)

AttServiceSpecification-VesEventListener-v7.1.1 - AG1 DRAFT.docx  - https://gerrit.onap.org/r/#/c/vnfrqts/requirements/+/100867/

VES Event Registration Specification 3.2.1 Draft.docx  - https://gerrit.onap.org/r/#/c/vnfrqts/requirements/+/100876/

DCAEGEN2-2048 created for Frankfurt VESColector update (Impacts VES Collector to use new VES schema file (CommonEventFormat_30.1.1.json)

DCAEGEN2-2067: VES API/swagger documentation updateClosed created for VESCollector API/spec updates under documentation;

2/17 - DCAEGEN2-2048  - VES spec update and new container will be released by Friday; documentation updates to follow next week

Need volunteer to support DCAEGEN2-2067 documentation updates

3

CBS TLS in SDK

@Piotr Wielebski

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

2/20, 2/13 - Plugin changes submitted/under-review

2/6 - TLS init container updates completed (2.1.0); Plugin WIP,  SDK - Test only

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

 4

Java 11 Migration

 @Vijay Kumar

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

DCAEGEN2-1884

2/20 - VES validated. HV-VES & BBS_EP?

2/13 - @Piotr Wielebski PRH, SDK tested successfully. HV-VES and VES testing in-progress. BBS-Ep dev WIP

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

Certificate for components/instance (wild card support)

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: support certificate generation at instance level for DCAE servicesClosed to track this request for DCAE; AAF dependency will be discussed post Frankfurt and corresponding AAF Jira to be created

DMaap HTTP → HTTPS

Parked for Guilin

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

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;