-
Story
-
Resolution: Done
-
Medium
-
None
What
- Separate model-sync from Registration. ie. just persist the cm handle data with state 'ADVISED'
This was accidently done before and the reverted here: https://gerrit.onap.org/r/c/cps/+/129102/6..9 so this link might help you where it needs to be added - Add logic to persist cm-handle with 'ADVISED' state once registration is successful
- watch out for method names stil assuming sync will happen immediately
- e.g. org.onap.cps.ncmp.api.NetworkCmProxyDataService#updateDmiRegistrationAndSyncModule
- CSIT test will be impacted as sync does NOT happen immediately anymore
- remove assert on module info (can be re-added on sync-on-command)
A/C
- Demo
- after registration all CmHandles are in state 'ADVISED' (need to delay Watchdog possibly)
- after some time CmHandles states should move to 'READY'
- NFP-Operational should not be done as part of registration, but during watchdog process.
Open Issues
- Does updating cm-handles affect the cm-handle state.
Not for now. maybe later we have 'upgrade' or similar - Is the state always going to be persisted as 'ADVISED'?
Yes for registration it always will be "ADVISED" for newly created cm-handles
Out of Scope