...
# | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Which operation(s) need support for multiple cm handles? |
if many what is the priority? | |
| 2 | Do we need to use same xpath (resourceIdentifierInQuery) for all cm handles or different for each cm handle ? | ||
| 3 | Which datasources ? | Do we need to support passthrough-only no-cached() data only ? or, alternatively, support operational/running (cached) data too ? | |
| 4 | Endpoint url patterns? | Existing : /v1/ch/{cm-handle}/data/ds/{datastore-name} CPS Proposed : /v1/batch/data/ds/{datastore-name} ( include cm handles into payload / body and leave datastore into url) | |
| 5 | keep datastore, topic and optional parameters in the URL itself instead into body. | CPS prefers keep interface similar as single cm handle interface (consistency and cost) Existing : ...&topic=topicParamInQuery | |
| 6 | Impacts on DMI Plugin Interfaces
| ||
| 7 | How we are supporting multiple anchors into CPS-Core ?
| ||
| 8 | Response always Async ie. topic is compulsory ?
| ||
| 9 | Should NCMP Amalgamate Async responses from DMI-Plugin before forwarding ? | step 6 in flow diagram | |
| 10 | Overlap with Deutsche Telekom | Sourabh Sourabh discussed Lee Anjella Macabuhay who confirmed there s no overlap | No Overlap |
<Note. use green for closed issues, yellow for important ones if needed>
...
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Message Flow details
...
Short description | Message Details | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Bulk Get Request |
| Define new get operation "getResourceDataForCmHandles" into ncmp.yml | ||||||||
| Ack Client Request |
| 2|||||||||
| DMI Bulk Request |
| |||||||||
| Ack Client Request |
| |||||||||
| Kafka Messages from DMI to NCMP |
| |||||||||
| Kafka Message(s) from NCMP to Client |
| see open issue #9 |
< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>
...