Versions Compared

Old Version 27

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version 28

changes.mady.by.user Sourabh Sourabh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Flow Step

Short description

Message Details

Notes

1

Bulk Get Request


Code Block
title/v1/batch/data/ds/{datastore-name}
collapsetrue
body:
{"Cnhandles":["ch-1",...,"ch-n"]


Define new get operation "getResourceDataForCmHandles" into ncmp.yml

2Ack Client Request


Code Block
titleResponse 200
collapsetrue
{"requestId":"123"}



3DMI Bulk Request


Code Block
titleurl tbd
collapsetrue
body:
tbd


The DMI PLugin should be told (included in request) the client topic so that NCMP does not have to 'remember' to relation between request id and client topic!


Existing DMI endpoints are : 

/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-operational:
/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-running

 ...&topic=topicParamInQuery


CPS Proposed :

/v1/ch/batch/data/ds/ncmp-datastore:passthrough-operational:
/v1/ch/batch/data/ds/ncmp-datastore:passthrough-running

 ...&topic=topicParamInQuery

Requestid into body

4Ack Client Request


Code Block
titleResponse 202
collapsetrue


5Kafka Messages from DMI to NCMP

 Code Block
titleTopic: ncmp-async-m2m
collapsetrue
Message Details TBD


6Kafka Message(s) from NCMP to Client 



 Code Block
titleTopic: <client topic>
collapsetrue
Message Details TBD


7Alternative for 4/5 → Non responding DMI. NCMP will have to create error message detailing cm-handles
See decision # 8
...