You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Create 'bulk' version for org.onap.cps.ncmp.rest.controller.NetworkCmProxyController#getResourceDataForCmHandle to support multiple cm-handles (~ multiple anchors in in CPS-Core)

References

CPS-1515 - Spike: Support multiple CM-Handles for NCMP Get Operation

Assumptions<optional>

<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>

#

Assumption

Notes

1

"fields" and "scope" are proprietary options or not in the scope of this analysis.


2



Issues & Decisions

#

Issue

Notes 

Decision

1Which operation(s) need support for multiple cm handles?
  1. Get
  2. Create
  3. Update (Put)
  4. Patch
  5. 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 ?

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)


5keep 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

    1. support in ONAP DMI-plugin


7

How we are supporting multiple anchors into CPS-Core ?

    1. Java Interface (depend on 2.1) or,
    2. REST Interface


8

Response always Async ie. topic is compulsory ?

    1. Reuse existing topic


9Should NCMP Amalgamate Async responses from DMI-Plugin before forwarding ?step 6 in flow diagram
10Overlap 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>

Implementation

Bulk Request Message Flow

Cm Handle Batch Interface Design

Message Flow details

Short description

Message Details

Notes

Bulk Get Request

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

Define new get operation "getResourceDataForCmHandles" into ncmp.yml

Ack Client Request
Response 200 
{"requestId":"123"}

DMI Bulk Request
url tbd 
body:
tbd

Ack Client Request
Response 202

Kafka Messages from DMI to NCMP
Topic: ncmp-async-m2m 
Message Details TBD

Kafka Message(s) from NCMP to Client 


Topic: <client topic> 
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>

Note : Overlap with Deutsche Telecom (check with Lee Anjella Macabuhay there is no overlap)

  • No labels