Key


Event 1Event 2
OwnerDMI ?NCMP
Repo & location

cps-events/src/main/resources/schemas/cps-async-request-response-event-schema.json *

* this may change once ownership is established

cps-events/src/main/resources/schemas/cps-async-request-response-event-with-origin-schema.json
TypeT1 = org.onap.???:async-request-response-event:v1T2 = org.onap.ncmp:async-request-response-event:v1
SchemaS1 = org.onap.???.async-request-response-eventS2 = org.onap.ncmp:async-request-response-event:v1
ProducerDMINCMP
ConsumerNCMPClient


Questions

#IssueAnswer
1

Which application owns which schemas?

Both are owned by NCMP and will live in an ncmp module. 
2Can different plugins use different schemas for event 1?!
Alternatively maybe agree a base event which can be extended?!		Yes, event 1 can be defined by dmi but prefer to use ncmp provided event
3

Where does the schemas reside exactly (related to #1)

new ncm-events module. update rtd with reference to event schemas
4

Does NCMP or DMI need to interpret the schema in any way?

    1. Or is it fir the client?
No
5

Should the eventSchema and eventType be the same in both events?

(e.g. S1 & T1)

They can be the same and different depending on the event and wrapper
6

What data exactly goes in the "event":  { ... } blocks?

if event origin is there use that, if not use event.

for this user story only forwardedEvent will be used. But the schema will contain both forwardedEvent and event.

(perhaps rename eventOrigin also - forwardedEvent, )

Notes

#Note
1

Event ids are different between ncmp-dmi and dmi-ncmp

2

Correlation event id remains the same for auditing


Sample Output 
{
  "eventId": "44acf596-535d-4d54-aa2d-a5a5f6ca34a7",
  "eventCorrelationId": "9741e21b-7de4-46a0-b61f-76a55311a5d4",
  "eventTarget": "my-topic-999",
  "eventTime": "2022-05-09T13:50:37.093+0000",
  "forwardedEvent": {
    "eventId": "0ee3fcbf-6cd5-41a7-9dca-5c454b4f9dfa",
    "eventCorrelationId": "9741e21b-7de4-46a0-b61f-76a55311a5d4",
    "eventTime": "2022-05-09T13:50:36.958+0000",
    "eventSource": "org.onap.ncmp",
    "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "eventTarget": "my-topic-999",
    "response-data": {
      "ietf-netconf-monitoring:netconf-state": {
        "schemas": {
          "schema": [
            {
              "identifier": "ietf-tls-server",
              "version": "2016-11-02",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-tls-server",
              "location": [
                "NETCONF"
              ]
            }
          ]
        }
      }
    }
  }
}



Overview

  • No labels