References:
- CPS-1119Getting issue details... STATUS
Overview
This user story relates to CPS-1119 Define the Initial Data Sync State on each cmhandle registration request
Current Process:
- Cm Handle Is Registered in Advised State
- Watchdog Process Wakes Up, set state to READY
- The dataSyncState is set to UNSYCHRONIZED as part of the following user commit (https://gerrit.onap.org/r/c/cps/+/129720)
New Process:
- Cm Handle Is Registered in Advised State,
- Set and persist dataSyncEnabled flag
- Watchdog Process Wakes Up, set state to READY
- Based on the dataSyncEnabled flag, the default state is set to UNSYCHRONIZED or NONE_REQUESTED
- The data sync watchdog should pick up any cm handles found in the UNSYCHRONIZED state.
Issues/Decisions
# | Questions/Open Issues | Notes | Decision/Answer |
---|---|---|---|
1 | How is dataSyncEnabled set? | Presumably during the registration process (ie part of POST body), optionsÂ
| |
2 | What is the default state (if nor provide assuming new parameter is optional) | Presumably UNSYNCHRONIZED if data sync enabled flag is true, and NONE_REQUESTED if data sync enabled flag is false. | |
3 | Does update functionality as part of cm handle registration have any effect on the data sync state and in turn the dataSyncEnabled flag? | Consider
|