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:

DCAE_Weekly_05272020.mp4

Attendees:

Host: Vijay Venkatesh Kumar


Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status

Vijay Venkatesh Kumar

Release Status  

Frankfurt Milestone Status#RC1




DCAE Blockers/High priority

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh




DCAE Outstanding Jira & MED priority bugs 

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

DCAEGEN2-2141 - Documentation warning 

2
ONAP/3GPP & O-RAN ALIGNMENT–STANDARDS DEFINED NOTIFICATIONS OVER VES

 Marge Hillis

Damian Nowak

Vimal Begwani


Review R7 proposal for VES and DCAE changes.

Arch Presentation STD Defined Event in ONAP May 19 2020.pptx

Let`s go thru this presentation:


Comments/Action-items for usecase team

  1. Proposal supports DCAE data collection apect only (based on VES). Any further processing/analytics is not supported in ONAP/DCAE currently (this will depend on Operators to provide 3gpp schema aware analytics). This must be documented on VNFSDK and 3GPP liason statement
  2. As the 3gpp external schema for Guilin will be static, they can built into VES container instead of dynamic schema support
  3. Design for schema store to be revisited. Need more info on how external schema will binded with xNF instance onboarded (as each xNF could rely on different on schema/version). Possibly SDC/catalog can be used as catalog to retrieve supported schemas.
  4. Review VES updates proposed with Trevor/VNFREQ team
  5. SDK adaptation for schema validation is optional. If dynamic schema retrieval is identified (based on #1) then SDK lib function can be persued
  6. For each supported 3gpp schema/domain - need transformation rules to standard VES identified part of documentation deliverable




All below topics/items deferred for next meeting
3
AAF change impact

Fiachra Corcoran Jack Lucas

aaf_agent (2.1.20) changed in Frankfurt generates cert as non-root; need to assess impact to dcae TLS init (currently uses 2.1.15)

  • 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 into separate 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 Venkatesh Kumar

5
Guilin 

Vijay Venkatesh Kumar

DCAE Guilin Priorities

Platform 

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


Requirements from OOM team to be discussed with team

  • All logs to STDOUT
  • AAF integration must be configurable

Review backlog Jira/commitment for Guilin



DCAE multisite deployment

Pawel Baniewski

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





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 Venkatesh Kumar


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;




Page viewed times