Proprietary options or not in the scope of this analysis.
agreed with kieran mccarthy ; these are optional parameters (name-value pairs) not interpreted by NCMP but can be interpreted by proprietary plugins In the future "scope" might become standardized instead of proprietary but that wil be achieved through a separate requirement
2
same xpath (resourceIdentifierInQuery) for all cm handles or different for each cm handle
agreed with kieran mccarthy ; if different resources are required on the same cm-handle the client wil send another (batch) request
3
options, resourceIdentifier is optional for bulk operations.
operation, datastore and cmhandleIds are mandatory fields
agreed with CPS team.
Issues & Decisions
#
Issue
Notes
Decision
1
Which operation(s) need support for multiple cm handles?
Additional error (messages) response with all cm-handles that cannot be resolved, also a separate error message wil be sent for each failed DMI
11
Overlap/clash with Deutsche Telekom user story:
Jira
server
ONAP Jira
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
key
CPS-1377
?!
discussed in weekly ONAP meeting the DT user story is affect CPS-Core interface (not NCMP) and the requirement is to execute a query over ALL cm-handles (cached only?!) instead of a given list of cm-handles (~anchors)
1) Agreement required on the structure of the response. Please see response structure below. 2) Does 'eventTime' field which holds the timestamp of the bulk response event, required or can it be dropped?
Code Block
title
Schema of bulk response
collapse
true
{
"$schema": "https://json-schema.org/draft/2019-09/schema",
"$id": "urn:cps:org.onap.cps.ncmp.events:bulk-response-event-schema:v1",
"$ref": "#/definitions/BulkResponseEvent",
"definitions": {
"BulkResponseEvent": {
"description": "The payload for bulk response event.",
"type": "object",
"properties": {
"eventId": {
"description": "The unique id identifying the event generated by DMI for this bulk response event.",
"type": "string"
},
"eventCorrelationId": {
"description": "The request id passed by NCMP for this bulk response event.",
"type": "string"
},
"eventTime": {
"description": "The time of bulk response event. The expected format is 'yyyy-MM-dd'T'HH:mm:ss.SSSZ'.",
"type": "string"
},
"eventType": {
"description": "The type of bulk response event.",
"type": "string"
},
"eventSchema": {
"description": "The event schema for bulk response event.",
"type": "string"
},
"eventSchemaVersion": {
"description": "The event schema version for bulk response event.",
"type": "string"
},
"event": {
"$ref": "#/definitions/Event"
}
},
"required": [
"eventId",
"eventCorrelationId",
"eventTime",
"eventType",
"eventSchema",
"eventSchemaVersion"
]
},
"Event": {
"description": "The bulk response event content.",
"type": "object",
"existingJavaType": "java.lang.Object"
}
}
}
1. Do we need to send only one response containg all the requested cm handles ? 2. Send single response for each cm handle? 3. Single response message per dmi plugin?