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

Version 1 Next »

Bridge

[dcaegen2] Team ONAP11, Wed UTC 14:30

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:

TBD

Attendees:

Host: Vijay Kumar



Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status & General updates
  • Frankfurt Release 
  • Frankfurt maintenance release

LFN Developer & Testing Event 

Agenda :  https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34604523

2
 Python 3.8 migration

Michal.Jagiello@t-mobile.pl

DIscuss DCAE components 3.8 migration support

3
VES Collector performacne testing reportPawel Kasperkiewicz
  • VESCollector peformance test results
4
AAF change impact

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 

AAF-1156 - Getting issue details... STATUS

06/10 - More details on next meeting with Pawel Baniewski ; AAF_agent change/support to be confirmed. 

5
Guilin 

DCAE Guilin Priorities

Platform 

  • Plugin migration from CCSDK to DCAE (CCSDK-2325 & DCAEGEN2-2207 )
    • Plugin migration (completed)
    • 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

DCAEGEN2-2015 (remove DMAAP MR http/3904 dependency) - Fiachra Corcoranwill confirm DMAAP team plans for Guilin

6
DCAE Outstanding Jira & MED priority bugs (Guilin)

DCAEGEN2-2218 - Blocked by AAF changes (AAF-1134)

DCAEGEN2-2219 - DFC's SFTP client doesn't protect from MITM attacks (Guilin)  

   06/10 - Nokia confirmed support; need to get exception from SECCOM team - Pawel Baniewski

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

DCAEGEN2-2136 - Getting issue details... STATUS  - 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) 

Guilin

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



MOD OnboardingAPI  issue
  • DFC spec to be corrected and verify onboarding/distribution through MOD (manual deletion via PG DB can be done if required)  - Joseph O'Leary
  • Deven investigating with original DFC spec/recovery

Open question from prev meeting

  • To verify OnboardingAPI has delete option - Vijay Kumar
    • No delete api in OnboardingAPI
  • Bp-gen issue for DFC spec - Joseph O'Leary to verify with bp-gen 1.3.1 jar
    • Verified; not a bp-gen issue. 





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



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










  • No labels