Versions Compared

Key

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

Table of Contents

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_07152020.mp4

Attendees:

Host: Vijay Kumar


Image Added


Image Added

Discussion Topics:

...


 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST

1
Project Status & General updates

Review 


Next milestore M2/M3

  • Finalize API's exposed by components; swagger definition/documentation must be provided
  • DCAE ARC review planned for  
2

Frankfurt Maintenance Candidates

SON_Handler (Wipro)

  • Vijay Kumar  - To check if outstanding frankfurt branch commit pending.  No blueprint/bootstrap revision required; Frankfurt doc to be updated for version update.

Other DCAE components? NO

3
Huawei support for RESTConf
4
Review MUST-HAVE/Committed  REQ status/updates

REQ-374 ONAP shall use STDOUT for logs collection (PTL)  

- To be verified
  • write both into log file/stdout.
  •  Vijay Kumar  - Identify list of impacted component 

REQ-366 Containers must crash properly when a failure occurs (MUST-HAVE)

REQ-365 Containers must have no more than one main process (MUST-HAVE)

  • Cloudify - need exception. 
  • Other DCAE components complaint?

Guilin Release Requirements

Requirements from OOM team to be discussed with team

  • AAF integration must be configurable

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

 - No change for Guilin release

5
REQ-379 (ONAP projects must use only approved and verified base images for their containers)

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Database%2C+Java%2C+Python%2C+Docker%2C+Kubernetes%2C+and+Image+Versions

java is based on debian, for python it is based on alpine
Pending TSC approval for java

Docker files are here:
java: https://git.onap.org/integration/docker/onap-java11/tree/
python: https://git.onap.org/integration/docker/onap-python/tree/
and images are built though jjb

there are available on the nexus
https://nexus3.onap.org/#browse/search=keyword%3Donap%2Fintegration-java:c60bc6b9612f47d368c19be6ea730120
https://nexus3.onap.org/#browse/search=keyword%3Donap%2Fintegration-java:22b3686a9064fa3d02b9686c538dc15d


Releates to REQ-351 (java upgrade)


Boostrap/Cloudify Guilin new container released update

Deferred to next week

https://gerrit.onap.org/r/c/oom/+/109470


  • 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 (DCAEGEN2-2144)
  • Plugin/type file import (DCAEGEN2-1789) 
7
VES7.2 stddefined mapping to legacy

Hillis, Marge (Nokia - US) <marge.hillis@nokia.com>

@Marge Hillis 

Review proposal for mapping 3GPP fault/heartbeat

/notify etc

/notify 

 3GPP-Standard VES Mapping for fault, fileReady and heartbeat v1.xlsx

Comments

  • Add JSON notation path for 3gpp mapped fmapping fields 
  • Fault : alarmCondition mapping TBD based on analytics/correlation services 
  • Fault : FirstOccurrence not maintained in 3GPP; will have current timestamp when VES event was sent (correlation/analytics MS are expected to use eventId/Firstoccurrent from original/first event).
  • No measurement domain under 3GPP; will use bulkPM flow (revised 3gpp schema)
  • ThresholdInfoFault - TCA equivalent of VES mapping to measurement to be defined. This is not currently in ORAN spec; @Marge Hills  will followup.


8

PMSH Enhancement (DCAEGEN2-2345/DCAEGEN2-2344)

Deferred to next week

 - Review new enhancement proposed 





Backlog from prev meeting  - will be discussed as time permits
9
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 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAF-1156

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

07/15 - CertService Client (configurable cert format). OOM configuration change pending (to be confirmed with David/Catherine). damian.nowak - Notify TSC on meeting tomorrow or email.

10
DCAE Outstanding Jira & MED priority bugs (Guilin)

DCAEGEN2-2308 PM-Mapper: Wrong 3GPP rel-16 schema format supported (28.550 instead of 28.532)

From prev meeting

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 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2136
 - 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 (Bugs)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryfilter=12333
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

11
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 - DCAEGEN2-2328

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


...