Table of Contents |
---|
Related Jira(s)
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Assumptions
Assumption | Notes | |
---|---|---|
1 | When a DMI restarts all cm-handles related to that DMI will consider to have trust-level COMPLETE | Temporary assumption until the 'Audit' function has been implemented |
...
# | 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 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- | E-05Once a CM Handle is registered the trust-level for that CM Handle should be reported to be 'COMPLETE' | 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 | reportedset to be 'NONE' | It might not need to be persisted. Reporting should be a separate req |
| |
5 | CPS-NCMP-E-05. | ..5e | NCMP notification shall be sent IF the trustlevel changes | i.e 20k notification Should 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 |
|
Error Handling
# | Error Scenario | Expected behavior |
---|---|---|
1 | NCMP 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) |
...
Interface | Name | Trigger | Description | Type | Endpoint or Topic | Schema |
---|---|---|---|---|---|---|
1 | HealthCheck | 30 second interval (configurable) | NCMP is to perform a health check against each of the DMI Plugins | REST | http://<dmiPluginServiceName>/manage/health This endpoint will be the standard heath check endpoint provided by spring boot actuator. We don't store it anywhere. We just document it for now. | |
2 | CMHandle trust level change | A CMHandle managed by DMI Plugin's trust level has changed | data contains {trustLevel: ENUM} event id is cmhandle id | Kafka | kafka topic: dmi-device-heartbeat | <cloudEvents-header> id : <cmhandleId> type : org.onap.cm.events.trustlevel-notification data : { |
3 | TrustLevel Request | Client Request | TrustLevel is to be returned based on the values in above Maps | REST |
| { |
Managing TrustLevels
...