...
# | Issue | Notes | Decisions |
|---|---|---|---|
| 1 | Delete the subscription from the database? |
| |
| 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. |
| |
| 3 | The subscription delete request 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 DMI | Are additional properties needed to delete the subscription |
...
- NCMP receives subscription delete response from DMI Plugins
- NCMP checks the existing create subscription object in db
- If cmhandle is accepted, delete cmhandle is pending
- If cmhandle is rejected, delete cmhandle is rejected with message like "create subscription was rejected originally"
- If cmhandle is pending, delete cmhandle is rejected with message like "create subscription for cmhandle is pending"
- NCMP persists subscription delete in db
- NCMP forwards subscription delete to the pending delete operation cmhandle's dmi plugins.
- NCMP listens for DMI responses and updates subscription delete in db
- If all respond then send NCMP to ClientApp response
- If not all respond then send response after 30 seconds
- Check if subscription create and subscription delete match states for all cmhandles then the subscriptions can be deleted from the db
If Delete is requested again by client apps
Create State Delete State NCMP action 1 Accepted Accepted Nothing 2 Accepted Rejected Delete for that cmhandle once 3 Accepted Pending Delete for that cmhandle once 4 Rejected Rejected Nothing 5 Pending Rejected Nothing See step 5.