Table of Contents |
---|
...
# | Issue | Notes | Decision |
---|---|---|---|
1 | Do we need to update existing update notification to send delta notification or delta notification along with existing notification. | 29-Sep-2023: We decided to implement delta notification separately without changing the existing update notification. | |
2 | Using Liquibase v. Yang Model for storing new metadata per anchor in CPS Core | Needs discussions with architects | |
3 | generic text field OK for future refinement, maybe consider json? |
Event Schema
For delta notification we can use the existing cps data update event schema (cps-data-update-event-schema.json).
# | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | id | UUID of the event | |||||||||
2 | source | urn:cps:org.onap.cps | |||||||||
3 | schema | urn:cps:org.onap.cps:data-updated-event-schema:v1 | |||||||||
4 | type | org.onap.cps.data-updated-delta-event | |||||||||
5 | content | { "operation": "UPDATE",
} |
...
Additional field will be added to Anchor table to persist delta notification subscription. newly added field details are as below.
Updated Table | Anchor |
new field name | notification |
type | text |
example | true (string). change later. |
Open questions to be discussed:
Is it OK to modify Postgres tables instead of using a yang modelled data approach... (this will require Liquibase steps)
TD : Toine Siebelink need to discuss with Architects and update
Implementation details
- For data nodes update operation, generate delta report by comparing previous and current configuration after successful update.
- Process data update delta event and send notification as described in event schema above.