Versions Compared

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:
["cm-1",...,"cm-n"]


Code Block
titleExample CURL cmd : curl --location --request POST
collapsetrue
'http://localhost:8080/ncmp/v1/batch/data/ds/ncmp-datastore:passthrough-running?resourceIdentifier=parent/child%26options=(a=1,b=2)&topic=my-topic-name&options=(fields=schemas/schema)' \
--header 'Authorization: Basic Y3BzdXNlcjpjcHNyMGNrcyE=' \
--header 'Content-Type: application/json' \
--data '[ "40137a9771f84459affa795fa1d633ab", "f5a92ec7a7db4d6fbb0e0ce2803a86cc" ]'


Define new get operation "getResourceDataForCmHandles" into ncmp.yml

2Ack Client Request


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



3DMI Bulk Request


Code Block
title/v1/ch/batch/data/ds/{datastore-name}&topic=topicParamInQuery
collapsetrue
body: {"Cmhandles":["cm-1",...,"cm-n"],"requestId":123}


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!



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 
Table


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 and 9
8

Response message structure ? (Flow no. 5)

Non responding DMI-plugin 


Code Block
titleNon responding DMI-plugin 
collapsetrue
{
  "timestamp":"2023-03-01T23:00:00.345-0400", 
  "requestId":123,
  "error": "DMI Service Unavailable, {service-name}",
  "Cmhandles":["cm-1",...,"cm-n"]
  }



9

Response message structure ? (Flow no. 5)

Non existing cm handles


Code Block
titleNon existing cm handles
collapsetrue
{
	"timestamp":"2023-03-01T23:00:00.345-0400",
    "requestId":123,
	"error":"Cm-Handle not found",
	"Cmhandles":["cm-1",...,"cm-n"]
}



10Non Ready cm handles


Code Block
titleNon READY existing cm handles
collapsetrue
{
	"timestamp":"2023-03-01T23:00:00.345-0400",
    "requestId":123,
	"error":"Cm-Handle not in READY state.",
	"Cmhandles":["cm-1",...,"cm-n"]
}



11URL  pattern for DMI-Plugin bulk endpoints

Existing DMI endpoints are : 

/v1/ch/{cmHandle}/data/ds/{datastore-name}


datastore-name:

  1. ncmp-datastore:passthrough-operational
  2. ncmp-datastore:passthrough-running

 ...&topic=topicParamInQuery


CPS Proposed :

/v1/ch/batch/data/ds/{datastore-name}

 ...&topic=topicParamInQuery

cm handle ids and requestid into body



Proposed JIRAs :

15571614columnIds1636
#PriorityComponentDescriptionJIRAsEstimate
1DMI-PluginAccept  datastore name as param into URL 

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1550

5 Days
2NCMP Expose REST endpoint to accept collection of cm handles for GET operation (Passthrough only)

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1553

15 Days
3DMI-PluginExpose endpint for ONAP not impl. and Stub impl. for testing/demo

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1555

5 Days
4Stubbed DMI-PluginNCMPNCMP: Update existing REST endpoint that accepts bulk request for GET operationInclude code to send response messages to internal kafka topic with delay 10 Days5NCMP Forward response messages to client given kafka topic
Jira
serverONAP Jira

Jira
serverONAP Jira

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1556

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-

1635

5 Days
65NCMP DMI-PluginDMI-Plugin : Update endpoint to accept bulk requestHandle non-existing cm handles

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-15831636

5 3 Days
6Stubbed DMI-PluginInclude code to send response messages to internal kafka topic with delay 7NCMP Error handling for non-ready cm handle state
Jira

Jira

serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-

1556

5 10 Days
87NCMP Handle non responding DMI-PluginForward response messages to client given kafka topic

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-15581557

5 Days
98NCMPNCMP Handle non-existing cm handlesNCMP: Update existing REST endpoint that accepts bulk request for GET operation

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionstatus,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1583

5 Days
9NCMP Error handling for non-ready cm handle state

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-16351614

TBD5 Days
10MI-PluginNCMP Handle non responding DMI-Plugin : Update endpoint to accept bulk request

Jira
serverONAP Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-

1558

TBD5 Days
11CSIT test for demo

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1560

5 Days

...

  • Allow for 2 more user stories each may take 1 weeks
  • Based on 2 resource working  parallelly may take àpprox. 6 weeks from 29 March 2023  
  • The estimated date for completion is 19th 31st May ' 2023.