You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

Overview

CPS-1628 - Getting issue details... STATUS

  • This page gives a description of CPS events including their fields
  • Events will be split into events and Kafka headers

Issues & Decisions:

#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 Common (base) set of headers but mandatory aspect might differ. In 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

6Event(Content) field in DMI Async Request Response Event has inconsistent name (compared with other schemas)

7NCMP Async Request Response Event contains both an Event and ForwardedEventForwardedEvent is not wrapped inside Event but question now is if we need 2 events at all?!
8Bulk Operation events details have not yet be defined (just headers)

Sourabh Sourabh to create Jira's


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

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

eventEventThe payload of an event

M

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

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

A normalized AVC Event  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.

AVC Event Object

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

The version of the schema that this event adheres to

x
M (e.g. v1.0 orv2.0)
eventEventThe payload of an event

M

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

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

#3 AVC Subscription Event (DME → NCMP)

Description

AVC Subscription Event  (External Clients Apps  → NCMP) : ON HOLD - kieran mccarthy to analyze further

Subscription Event Object

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
versionstringThe event type version

ekiemcc : What is this version?  This should be covered in the header now?
eventTypestring

The event type



ekiemcc : This is now covered by the header?  Is this needed any longer in the body?

Enum: 

["CREATE"]

eventEventThe payload for an event

Defined by event object below

Event Object (cps:org.onap.cps.ncmp.events:avc-subscription-event:v1)

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
subscriptionSubscriptionThe subscription details
xDefined by subscription object below
dataTypeDataType

The datatype content


xDefined by dataType object below
predicatesPredicates

Additional values to be added into the subscription


xDefined by predicates object below

Type: Subscription

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
clientIDstring

The client ID


x
namestring

The name of the subscription


x
isTaggedboolean

optional parameter, default is false


xdefault: false

Type: DataType

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
dataspacestring

The dataspace name


x
dataCategorystring

The category type of the data


x
dataProviderstring

The provider name of the data


x
schemaNamestring

The name of the schema


x
schemaVersionstring

The version of the schema


x

Type: Predicates

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
targetsarray

CM Handles to be targeted by the subscription


x
datastorestring

datastore which is to be used by the subscription


x
xpath-filterstring

filter to be applied to the CM Handles through this event


x

#4 DMI Async Request Response Event (DMI → NCMP)

Description

This event is for the asynchronous responses  from DMI to NCMP following (synchronous) requests (from NCMP) specifying a (response) topic. See 3b → 4a in CPS-821 Spike: Support Async read-write operations on CPS-NCMP interface#ProposedDesign

DmiAsyncRequestResponse 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

eventSourcestringThe source of the eventx

eventContentEventContentThe payload of an event

The name of this fields is inconsistent with all other event schemas, see issue #6

Type: EventContent (cps:org.onap.cps.ncmp.events:dmi-async-request-response-event-schema:v1)

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
repsonse-data-schemastring

The schema of response data


x
response-statusstring

The status of the response


x
response-codestring

The code of the response


x
response-dataobjectThe data payload
xcontains payload of type object

#5 NCMP Async Request Response Event (NCMP → Client App)

Description

This event is for the asynchronous responses from NCMP to Client Apps following (synchronous) requests (from client) specifying a (response) topic. See 4b → 5 in CPS-821 Spike: Support Async read-write operations on CPS-NCMP interface#ProposedDesign

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

Relation to Event field unclear, do we need 2 events at all see issue #7

Type: Event (cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1)

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 (cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1)

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

#6 Bulk Response Event (DMI → NCMP)

Description

Bulk (data) request will always result in asynchronous events (responses) sent to the client. This event is the response from DMI to NCMP. See 5 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations)#BulkRequestMessageFlow

BulkResponseEvent Object

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

eventCorrelationIdstring

The request id passed by NCMP

x

eventTargetstringThe destination topic of the clientx

eventTimestringThe timestamp when original event occurredx

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
xjava object not yet defined by schema, see issue#8

Type: Event (cps:org.onap.cps.ncmp.event:dmi-async-bulk-response-event-schema:v1)

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
No Properties defined (Entire event treated as single object)

#7 Bulk Response Event (NCMP → Client App)

Description

Bulk (data) request will always result in asynchronous events (responses) sent to the client. This event is the response from DMI to NCMP. See 6 in CPS-1515: Spike: Support Multiple CM-Handles for NCMP Get Operation (bulk / batch operations)#BulkRequestMessageFlow

BulkResponseEvent 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

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
xJava object not yet defined by schema, see issue#8

Type: Event (cps:org.onap.cps.ncmp.event:ncmp-async-bulk-response-event-schema:v1)

FieldTypeDescriptionKafka HeaderEvent Payload FieldNotes
No Properties defined (Entire event treated as single object)
  • No labels