Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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. 

Requirements

Functional

#InterfaceRequirementAdditional InformationSign-off
1CPS-NCMP-E-05The 'trustlevel'
can
is visible
)
on
the
all REST methods
as
that currently include the 'cm handle state'
Should only include
existing
endpoint 
endpoints 

 

2CPS-NCMP-E-05CM Handles can be queried (filter condition) on  'trustlevel'  

using a new 'trustLevel' condition (cannot use cpsPath condition)

Existing CM Handle query param should also include TRSUTLEVEL condition

 

3CPS-NCMP-
i
I-01

During registration, DMI plugin can report initial trustlevel.

If the state is not 'complete', it should be considered as 'Trustlevel change' (See req 5)

Initial trust level will be backward

compactable

compatible if not set, we assume trustlevel is 'complete'

For a new cm-handle where the trustlevel is 'complete' this is NOT considered a chance and no notifications should be sent

  

4CPS-NCMP-E-05Once DMI (plugin) is detected to be down the trust-level for all affected CM Handles should be set to be 'NONE'

It might not need to be persisted. 

. This wil also lead to many notifcations as per req. #5

this might lead to a high level (20K) of notifications 

(need to discuss capabilities)

Reporting should be a separate requirement

 

5CPS-NCMP-E-05.e

NCMP notification shall be sent

IF

when the trustlevel changes

i.e 20k notification

Notification be sent externally based on Kafka 

many small or bulk: Agreed Many

small

notifications, one for each cm-handle

  

6
EventsOnce DMI (plugin) is detected to be down the trust-level for all affected CM Handles send notification if NCMP is 'DOWN'7

 

CPS-NCMP-I-01.e

It shall be possible to report any trustlevel of one CM Handle

DMI plugin can report the current trustLevel of a single cm handle id

i.e. the DMI can tell NCMP the trustLevel is 'NONE' when a  node heartbeat failure is detected and 'COMPLETE' once it is restored.
Again this should lead to notifications on the external interface as per req #5 

 

Error Handling

#Error ScenarioExpected behaviorSign-off
1NCMP restart (all instances)

To be discussed, not sure if it can/should be handled

TrustLevels should be 'NONE' and need to be restored using an audit-request (not in scope)


...