...
# | Issue | Notes | Decisions | ||
|---|---|---|---|---|---|
| 1 | Delete the subscription from the database? | When do we actually delete the subscription from CPS DB ? We 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. |
| Only the subscriptionId has to be sent to the DMI plugin | 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 ? | kieran mccarthy As per the discussion today we agreed to use targets , datastore-xpath-filters and datastores for the subscription delete use case. | |||
| 5 | Do we send additional properties from NCMP to DMIAre additional properties needed to delete the subscription | 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 ? |
Algorithm for CM Subscription Delete
...