...
| # | Interface | Requirement | Additional Information | Sign-off |
|---|---|---|---|---|
| 1 | CPS-NCMP-E-05 | The 'trustlevel' can is visible) on the methods as currently the 'cm handle state' | Should only include existing endpoint |
|
| 2 | CPS-NCMP-E-05 | CM 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 |
|
| 3 | CPS-NCMP-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 if not set, we assume is complete |
|
| 4 | CPS-NCMP-E-05 | Once 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. Reporting should be a separate reqrequirement |
|
| 5 | CPS-NCMP-E-05.e | NCMP notification shall be sent IF the trustlevel changes | i.e 20k notification Should notification Notification be sent internally/ externally based on Kafka many small or bulk: Agreed Many small |
|
| 6 | Events | Once 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 |
|
...