2020-06-03 DCAE Meeting Notes

Bridge

https://zoom.us/j/98967242523 
Meeting ID: 989 6724 2523
One tap mobile
+16465588656,,98967242523# US (New York)

Dial by your location
        +1 646 558 8656 US (New York)
        +1 669 900 6833 US (San Jose)
        877 369 0926 US Toll-free
        855 880 1246 US Toll-free
Meeting ID: 989 6724 2523
Find your local number: https://zoom.us/u/ad1U59khic

Recording:

No recording available (encountered issues with zoom connection during meeting; recording files couldn't be retrieved)

Attendees:

Host: @Vijay Kumar



Discussion Topics:





 Time (est)

 Topics

 Requester/Assignee

 Notes/Links









START RECORDING

PARTICIPANT LIST

1



Project Status

@Vijay Kumar

Release Status  

Frankfurt Milestone Status#RC1







DCAE Blockers/High priority

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







DCAE Outstanding Jira & MED priority bugs 

DCAEGEN2-2263: Ingress services on DCAE MOD cannot resolve the diffrerent urlsClosed - Ingress services on DCAE MOD cannot resolve the diffrerent urls 

05/27 - All remaining bug/Jira pushed for Guilin

DCAEGEN2-2218 - Deferred to Guilin; pending Security team confirmation

DCAEGEN2-2219 - DFC's SFTP client doesn't protect from MITM attacks (Guilin)  -  Plan to disable SFTP; need help with Test

   06/03 - Keep SFTP and necessary enhancement to be supported by Nokia. To be confirmed with Oskar/Damian 

DCAEGEN2-2141 - Documentation warning 

3



AAF change impact

@Fiachra Corcoran @Jack Lucas

aaf_agent (2.1.20) generates cert as root; this prohibits making change to cert within container (as most of containers are running as non-root).

  • one option is for separate truststore for external (discussed under CMPv2)

  • resolve the ownership for current cert/truststore to non-root user (+ common onap usergroup + and add this usergroup into container)

    • change aaf_agent to default to non-root

DCAE change to be assessed based on CMPv2 proposal; generic onap/usergroup to be discsussed with AAF team - @Vijay Kumar

AAF-1156: Certificate generated via AAF init container are root ownedOpen

06/03 - Discussed with @Pawel Baniewski ; he is looking to incorporate this part of CMPv2 proposal/design.

5



Guilin 

@Vijay Kumar

DCAE Guilin Priorities

Platform 

  • Plugin migration from CCSDK to DCAE (CCSDK-2325 & DCAEGEN2-2207 )

    • Plugin load/bootstrap (in-progress)

    • blueprint-generator (in-progress)

    • Blueprint impacts (using pg/dmaap)

  • K8S plugin optimization   (DCAEGEN2-2215 - allow env support for docker_config, DCAEGEN2-1791 - Switch to containerizedServiceComponent nodetype); bpgen (Jira to be ref)

  • Plugin/type file import (DCAEGEN2-1789) (Submitted/WIP)



Requirements from OOM team to be discussed with team

  • All logs to STDOUT

  • AAF integration must be configurable

Review backlog Jira/commitment for Guilin



Guilin Release Requirements





DCAE multisite deployment

@Pawel Baniewski

Discuss impact of DCAE multisite deployment on AAF and CMPv2 - Remote K8s cluster deployment of DCAE MS





Cloudify recursion limit



DCAEGEN2-2136: Cloudify unable to parse certain micro service policiesClosed 

@Joseph O'Leary  - Will check if this Jira is required for Guilin or can wait until Cloudify 3.x upgrade is available (stretch goal for Guilin) 





MOD OnboardingAPI

@Joseph O'Leary

  • To verify OnboardingAPI has delete option - @Vijay Kumar

  • Bp-gen issue for DFC spec - @Joseph O'Leary to verify with bp-gen 1.3.1 jar









Next weekly meeting (06/10)  to start at 11 AM ET / 15.00 UTC 

Frankfurt Artifacts Release versions

Check "Artifacts released" section under RTD - https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/release-notes.html

Open Action Items

#3 -DCAE change to be assessed based on CMPv2 proposal; generic onap/usergroup to be discsussed with AAF team - @Vijay Kumar

New Action items



Seeking Community support

Topic/JIRA

Current Status

 Planned Work

Topic/JIRA

Current 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;