Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status



DCAE Blockers/High priority

Jira
serverONAP JIRA
jqlQueryfilter=12210
serverId425b2b0a-557c-3c0c-b515-579789cceedb




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

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:

View file
nameDCAE weekly stndDefined Event in ONAP 2020-05-27 v2.pptx
height250


Comments/Action-items for usecase team

  • 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).
  • As the 3gpp external schema for Guilin will be static, they can built into VES containercontainer instead of dynamic schema support
  • 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.
  • Review VES updates proposed with Trevor/VNFREQ team
  • SDK adaptation for schema validation is optional. If dynamic schema retrieval is identified (based on #1) then SDK lib function can be persued
  • 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

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 

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 deploymentDiscuss impact of DCAE multisite deployment on AAF and CMPv2 - Remote K8s cluster deployment of DCAE MS





...