CM Handle Connectivity Freshness/Staleness

Related Jira(s):

CPS-1415 - Getting issue details... STATUS

Description

Define scenarios which cause a CM Handle to go stale
Implement changes to support tracking of CM Handle Freshness/Staleness

What might trigger a cmhandle to go to STALE?

dmi plugin identifies that the device is no longer contactable
dmi plugin identifies that an underlying device manager managing the device (node) is out of sync with the device itself.

Scope

Currently only supporting NONE and COMPLETE. PARTIAL and POOR may be added later as below.

Changes to DMI Registry Model

We will not be making changes to the DMI Registry Model, Public Properties of the CMHandle will be used where needed.

Triggers of CMHandle trust level change

DMI Availability

Ping every 30 seconds configurable or (every communication with DMI OOS)

Health check endpoint already exists

http://'$1'/manage/health/readiness

Hazelcast Map

When DMI comes back up, DMI does audit and provides list of Trustworthy CM Handles

Audit triggered by NCMP with list of CMHandles IDs and for DMI to reregister HTTP

Deltas: DMI handling, properties; Delete all under a DMI? Performance?

DMI Availability	Trust Level
Available	FULL
Unavailable	NONE

Device Heart Beat

Assumed functionality is that this will be defined by the DMI Plugin as NCMP does not communicate with device directly

Interface in NCMP for DMI Plugin to be able to tell when device HB has been lost?

10 minute limit should be configurable with 10 as default.

Probably event based

Elapsed time since last DMI Plugin lost Device HB	Trust Level
Less than 10 minutes	COMPLETE
Over 10 minutes	NONE

Last Data Update

~~OUT OF SCOPE~~

~~Trust Level defined by Client's use of NCMP endpoints to change data related to a CMHandle (passthrough only).~~

~~10 minute limit should be configurable with 10 as default.~~

~~Stored in public properties~~

~~Elapsed time since last data change for CM Handle~~	~~Trust Level~~
~~Less than 10 minutes~~	~~COMPLETE~~
~~Over 10 minutes~~	~~NONE~~

~~Open Question: External Notifications NCMP is subscribed to should effect this?~~

~~Issue~~

~~Description~~

~~Answer~~

~~CM Handle sync~~

~~Assumption is that at CMHandle registration the CMHandle is originally persisted as NONE trustLevel~~

~~As CMHandle moves to READY, NONE moves to COMPLETE, Else stays as NONE~~

~~The DataSync does not effect this as is related to cache.~~

~~What Data?~~

~~What about changes to the CMHandle Properties etc?~~

~~Last Data Update~~

~~External Notifications NCMP is subscribed to should effect this?~~

Schema Model Mismatch