You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

References:

CPS-1119 - Getting issue details... STATUS


Overview

This user story relates to CPS-1119 Define the Initial Data Sync State on each cmhandle registration request

Current Process:

  1. Cm Handle Is Registered in Advised State
  2. Watchdog Process Wakes Up, set state to READY
  3. The data sync state is set to UNSYCHRONIZED as part of the following user commit (https://gerrit.onap.org/r/c/cps/+/129720)

New Process:

  1. Cm Handle Is Registered in Advised State
  2. Watchdog Process Wakes Up, set state to READY
  3. Based on the data sync enabled flag, the default state is set to UNSYCHRONIZED or NONE_REQUESTED
  4. The data sync watchdog should pick up any cm handles found in the UNSYCHRONIZED state.

Issues/Decisions

#Questions/Open IssuesNotesDecision/Answer
1How is data sync enabled set?Presumably during the registration process
2What is the default statePresumably UNSYNCHRONIZED if data sync enabled flag is true, and NONE_REQUESTED if data sync enabled flag is false.
3Is Data Sync State part of the registration request POST api Body?

4Does update functionality as part of cm handle registration have any effect on the data sync state and in turn the dtata sync enabled flag?


  • No labels