...
| # | Description | Notes | Decision | ||
|---|---|---|---|---|---|
| 1 | No Event properties defined for DMI AVC Event | Priyank Maheshwari will need to specify and agreed event structure for | DNI DMI AVC Event with | stakeholdersstakeholders ie. provide Jira ticket | |
| 2 | No Event properties defined for Bulk Response Events [Internal & client] | ||||
| 3 | Should all the events have same kafka headers | kieran mccarthy Posissbly Common (base) set of headers but mandatory aspect might differ. In practice we might need a separate headers (shema?) for each event | |||
| 4 | Clarify the format of the version eventSchemaVersion | v1 or 1.0 | kieran mccarthy to check ORAN preference | ||
| 5 | What to do with additional event headers (from DMI Plugins) | if | if DMI produce Additional headers NCMP will discard | thoe those ie. not included in forwarded events | |
| 6 | Event(Content) field in DMI Async Request Response Event has inconsistent name (compared with other schemas) | ||||
| 7 | NCMP Async Request Response Event contains both an Event and ForwardedEvent | ForwardedEvent is not wrapped inside Event but question now is if we need 2 events at all?! | |||
| 8 | Bulk Operation events details have not yet be defined (just headers) | Sourabh Sourabh to create provide Jira 'stickets | |||
| 9 | Dmi Data AVC Event, use of eventSource field | Priyank Maheshwari wanted to store 'datastore' in this field but kieran mccarthy explained it to use for different purposes | |||
| 10 | Can Kafka Headers be describe with 'schema's owned and managed by NCMP | ||||
| 11 | Depending #10 can schema inherit/extend a common schema for common headers | alternatively we just create many schemas and ensure common fields are defined consistently |
Event Overview
| #Description | Short Name | Source | Destination | Impl. Status | Notes | Full Schema Name | Diagram Ref. | |
|---|---|---|---|---|---|---|---|---|
| 1 | LCM Event | NCMP | ExternalClient Apps | In Use | Life Cycle Management Events, when cmHandles are added or removed | cps:org.onap.ncmp.cmhandle.lcm-event:v1 | CM-Handle State Changes and Notifications Overview#Notificationhandlingincode | |
| 2 | DMI Data AVC Event | DMI | NCMP | Implemented, Not in use | Attribute Value Change in configuration management (CM) data. | cps:org.onap.cps.ncmp.events:avc-event-schema:v1 | 5 in CPS Data Notifications Overview#ComponentDiagram | |
| 3 | AVC Subscription Create Event | External Client AppsClient | NCMP | - Fwd to DMI& DMIs | Implemented, Not in use | Create Event Only | cps:org.onap.cps.ncmp.events:avc-subscription-event:v1 | 7 in CPS Data Notifications Overview#ComponentDiagram |
| 4 | DMI Async Request Response Event | DMI | NCMP | In Use | DMI passes response onto Kafka topic specified by client. | cps:org.onap.cps.ncmp.events:dmi-async-request-response-event-schema:v1 | 3b → 4a in CPS-821 Spike: Support Async read-write operations on CPS-NCMP interface#ProposedDesign | |
| 5 | NCMP Async Request Response Event | NCMP | ExternalClient Apps | In Use | Forward No.4 to client specified topic | cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1 | 4b → 5 in CPS-821 Spike: Support Async read-write operations on CPS-NCMP interface#ProposedDesign | |
| 6 | Bulk Response Event (Internal) | DMI | NCMP | In Progress | Internal Kafka topic | cps:org.onap.cps.ncmp.event:dmi-async-bulk-response-event-schema:v1 | 5 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations) | |
| 7 | NCMP | External ClientClient Apps | In Progress | Forwarding the DMI responses to the client topic | cps:org.onap.cps.ncmp.event:ncmp-async-bulk-response-event-schema:v1 | 6 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations) |
#1 LCM Event (NCMP → Client Apps)
...