Versions Compared

Old Version 11

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version 12

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...

#

Assumption

Notes

1

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


2



Issues & Decisions

345

#

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 Propossed 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

<Note. use green for closed issues, yellow for important ones if needed>

...

Gliffy Diagram
macroId5966a68a-1641-430a-8c78-27c938f06e15
displayNameCm Handle Batch Message Flow
nameCm Handle Batch Interface Design
pagePin12

Message Flow details

1

Implement org.onap.cps.ncmp.rest.controller.NetworkCmProxyController#getResourceDataForCmHandles

with params below :

final String datastoreName,
final Collection<String> cmHandles,
final String resourceIdentifier,
final String optionsParamInQuery,
final String topicParamInQuery,
final Boolean includeDescendants

#

Steps

Notes 

Decision

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

Request

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


22



< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>
...