...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Issues and Decisions
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | how fast should CPS (and DB) be able to process max heart beat failures | is 60K really realistic if ENM goes down we should get a notification for each node do we ?! | PoC has shown 60 seconds is reasonable |
| 2 | restart of NCMP | should/can this be handled | |
| 3 |
Description
- Define scenarios which cause a CM Handle to go stale
- Implement changes to support tracking of CM Handle Freshness/Staleness
...
- dmi plugin identifies that the device is no longer contactable
- dmi plugin identifies that an underlying device manager managing the device (node) is out of sync with the device itself.
Requirements
Functional
| # | 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' | can be new or existing (preferred) endpoint | |
| 2 | CPS-NCMP- |
| E-05 | CM Handles can be queried (filter condition) on 'trustlevel' | using a new 'trustLevel' condition (cannot use cpsPath condition) | |
| 3 | CPS-NCMP-E-05 | Once a CM Handle is registered |
| the trust -level for that CM Handle should |
| be reported to be 'COMPLETE' |
| 4 | CPS-NCMP- |
| E- |
| 05 | Once DMI (plugin) is detected to be down the trust-level for all affected CM Handles should be reported to be 'NONE' | It might not need to be persisted.... |
| 5 | CPS-NCMP-I-01 |
REST or ASYNC TBD
| .e | DMI plugin can report the current trustlevel of a single |
| cm handle |
| id |
| ie. the DMI can tell NCMP the trustlevel is 'NONE' when a node heartbeat failure is detected and 'COMPLETE' once it is restored |
Error Handling
| # | Error Scenario | Expected behavior | |
|---|---|---|---|
| 1 | NCMP restart Options: | To be discussed, not suer if it can/should be handled Trustlevels should be 'NONE' and need to be restored using an audit-request (not in scope) | 2 |
Characteristics
| # | Parameter | Expectation | Notes | Sign-off |
|---|---|---|---|---|
| 1 | dmi-down detection speed |
| 30 seconds |
| 2 | maximum number of cm-handles down report by DMI in one request and/or per minute | 30,000 / minute |
| a peak can be processed within 60 seconds | ||||
| 3 | processing of all trustlevel time for DMI-Down and/or peak load by DMI | 1 second |
Out-of-Scope
- This epic will only introduce trustlevels NONE and COMPLETE. PARTIAL and POOR may be added later as below.
- Re-registration ie. resolve resolving trutslevel degradation is not in scope of this epic
- NCMP wil not send notification on trustlevel changes for external consumers
High Level Interactions
| Drawio | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...