Related Jira(s):
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
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
Trust level defined by NCMP's communication with a DMI Plugin. 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.
Hazelcast Map?
...
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
Open Question: External Notifications NCMP is subscribed to should effect this?
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 (passthrough only).
If this error occurs Trust Level is set to NONE.
| Issue | Description | ||
|---|---|---|---|
| |||
|
| ||
Schema Model Mismatch
OUT OF SCOPE
Occurs when data change has been called for a CMHandle and the data change does not fit the defined schema for that CMHandle Anchor (passthrough only).
If this error occurs Trust Level is set to NONE.
Open Questions
| Issue | Description | Answer |
|---|---|---|
| Storing Trust Level | Do we have to store the trust level or can it be calculated when asked? | Storing in a Hazelcast Map |
| Interface | What is the interface for getting the trust level going to be | New endpoint |