...
# | Issue | Notes | Decisions |
|---|---|---|---|
| 1 | Delete the subscription from the database? | We plan to do it when we receive response from the DMI plugins and the underlying subscriptions from the devices are deleted. | |
| 2 | What do we need to send to the DMI Plugin so that they are able to decide that how to delete the ongoing subscription. | We are sending cmHandle information and predicates information ( datastore , xpaths and cmHandle ) and private cmHandle properties. | |
| 3 | Who should be able to retry and make sure the subscriptions are deleted from the respective DMIs managing the devices. | kieran mccarthy The agenda for the next meeting. We can decide then. More on the "DELETING" stage ( if we want to have it ) | kieran mccarthy As discussed on , The DME should be able to maintain Subscription State and make decision when to retry based on the response outcome we provide to it for create and/or delete use cases. |
| 4 | DME to NCMP Event to have targets and datastore-xpath-filter information for the subscription delete use case ? | DME to only send the subscription id inorder to delete the request. NCMP will figure out the details corresponding to the provided subscription id and figure out what to request to DMI Plugin for deletion. | kieran mccarthy As per the discussion today we agreed to use targets , datastore-xpath-filters and datastores for the subscription delete use case. Revised approach is mentioned in the Notes section. |
| 5 | Do we send additional properties from NCMP to DMI | We are sending additional/private properties as of now. | |
| 6 | Can the DMI Plugin REJECT the Cm Subscription Delete Request ? | kieran mccarthy Wanted to check if this is the VALID use case we have ? | Yes it could be possible. If the underlying data producer (node/ems) is disconnected for some reason then the request cannot be fulfilled. The client should be notified of the failure.
|
Algorithm for CM Subscription Delete
...