-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
NCMP to Client
-
- Create Response Event for Client based on data structure updated during DMI to NCMP
- #4 Schema (https://wiki.onap.org/pages/viewpage.action?pageId=190218335)
- * Change in distributed data structure is 'watched' to trigger sending response to the client
- Send response to Client
- Response should include accepted/rejected/pending (for all applicable)
- Within the configurable time (30 seconds)
- First is message sent
- Atleast one message per subscription ID
- Clear the data structure holding all 'new' subscriptions
- for accepted/rejected = to be removed
- for pending = to be kept (for now- see open question)
- Create Response Event for Client based on data structure updated during DMI to NCMP
Open Question:
- How long should we keep 'PENDING' subscriptions?
- What happens if we "remove" a "PENDING" subscription and DMI responds back with ACCEPTED/REJECTED
A/C
- Proposal for implementation agreed with team
- Respond successfully to client (positive scenarios)
- Data structure correctly updated
- removed all SENT accepted and rejected
- pending still exists
- Initial demo to team/PO
- Demo to stakeholders