Versions Compared

Key

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

Table of Contents

Related Jira(s)

Jira Legacy
serverONAP System Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176
keyCPS-1415

Jira Legacy
serverONAP System Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176
keyCPS-1638

Assumptions


AssumptionNotes 
1When a DMI restarts all cm-handles related to that DMI will consider to have trust-level COMPLETETemporary assumption until the 'Audit' function has been implemented

...

E-05 reported ..5
#InterfaceRequirementAdditional InformationSign-off
1CPS-NCMP-E-05The '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 

 

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-Once 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

  

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. 

Reporting should be a separate req

 

5CPS-NCMP-E-05.e

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

  

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


 

7CPS-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 ScenarioExpected behavior
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)

...

InterfaceNameTriggerDescriptionTypeEndpoint or TopicSchema
1HealthCheck30 second interval (configurable)NCMP is to perform a health check against each of the DMI PluginsREST

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.


2CMHandle trust level changeA 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 : {
      trustlevel : "COMPLETE"
}

3TrustLevel RequestClient RequestTrustLevel is to be returned based on the values in above MapsREST
  1. http://<host>:<port>/ncmp/v1/ch/id-searches
  2. http://<host>:<port>/v1/ch/searches 

{
  "cmHandleQueryParameters": [
    {
        "conditionName""cmHandleWithTrustLevel",
        "conditionParameters": [ {"trustLevel""COMPLETE"} ]
    }
  ]
}

Managing TrustLevels

...