Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#DescriptionNotesDecision
1No Event properties defined for DMI AVC Event

Priyank Maheshwari will need to specify  and agreed event structure for DNI AVC Event with stakeholders

2No Event properties defined for Bulk Response Events [Internal & client] 

3Should all the events have same kafka headers

kieran mccarthy  Posissbly Posissbly Common (base) set of headers but mandatory aspect might differ. In parctvie practice we might need a separate headers (shema?) for each event

4Clarify the format of the version eventSchemaVersionv1 or 1.0

kieran mccarthy to check ORAN preference

5What to do with additional event headers (from DMI Plugins)

kieran mccarthy   if DMI produce Additional headers NCMP will discard thoe ie. not included in forwarded events

Event Overview

#DescriptionSourceDestinationStatusNotesFull Schema NameDiagram Ref.
1LCM EventNCMPExternal Client AppsIn UseLife Cycle Management Events, when cmHandles are added or removedcps:org.onap.ncmp.cmhandle.lcm-event:v1CM-Handle State Changes and Notifications Overview#Notificationhandlingincode
2DMI Data AVC EventDMINCMPImplemented, Not in useAttribute Value Change in configuration management (CM) data.cps:org.onap.cps.ncmp.events:avc-event-schema:v15 in CPS Data Notifications Overview#ComponentDiagram
3AVC Subscription Create EventExternal Client AppsNCMP - Fwd to DMIImplemented, Not in useCreate Event Only

cps:org.onap.cps.ncmp.events:avc-subscription-event:v1

7 in CPS Data Notifications Overview#ComponentDiagram
4DMI Async Request Response EventDMINCMPIn UseDMI 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
5NCMP Async Request Response EventNCMPExternal Client AppsIn UseForward 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
6Bulk Response Event (Internal)DMINCMPIn ProgressInternal Kafka topiccps:org.onap.cps.ncmp.event:dmi-async-bulk-response-event-schema:v15 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations)
7

Bulk Response Event (Client)

NCMPExternal Client AppsIn ProgressForwarding the DMI responses to the client topiccps:org.onap.cps.ncmp.event:ncmp-async-bulk-response-event-schema:v16 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations)

#1 LCM Event (NCMP → Client Apps)

Description

LCM (Life Cycle Management) Event. Sent by NCMP when the state of a CM Handle changes. For diagram see CM-Handle State Changes and Notifications Overview#Notificationhandlingincode

Expand
titleLCM Event Details

Current LCM Event Object

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes (M=Mandatory, O=Optional)
eventIDstringThe unique id identifying the eventx
M
eventCorrelationIdstringThe id identifying the event.  In LCMEvent this is always a cmhandleIdx
eventTimestringThe timestamp when original event occurredx
M
eventSourcestringThe source of the eventx
M
eventTypestringThe type of the eventx
M
eventSchemastringThe schema that this event adheres to. x

M
E.g. cps:org.onap.ncmp.cmhandle.lcm-event

eventSchemaVersionstring

The version of the schema that this event adheres to

x

M

e.g v1.0 → v2.0

eventEventThe payload of an event

M

Type:Event (cps:org.onap.ncmp.cmhandle.lcm-event:v1

Defined by event object below

ekiemcc : Suggest to add the full schema name for the LCM event body and the eventSchemaVersion

Type:Event

)

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
cmHandleIdstringcmHandle id
x
oldValuesValues

Values that represents the state of a cmHandle


xDefined by values object below
newValuesValuesValues that represents the state of a cmHandle
xDefined by values object below

Type:Values

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
dataSyncEnabledstringcmHandle id
x
cmHandleStatestring

State of cmHandle


xEnum: 

["ADVISED", "READY", "LOCKED", "DELETING", "DELETED"]

cmHandlePropertiesobjectcmHandle properties
xList of Java <String, String> Maps


#2 DMI

...

Data AVC Event  (ONAP DMI → NCMP)

Description

DMI A normalized AVC Event  (DMI → NCMP)that ONAP DMI Plugin will send to NCMP. NCMP can process the event and update cached data if needed. See 5 in CPS Data Notifications Overview#ComponentDiagram
Other DMI Plugin might snet similar events, using same headers but different payload and value for 'eventSchema' Depending on the AVC subscription details those events might or might not be forwarded to the Client Apps.

Expand
titleAVC Event Details

AVC Event Object

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes (M=Mandatory, O=Optional)
eventIDstringThe unique id identifying the eventxMM
eventCorrelationIdstringThe id identifying the eventxMM
eventTimestringThe timestamp when original event occurredxOO
eventSourcestringThe source of the eventxOO
eventTypestringThe type of the eventxMM (e.g. cps:org.onap.cps.ncmp.events:avc-event ?)
eventSchemastringThe schema that this event adheres toxMM (e.g. cps:org.onap.cps.ncmp.events:avc-event-schema)
eventSchemaVersionstring

The version of the schema that this event adheres to

xMM (e.g. v1.0 → v2orv2.0)
eventEventThe payload of an event

M

Type: Event (cps:org.onap.cps.ncmp.events:avc-event-schema:v1)

Type: Event

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
No Properties defined (Entire entire event treated as single object) See open issue #1


AVC Subscription Event

Description

...

Expand
titleNCMP Async Request Response Event

NcmpAsyncRequestResponse Event Object

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
eventIDstringThe unique id identifying the event generated by DMIx

eventCorrelationIdstring

The request id passed by NCMP

x

eventTimestringThe timestamp when original event occurredx

eventTargetstringThe target of the eventx

eventTypestringThe type of the eventx

eventSchemastring

The event schema for async request response events

x

eventSchemaVersionstring

The event schema version for async request response events

x

eventEventThe payload of an event

Defined by event object below
forwardedEventForwardedEventThe payload of a forwarded event

Defined by forwardedEvent object below

ekiemcc: This is a sub-element of 'event' payload as I recall which woulld be defined by the 'eventSchema'?

Type: Event 

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
eventIDstringThe unique id identifying the event generated by DMI
xOnly in payload in v1 of the payload schema.  To be removed in v2 version (will be in the header only)
eventCorrelationIdstring

The request id passed by NCMP


xas above
eventTimestringThe timestamp when original event occurred
xas above
eventTargetstringThe target of the event
xas above
eventTypestringThe type of the event
xas above
eventSchemastring

The event schema for async request response events


xas above
eventSourcestring

The source of the event


x
response-data-schemastring

The received schema of response data


x
response-statusstring

The received status of the response


x


response-codestring

The received code of the response


x
response-dataobject

The data payload


xcontains payload of type object

Type: forwardedEvent

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
eventIDstringThe unique id identifying the event generated by DMI
?Can NCMP put these in the header and remove them from the 'forwardedEvent'
eventCorrelationIdstring

The request id passed by NCMP


?as above
eventTimestringThe timestamp when original event occurred
?as above
eventTargetstringThe target of the event
?as above
eventTypestringThe type of the event
?as above
eventSchemastring

The event schema for async request response events


?as above
eventSchemaVersionstring

The event schema version for async request response events


?as above
eventSourcestring

The source of the event


?as above
response-data-schemastring

The received schema of response data


x
response-statusstring

The received status of the response


x


response-codestring

The received code of the response


x
response-dataobject

The data payload


xcontains payload of type object


...