...
# | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Which operation(s) need support for multiple cm handles? |
if many what is the priority? | Get (read) |
| 2 | Which datasources should be supported? | Do we need to support passthrough-only no-cached() data only ? | passthrough.* Not implemented for other datastores with respponse code |
| 3 | URL pattern for NCMP bulk endpoints | 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) | |
| 4 | 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 | |
| 5 | support in ONAP DMI-plugin | ||
| 6 | Response always Async ie. topic is compulsory ? | Assume topic is compulsory (defined in OPenApi) → Response therefore wil be 400 if not supplied | Yes , Not supported for others |
| 7 | Should NCMP Amalgamate Async responses from DMI-Plugin before forwarding ? | step 6 in flow diagram | No |
| 8 | Handle non responding dmi-plugin | No response for 4b then send an error response to the topic given by client | |
| 9 | Overlap with Deutsche Telekom | Sourabh Sourabh discussed Lee Anjella Macabuhay who confirmed there s no overlap | No Overlap |
...