Versions Compared

Old Version 14

changes.mady.by.user Arpit Singh

Saved on

compared with

New Version 15

changes.mady.by.user Arpit Singh

Saved on

Key

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

...

Decisions Table

DateDecisionAdditional Notes

 

  • Initial proposal to be prepared.
  • To start work on design of Delta Feature.
  • In first phase work on delta feature for one data space.
    Option to expand the feature to multiple dataspaces yet to be explored.

 

  • Presented the Delta Feature proposal in ONAP community meeting.
  • Decision to work on two Delta APIs was made:
    • first API to generate Delta between 2 anchors.
    • second API to generate delta between an anchor and a JSON payload.
  • The delta feature to be limited to one dataspace for now.
  • Delta generated will not be persisted. 
Configuration Persistence Service Montreal Meeting Notes & Recordings

Introduction

The CPS Delta feature is proposed as a new feature to the existing functionalities of CPS. The main idea behind it being is to have the ability to find the delta between two configurations stored in CPS DB.

...

  • Can the functionality be expanded to anchors within different dataspaces?

Final Decisions

Delta feature for CPS will have 2 APIs:

  • First API to generate Delta between 2 anchors. Detailed documentation for first API can be found here.
  • Second API to generate delta between an anchor and a JSON payload. Detailed documentation for second API can be found here.
  • To work on a notification service to publish the delta generated as Kafka events.
  • Delta generated will not be persisted.
  • Delta feature will be limited to one dataspace.