z
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| # | Interface | Requirement | Additional Information | Sign-Off |
|---|---|---|---|---|
| 1 | CPS-E-08.e | NCMP is to merge CM Notification Subscriptions 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 | 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. |
| |
| 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 | 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 |
|
| 6 | CPS-E-08.e |
| ||
| 7 | Order of the create/delete subscription needs to be discussed . TBD. |
...