Page History

...

#	Assumption	Notes
1	"fields" and "scope" are proprietary options or not in the scope of this analysis.
2	same xpath (resourceIdentifierInQuery) for all cm handles or different for each cm handle

Issues & Decisions

#	Issue	Notes	Decision
1	Which operation(s) need support for multiple cm handles?	Get Create Update (Put) Patch Delete 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 should be supported?	Do we need to support passthrough-only no-cached() data only ? or, alternatively(maybe just start with that, support operational/running (cached) data too ?cached data bulk request later)
3	URL pattern for NCMP bulk endpoints	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)
54	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	6	Impacts on DMI Plugin Interfaces support in ONAP DMI-plugin	7	How we are supporting multiple anchors into CPS-Core ? Java Interface (depend on 2.1) or, REST Interface
6	8	Response always Async ie. topic is compulsory ? Reuse existing topic	Assume topic is compulsory (defined in OPenApi) → Response therefore wil be 400 if not supplied
79	Should NCMP Amalgamate Async responses from DMI-Plugin before forwarding ?	step 6 in flow diagram
108	Overlap with Deutsche Telekom	Sourabh Sourabh discussed Lee Anjella Macabuhay who confirmed there s no overlap	No Overlap

...

Short description

Message Details

Notes

Bulk Get Request

Code Block

title	/v1/batch/data/ds/{datastore-name}
collapse	true

body:
{"Cnhandles":["ch-1",...,"ch-n"]

Define new get operation "getResourceDataForCmHandles" into ncmp.yml

Ack Client Request

Code Block

title	Response 200
collapse	true

{"requestId":"123"}

DMI Bulk Request

Code Block

title	url tbd
collapse	true

body:
tbd

Ack Client Request

Code Block

title	Response 202
collapse	true

Kafka Messages from DMI to NCMP

Code Block

title	Topic: ncmp-async-m2m
collapse	true

Message Details TBD

Kafka Message(s) from NCMP to Client

Code Block

title	Topic: <client topic>
collapse	true

Message Details TBD

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>

...