...
Interface | Requirement | Additional Information | Signoff | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | CPS-E-08e | NCMP will forward 'CM Notifications Subscription' LCM Create events to the appropriate DMI Plugins responsible for the CM Handles (ids) defined in the LCM Events. The message sent to DMI should include the private properties for each CM-Handle |
| |||||||||||
| 2 | CPS-E-08e | NCMP will forward 'CM Notifications Subscription' LCM Delete events to the appropriate DMI Plugins responsible for the CM Handles is defined in the LCM Events. | 'Basic' delete we be implemented followed by a more advanced delete operation depending on Merge functionality:
| A delete should only be forwarded if there is no other subscription for cmhandle datastore path. |
| |||||||||
| 3 | CPS-E-08e | NCMP responds using Kafka message(s) with the result of the LCM operation These messages wil will use agreed status fields:
| Action: Define error details later | |||||||||||
| 4 | CPS-E-08e | All events should use Cloud Events format | https://cloudevents.io/ | |||||||||||
| 5 | CPS-E-08e | Messages should be processed in the order they are created (received) | It will depend on DMIs responding within 30s. Subscription-id should be used as Kafka 'key' to ensure this. | |||||||||||
| 6 | CPS-E-08.e | NCMP is to merge CM Notification Subscriptions create request and forward those to DMI plugin. (Interface to be added). |
| |||||||||||
| 7 | CPS-E-08.e | Last lights out: upon subscription Delete request only when there is no more subscription for a cm-handle & xpath & datastore combination a subscription-delete request will be sent to the relevant DMI(s). | ||||||||||||
| 8 | CPS-E-08.e | A single client subscription request should result into a maximum of one request per DMI. Of course there can be several messages if more than 1 DMI is involved. | ||||||||||||
| 9 | CPS-E-08.e | Amalgamate response should include rejected/accepted/pending DMI responses received within 30 seconds. A client shall be notified of available DMI subscription information after 30 seconds. Subsequent DMI subscription updates shall be notified to clients as they become available. |
| |||||||||||
| 10 | CPS-NCMP-I-01 | CM Handle deletion should NOT update subscription details. | Do NOT delete dmi-subscription entry until owning subscription is deleted, see issue #4 below | |||||||||||
| 11 | CPS-E-08.e |
...
Error Scenario | Expected behavior | Sign-off | ||||
|---|---|---|---|---|---|---|
| 1 | Non responding DMIs (configurable timeout) | An error message listing the 'pending' CM Handle IDs and statusMessage as "partially applied subscription" with relevant statuscode.. statusMessage/statusCode to be agreed. | ||||
| 2 | Non Existing or non-valid CM Handle Ids | An error message listing the 'rejected' CM Handle IDs IDs. | ||||
| 3 | DMI Plugin without CM Event subscription support | An error message listing the 'rejected' CM Handle IDs | ||||
| 4 | Late Response (after timeout defined in #1) from DMI | A message contain the status message as "fully applied subscription" with relevant status code.list of outcomes (complete status on how many cmhandles are pending/rejected/accepted) from client subscription is returned in response. statusMessage/statusCode to be agreed. |
| |||
| 5 | Create for existing subscription id | The whole subscription will be rejected. statusMessage/statusCode to be agreed. |
| |||
| 6 | delete Delete for non-existing cm handle subscription id | (silently?) ignore | 7 | delete for non-existing subscription id | 8The whole delete subscription will be rejected. statusMessage/statusCode to be agreed. |
|
| 7 | Error upon error | An error scenario on a second subscription for the same cm-handle/xpath as a previous subscription which did not complete successfully (yet) to be discussed, see Error Upon Error Combinations |
...
Parameter | Expectation | Notes | Sign-off | |
|---|---|---|---|---|
| 1 | Frequency of LCM Subscription Events | No high volume of such events is expected For testing purposed purpose 1 LCM event per minute would suffice. | kieran mccarthy confirmed |
|
| 2 | Number of Subscriptions | Max: 200 | kieran mccarthy confirmed | |
| 3 | CM Handles per Subscription | Avg: 200 Max: 500 (document only) | kieran mccarthy to confirm | |
| 4 | Xpaths per Cm Handle | Avg: 10 | ||
| 5 | Status update processing time | (Order of 30) seconds (NCMP side) |
...