Related Jira(s):
...
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
...
| Elapsed time since last DMI Plugin lost Device HB | Trust Level |
|---|---|
| Less than 10 minutes | COMPLETE |
| Over 10 minutes | NONE |
Reregistration
This process occurs when the DMI Plugin Availability is down and then comes back up.
NCMP makes a synchronous call to the DMI Plugin (New Audit Endpoint) to trigger a reregistration
DMI Plugin then reregisters its CMHandles with NCMP (new reregistaration Endpoint?)
NCMP then compares the CMHandles which are being reregistered with the CMHandles which already exist.
CMHandles which are in NCMP but not in DMI reregistration request are kept as trust level none
What happens if there is conflict between the old and new properties of a CMHandle, just take the new properties?
New CMHandles could be registered
Hazelcast for Trust Level
Map Trust level for DMI Plugins
Key: Dmi Name, Values: health check url, trust level
Set Trust level for untrustworthy CMHandles
Key: CmHandleId
When checking the trust level for a CMHandle first check the trust level of that CMHandle's DMI Plugin
If None return None
If Complete check trust level for the CMHandle and return that
Last Data Update
OUT OF SCOPE
...