Versions Compared

Old Version 2

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

compared with

New Version Current

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minutes update

...

All attendees must set their Zoom name in First-name FAMILY-NAME (company) format
WAITING ROOM ENABLED by default; HOST/CO-HOST will allow attendees following naming convention.

Recording:

TBDNot available

Attendees:

Host: Vijay Venkatesh Kumar  (AT&T)

Image Added


Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST


  •  Review Open action-items


Project Status & General updates (Honolulu)

Vijay Venkatesh Kumar

Honolulu Release Status

Honolulu Reference  (Important Links)

Honolulu Release Key Updates

  • Release notes updates for new feature add-on/reference - DONE
  • Reference appropriate jira# and revise component version (pending RC1) - DONE
  • OOM submissions for Istanbul must hashtag set to "istanbul"
  • Istanbul cadence (draft) - Release Planning: Istanbul
  • Honolulu Maintenance release
    • Dashboard - 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyDCAEGEN2-2751




Review H release artifact changes

Vijay Venkatesh Kumar

See link below (Honolulu artifact tracker)

https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html#deliverables



VESCollector refactoringDamian Nowak

Discuss open items/questions from last presentation

-----

VES Collector Publish synchronization - 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-1483

  • Switch Cambria to DCAE-SDK/DMAAP-Client
  • Switch to synchronous mode
  • VES Spec updates (response code)


Comments:

  • Specify versions for SDK ( → we need DMaaP Client from 1.8.x line, e.g. 1.8.2)
  • Processing time/delay with SDK/DMaaP-Client  (~5 ms with very small load); need more load test to be performed
  • EventBatch: adapt synchronous VES to push a single event batch as an array of VES events to DMaaP
  • Check dual publish from VESCollector is required - Vijay Venkatesh Kumar
    • 05/04/21 - Dual publish feature not required to be retained
  • VES Spec updates to discuss response code - Damian Nowak
    • Vijay Venkatesh Kumar to verify, if any new DMaaP-CLient result codes need to be transferred to the xNF (VES Client).
    • 05/04/21 - See image above on RC updates; To be followed with VES team on new VES version required

05/05/21

  • Backward compatibility within VES Collector through config (for RC mapping)
  • VES version spec to worked in-parallel but not mandatory for new VES collector updates planned. The impact on VES spec can be limited by VESCollector implementation with backward compatibility support. 

VES Spec changes

  • Response code (success) from 202 to 200
  • New Error code - 503/413/429
  • To be discussed with Trevor and broader VES team and decide on timing/version for new VES spec release -  Damian Nowak




 DCAEGEN2-2630 - DCAE Helm Transformation (Phase 2)  / REQ-685

Jack Lucas

Vijay Venkatesh Kumar

Review EPIC/stories & discuss openitems/issues

  • Review stories and address questions any
  • Discuss commitments/progress for I release




Outstanding issues

Vijay Venkatesh Kumar



Configuration Standardization 

Damian Nowak

Update on current work 



VES Collector 

Damian Nowak

Update on current work












Topics/Demos' for future meetings

<Topics can be added below by presenters as they are ready>

05/12 - Nokia team to present POC on config mgmt through SDK

Honolulu Artifacts Tracker

...