...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"eventId" : "9999", # some generic event uuid generated by DMI Plugin
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2021-11-16T16:42:25-04:00",
"eventSource" : "org.onap.ncmp", # ??? Is this needed?
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
“eventTarget” : “topic:client-application-topic”, ” # indicates where to route the event
- ‘topic’ is default target type
"event" : {
“response-data-schema” : “org.onap.cps.yang-patch-json:v1”,
“response-status” : “SUCCESS”,
“response-code” # -: ‘topic’“200”,
is default target type
"event": {
“response-data” “response-data-schema” : “org.onap.cps.yang-patch-json:v1”,{
“response-status” : “SUCCESS”,
…
“response-code” : “201”,
“response-data” : {
<response-data-payload> …
<response-data-payload>
…
# This }
is same as would }
} | ||||||
| Code Block | ||||||
| ||||||
{ "eventId" be returned by synchronous call : "33001",… } } } |
- Is this not NCMP to DMI rather than DMI to NCMP?
- Should response code above be OK?
- Is there too much information being returned to NCMP?
- Should we just return OK??
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{ "eventId" # some generic event uuid generated by NCMP “eventCorrelationId” : “request-009995”, : "33001", # for event correlation - acts as the request Id when # some generic event uuid generated by NCMP “eventCorrelationId” : “request-009995”, # for event correlation - acts as the request # eventType=org.onap.ncmp.asyncId wheneventType=sync-request-response-event "eventTime" : "2015-11-16T16:42:26-05:06", "eventSource" : "org.onap.ncmp", # The source of the event "eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events ”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events "eventOrigin" : { "eventId" : "00001", # some generic event uuid generated by DMI Plugin "eventTime" : "2021-11-16T16:42:25-04:00", -04:00", “eventCorrelationId” : “request-009995”, “eventCorrelationId” : “request-009995”, # Matches eventCorrelationId for new message to client for auditing "eventSource" : "org.onap.dmi", # ??? Is this needed? "eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events ”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events “eventTarget” : “topic:client-application-topic” }, "event" : { “response-data-schema” : “org.onap.cps.yang-patch-json:v1”, “response-status” : “SUCCESS”, “response-code” : “201”“200”, “response-data” : { … <response-data-payload> … } } } |
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"eventId" : "9999", # some generic event uuid generated by DMI Plugin
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2021-11-16T16:42:25-04:00",
"eventSource" : "org.onap.ncmp", # ??? Is this needed?
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
“eventTarget” : “topic:client-application-topic” ” # indicates where to route the event
# - ‘topic’ is default target type where to route the event - ‘topic’ is default target type "event" : {
“response-data-schema” : “org.onap.cps.generic-error:v1”,
“response-status” : “FAILURE”,
“response-code” : “404”,
“response-data” : {
…
<response-data-payload-as-org.onap.ncmp.generic-error:v1>
…
}
}
} |
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"eventId" : "33001", # some generic event uuid generated by NCMP
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2015-11-16T16:42:26-05:06",
"eventSource" : "org.onap.ncmp", # The source of the event
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
"eventOrigin" : {
"eventId" : "00001", # some generic event uuid generated by DMI Plugin
"eventTime" : "2021-11-16T16:42:25-04:00",
“eventCorrelationId” : “request-009995”,
"eventSource" : "org.onap.dmi", # ??? Is this needed?
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
“eventTarget” : “topic:client-application-topic”
}
"event" : {
“response-data-schema” : “org.onap.cps.generic-error:v1”,
“response-status” : “FAILURE”,
“response-code” : “404”,
“response-data” : {
…
<response-data-payload-as-org.onap.ncmp.generic-error:v1>
…
}
}
} |
...