...
| # | Interface | Requirement | Additional Information | Sign-Off | |||
|---|---|---|---|---|---|---|---|
| 1 | CPS-E-08.e | NCMP is to merge CM Notification Subscriptions Create request for the same CM Handle & XPath(s)create request and forward those to DMI plugin. (Interface to be added). |
| kieran mccarthy | |||
| 2 | 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). |
| ||||
| 3 | CPS-E-08.e | Amalgamation per DMI: all subscription updates originating from aA single client subscription request should | be sent to a single DMI in one request (message)result into a maximum of one request per DMI. Of course there can be several | messagemessages if more than 1 DMI is involved. | The need for amalgamation / granularity of message might need to be discussed pending the required characteristics (issue #8). If a single subscriptions can contain all possible cm-handles with many cps-paths it then becomes feasible all CM-Handles refuse all paths or a specific path... Will all that info fit in a single response message. Is that the right thing to do?!!! |
| |
| 4 | 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. | Same schema for all notifications. Subsequent notifications contains the state of all cmhandles involved in the subscription. |
| |||
| 5 | 4CPS-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 |
| 5|||
| 6 | CPS-E-08.e | backward
| |||||
| 7 | Order of the create/delete subscription needs to be discussed . TBD. |
Error Handling
| Error Scenario | Expected behavior | Sign-off | |
|---|---|---|---|
| 1 | DMI Down | rejected | |
| 2 | DMI Not responding withing 30 sec | pending | |
| 3 | create for non-existing cm handle id | rejected | |
| 4 | delete for non-existing cm handle id | (silently?) ignore | |
| 5 | any operation on non-existing xpath | ignore? (no or minimal validation, see issue #5) | |
| 6 | delete for non existing name/client-id | TBD, should be handle in 'basic' solution | |
| 7 | delete for no existing cm-handle id | ignore? (no or minimal validation, see issue #5) | |
| 8 | 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 tabel below |
...