Versions Compared

Old Version 2

changes.mady.by.user Dylan Byrne

Saved on

compared with

New Version 3

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-877

Overview

This user story is related to  CPS-875 CM Handle State: Watchdog-process that syncs 'ADVISED' CM Handles.

Recap of watchdog process:

  1. Wake up on a specified schedule
  2. Identify node with state ‘ADVISED’
  3. Lock database, update timestamp, unlock the database
  4. Model sync
  5. Update state of the node to ‘READY’

As part of this story, only CM-Handles with a state of ready should be returned as part of queries or operations in regard to CM-Handles.

Issues and decisions

#Questions/Open IssuesNotesDecision/Answer
1Should
states
state details be part of Response - get CM Handles RequestDon't think so. Check with Stakeholder
2Should
the states last updated time also be part of the response?3Does this include
filter be applied to the API which queries cm handles based on public properties
4
Check with Stakeholder
3Are all data API's which interact with CM-Handles affected by this - such as GET/POST/PATCH/DELETE operations 
5

CPS-NCMP ↔ DMI-Plugin Interface Details Jakarta-R10
CPS-E-05 list all methods and check/decide in this study

Also consider CPS-NCMP-I-01


4What is the default value of a state if it is not specified when registering a cm-handle.consider anything as NOT equals to 'READY' as NOT ready 'ADVISED'


List of API's affectedand possible impact.