CM Handle Connectivity Freshness/Staleness

Related Jira(s):

CPS-1415 - Getting issue details... STATUS

Description

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

What might trigger a cmhandle to go to STALE?

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

Scope

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

Changes to DMI Registry Model

DMI-Registry model needs to be updated to include trustLevel enum(NONE, COMPLETE):

state : {
    cmhandleState   : CmHandleState,
    trustLevel      : ENUM (NONE, COMPLETE)
    lockReason      : LockReason,
    dataSyncEnabled : boolean,
    dataSyncState   : DataStoreSyncState
}

Triggers of CMHandle trust level change

DMI Availability

Trust level defined by NCMP's communication with a DMI Plugin.

10 minute limit should be configurable with 10 as default.

Last Data Update

Trust Level defined by NCMP's interaction with a CM Handle.

10 minute limit should be configurable with 10 as default.

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.

Schema Model Mismatch

Occurs when data change has been called for a CMHandle and the data change does not fit the defined schema for that CMHandle Anchor.

If this error occurs Trust Level is set to NONE.