Overview Jira Legacy
server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key Overview
Jira Legacyserver System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1628
This page gives a description of CPS events including their fields Events will be split into events and Kafka headers Headers Issues & Decisions # Description Notes Decision 1 No Event properties defined for DMI AVC Event Priyank Maheshwari will need to specify and agreed event structure for DMI AVC Event with stakeholders ie. provide Jira ticket
Event Body should be compatible with RFC8641
kieran mccarthy has confirmed.
Priyank Maheshwari created JIRA to create the event body schema.
2 Bulk Operation events details have not yet be defined (just headers) Sourabh Sourabh to provide Jira tickets
Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1658
3 Should all the events have same
kafka headers Headers kieran mccarthy 26 Apr 2023 Possibly Common (base) set of headers but mandatory aspect might differ. In practice we might need a separate headers (schema?) for each event
4 Clarify the format of the version eventSchemaVersion v1 or 1.0
EX ex : 1.0.0 (without 'v')
kieran mccarthy to check ORAN preference
kieran mccarthy confirms through email on 12 May 2023 to use semantic versioning which ORAN follows https://semver.org .
5 What to do with additional event headers (from DMI Plugins) kieran mccarthy 26 Apr 2023 if DMI produce additional headers NCMP will discard those i.e. not included in forwarded events
6 Event(Content) field in DMI Async Request Response Event has inconsistent name (compared with other schemas) Add V2 file Deprecate V1 Support both versions for a while Delete the V1 version (after some time) CPS Team 27 Apr 2023 Create a V2 of the schema and rename eventContent as event data . Do it as part of the schema addition.
7 NCMP Async Request Response Event (#5) contains both an Event and ForwardedEvent ForwardedEvent is not wrapped inside Event but question now is if we need 2 events at all?!
Sourabh Sourabh and RAVITEJA KARUMURI (EST) can check how it is actually working and then we decide (create a JIRA ticket)
Wiki for the Study on NCMPAsyncRequestResponse event schema
Conclusion: events not designed as proposed, very inconsistent. Never go a bug because these async events aren't used at all (confirmed by Csaba Koscis) Instead bulk request wil be used for topology use cases.
10 May 2023 kieran mccarthy and team agreed to:
Temporary disable the legacy async request feature (task created: Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1694
) As part of a lower priority work items (but during Montreal)
fix fiX related events with learnings from the new batch-usecase. (task created Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1693
) 8 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
kieran mccarthy Clients can use this field as per their requirements.
9 Can
Kafka Headers be described with 'schema's owned and managed by NCMP POC to follow. Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1657
Defining header schema.
Integration of header with kafka.
Naming and versioning convention for the header schemas. 'id'
Does the headers schema have a version too?!
03 May 2023 Priyank Maheshwari confirmed headers can be described with a separate schema.
Both header schema's and event schemas will be published on https://docs.onap.org/projects/onap-cps/en/latest/cps-events.html
Header schema name and version will be maintained in the 'id' metadata field of header's schema .
10 Depending #10 can schema inherit/extend a common schema for common headers Commonly define them and then define what are mandatory(required) or optional as per the schema extending it.
If a field is not used in the extended schema then it should be able to handle it.
Extend extend the POC (on #9) to cover this.
09 May 2023 Priyank Maheshwari did the POC and the conclusion of that was that :-
One schema can extend the other schema. We cannot override the mandatory/optional parameter from the Parent schema. 09 May 2023 Toine Siebelink agrees to go ahead with separate schema/headers per event. There will be some duplication but it will have its advantage when versioning.
11 Is anyone using Async Request feature? See
Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1660
we need to re-design event #4 (Covers Point 6 as well) and #5 in a backward incompatible way. If no-one is using this feature right now (suspected) we can do this more easily/cheaper! 03 May 2023 Csaba Kocsis confirmed this is not used by Ericsson currently. No plans to use soon for single-cmhandle requests either (TBC). Need to decide priority ( Csaba Kocsis to find out of
fixing fiXing the legacy schema(s) See decision on issue #7
12 Do we need additionalProperties for DMI ASync Data Request respondes (events #4, #5) The original code populates a framework defined 'additionalProperties' field with a singel key-value pair: "response-data",{<json data>}. No other (private) properties are added either in DMI PLugin or NCMP code. The name is just coincidence and misleading. In fact this 'additionalProperties' field should NOT have been used at all! No, the new schema should NOT add 'additionalProperties' field at all use 'additionalProperties:no' in the schema 13 AVC Subscription Event (DMI → NCMP) (events #3) Want to understand what 'data' is datatype referring to under Subscription Event? What value comes under 'schemaName' & 'SchemaVersion' of Datatype definition under AVC Subscription Event? Reconfirmation needed on 'schemaName' & 'SchemaVersion' should be in the payload?
In meeting 26 Apr 2023 kieran mccarthy updated #3 is ON HOLD to analyse further.
Agreed with Toine Siebelink on 18 May 2023 that Priyank Maheshwari will look into this from now as they are working on something related to this.
14 Align headers with CNCF Cloud Events Using standard headers as defined by Cloud Events and possibly common header extension See Table below, CNFC Cloud Event alignment CPS will use Cloud Events 3PP for all current and legacy events to ensure common format 23 May 2023 kieran mccarthy and Toine Siebelink agreed on general idea but exact list of common headers need to be agreed Jira (first impl.) to be added!
Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1717
15 During the meeting we saw that the Kafka header fields were prefixed with " ce_ " so need to check if we are ok with that.
kieran mccarthy 07 Jun 2023 this issue is now no longer relevant as the decision was to use CNCF Cloud Events instead as per decision #14
14 Align headers with CNCF Cloud Events Using standard headers as defined by Cloud Events and possibly common header extension See Table below, CNFC Cloud Event alignment CPS will use Cloud Events 3PP for all current and legacy events to ensure common format 23 May 2023 kieran mccarthy and Toine Siebelink agreed on general idea but exact list of common headers need to be agreed Jira (first impl.) to be added!
Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1717
15 During the meeting we saw that the Header fields were prefiXed with " ce_ " so we need to check if we are ok with that.
assume " ce_ " can be used as all user of the CNCF lib will get this behavior, will check if it can be replaced with no prefix at all. Sourabh Sourabh and Priyank Maheshwari concluded a cloud events specific serializer is used that add this prefix and cannot easily be changed (also that would be inconsistent use of this library)
CPS Team recommend to accept this prefix and simply document that this prefer is required when filtering on kafka headers defined by CloudEvenst standard.
07 Jun 2023 team agreed with kieran mccarthy to accept "ce_" prefix on serialzied CE defined headers. Note . Event(s) documentation in RTD should mentioned this clearly too
16 Do will still need/ can we
stil still use schemas for header details with CNCF library ?! How to publish info about non-standard headers like correlationid ? Meeting on 31 May 2023 Team agreed refer to CNFC doc. and add list of extensions in RTD documentation. (key and value constraints)
17
inconsistent Inconsistent casing convention for header fields v. json data fields Just observing. All header ion CNCF are lowercase whereas json field are camelCase. Don't
want to change but want to make sure agree... to be added to ALL events (declared mandatory for CNFC events) to be added to ALL events (declared mandatory for CNFC events) kieran mccarthy 07 Jun 2023 confirm is is compulsory and a value will need to be set for all event definition. in NCMP a default value of 'ncmp' can be used if no other source is applicable. Toine Siebelink will update this page were needed to add this field and default value
Event Overview #1 LCM Event (NCMP → Client Apps) ...
ExpandCurrent LCM Event Object Kafka Event Field Notes CloudEvents Mapping eventID string The unique id identifying the event
x X Mandatory standard ( id ) eventCorrelationId string The id identifying the event. In LCMEvent this is always a cmhandleId
x X Optional (extension fields will be optional now) extension ( correlationid ) eventTime string The timestamp when original event occurred
x X Mandatory standard ( time ) eventSource string The source of the event
x X Mandatory standard ( source ) eventType string The type of the event
x X Mandatory standard ( type ) eventSchema string The schema that this event adheres to.
x E cps:org.onap.ncmp.cmhandle.lcm-event:1.0.0
standard ( dataschema ) eventSchemaVersion string The version of the schema that this event adheres to
x e.g v1.0
N/A included in 'dataschema' event Event The payload of an event X Mandatory standard ( data ) N/A N/A The version of CNCF Specification X Specified by CNCF (value hardcoded) standard ( specversion )
Type:Event (cps:org.onap.ncmp.cmhandle.lcm-event:v1) Kafka Event Field Notes cmHandleId string cmHandle id
x X oldValues Values Values that represents the state of a cmHandle
x X Defined by values object below newValues Values Values that represents the state of a cmHandle
x X Defined by values object below
Type:Values Kafka Event Field Notes dataSyncEnabled string cmHandle id
x X cmHandleState string State of cmHandle
x ["ADVISED", "READY", "LOCKED", "DELETING", "DELETED"] cmHandleProperties object cmHandle properties
x X List of Java <String, String> Maps
#2 DMI Data AVC Event (ONAP DMI → NCMP) ...
ExpandAVC Event Object Kafka Event Field Notes CloudEvents Mapping eventID string The unique id identifying the event
x X Mandatory standard ( id ) eventCorrelationId string The id identifying the event
x X Optional extension( correlationid ) eventTime string The timestamp when original event occurred
x X Optional standard ( time ) eventSource string The source of the event
x X Optional standard ( source ) eventType string The type of the event
x (e.g. cps:org.onap.cps.ncmp.events:avc-event) standard ( type ) eventSchema string The schema that this event adheres to
x X Mandatory (e.g. cps:org.onap.cps.ncmp.events:avc-event-schema) standard ( dataschema ) eventSchemaVersion string The version of the schema that this event adheres to
x X Mandatory N/A included in 'dataschema' event Event The payload of an event Mandatory standard ( data )
Type: Event (cps:org.onap.cps.ncmp.events:avc-event-schema:v1) Field Type Description Kafka HeaderEvent Payload Field Notes
...
AVC Subscription Event (External external Clients Apps → NCMP) : ON HOLD - kieran mccarthy to analyze further
Priyank Maheshwari We need to revisit this schema and include the cloud events fields. (At the moment this doesn't have proper fields)
Excerpt
Expandtitle AVC Subscription Event
Subscription Event Object
Kafka Event Field Notes CloudEvents Mapping version string The event type version X
ekiemcc : What is this version? This should be covered in the header now? included in dataschema eventType string The event type
X
ekiemcc : This is now covered by the header? Is this needed any longer in the body?
Enum:
["CREATE"]
standard ( type ) source NEW TBC, see issue #18
standard ( type ) source X NEW see decision #18, value <clientId> (same as in payload) TBC standard ( source ) event Event The payload for an event X Defined by event object below standard ( data )
Event Object ( cps:org.onap.cps.ncmp.events:avc-subscription-event:v1)
Kafka Event Field Notes subscription Subscription The subscription details
x X Defined by subscription object below dataType DataType The datatype content
x X Defined by dataType object below predicates Predicates Additional values to be added into the subscription
x X Defined by predicates object below
Type: Subscription
Kafka Event Field Notes clientID string The client ID
x X name string The name of the subscription
x X isTagged boolean optional parameter, default is false
x Kafka Event Field Notes dataspace string The dataspace name
x X dataCategory string The category type of the data
x X dataProvider string The provider name of the data
x X schemaName string The name of the schema
x X schemaVersion string The version of the schema
x Kafka Event Field Notes targets array CM Handles to be targeted by the subscription
x X datastore string datastore which is to be used by the subscription
x xpath Xpath -filter string filter to be applied to the CM Handles through this event
x
#4 DMI Async Request Response Event (DMI → NCMP) ...
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
Expandtitle DMI Async Request Response Event
DmiAsyncRequestResponse Event Object
Kafka Event Payload Field Payload Notes CloudEvents Mapping eventID string The unique id identifying the event generated by DMI
x X standard ( id ) eventCorrelationId string The request id passed by NCMP
x X extensions ( correlationid ) eventTime string The timestamp when original event occurred
x X standard ( time ) eventTarget string The target of the event
x X extensions ( target ) eventType string The type of the event
x X standard ( type ) eventSchema string The event schema for async request response events
x X standard ( dataschema ) eventSchemaVersion string The event schema version for async request response events
x X N/A included in 'dataschema' eventSource string The source of the event
x X standard ( source ) eventContent EventContent The payload of an event The name of this fields is inconsistent with all other event schemas, see issue #6
standard (data)
Type: EventContent (cps:org.onap.cps.ncmp.events:dmi-async-request-response-event-schema:v1) Kafka Event Field repsonse response -data-schema string The schema of response data
x X response-status string The status of the response
x X response-code string The code of the response
x X response-data object The data payload
x X contains payload of type object
#5 NCMP Async Request Response Event (NCMP → Client App) ...
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
Expandtitle NCMP Async Request Response Event
NcmpAsyncRequestResponse Event Object Kafka Event Field Notes CloudEvents Mapping eventID string The unique id identifying the event generated by DMI
x X standard ( id ) eventCorrelationId string The request id passed by NCMP
x X extensions ( correlationid ) eventTime string The timestamp when original event occurred
x X standard ( time ) eventTarget string The target of the event
x X extensions ( target ) eventType string The type of the event
x X standard ( type ) source string The source of the event X NEW see decision #18, value 'ncmp' standard ( source ) eventSchema string The event schema for async request response events
x X standard ( dataschema ) eventSchemaVersion string The event schema version for async request response events
x X N/A included in 'dataschema' event Event The payload of an event X Defined by event object below standard (
source data ) forwardedEvent ForwardedEvent The payload of a forwarded event X Relation to Event field unclear, do we need 2 events at all see issue #7
standard ( data ) See new proposal below
Type: Event (cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1) Kafka Event Field Notes eventID string The unique id identifying the event generated by DMI
x X Only in payload in v1 of the payload schema. To be removed in v2 version (will be in the header only) eventCorrelationId string The request id passed by NCMP
x X as above eventTime string The timestamp when original event occurred
x X as above eventTarget string The target of the event
x X as above eventType string The type of the event
x X as above eventSchema string The event schema for async request response events
x X as above eventSource string The source of the event
X
x as above response-data-schema string The received schema of response data
x X response-status string The received status of the response
x X
response-code string The received code of the response
x X response-data object The data payload
x X contains payload of type object
Type: forwarded Event (cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1) Field Type Description Kafka HeaderEvent Payload Field Notes eventID string The unique id identifying the event generated by DMI ? Can NCMP put these in the header and remove them from the 'forwardedEvent' eventCorrelationId string The request id passed by NCMP
? as above eventTime string The timestamp when original event occurred ? as above eventTarget string The target of the event ? as above eventType string The type of the event ? as above eventSchema string The event schema for async request response events
? as above eventSchemaVersion string The event schema version for async request response events
? as above eventSource string The source of the event
? as above response-data-schema string The received schema of response data
x X response-status string The received status of the response
x X
response-code string The received code of the response
x X response-data object The data payload
x X contains payload of type object
Proposed New Schema: see
Jira Legacyserver System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-1660
Kafka Event Field Notes CloudEvents Mapping eventID string The unique id identifying the event generated by DMI X standard ( id ) eventCorrelationId string The request id passed by NCMP
X extensions( correlationid ) eventTime string The timestamp when original event occurred X standard ( time ) eventSource string The source of the event X What value should contain in this? Needs clarification, see issue #8 standard ( source ) eventType string The type of the event X standard ( type ) eventSchema string The event schema for async request response events
X standard ( dataschema ) eventSchemaVersion string The event schema version for async request response events
X N/A included in ' dataschema ' event Event The payload of an event X Defined by event object below standard ( data )
Type: Event (cps:org.onap.cps.ncmp.events:ncmp-async-request-response-event-schema:v1) Kafka Event Field Notes eventCorrelationId string The request id passed by NCMP
X as above @Toine asked to add this property. responseStatus string The received status of the response
X
responseCode string The received code of the response
X responseData object The data payload
X contains payload of type object
#6 ...
Data Operation (response) Event (DMI → NCMP) Description Batch (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
Expandtitle DMI Async Batch Response Event
BatchResponseEvent DmiDataOperationEvent Object
Kafka Event Field Notes CloudEvents Mapping eventID string The unique id identifying the event generated by DMI
x . Generated by DMI-Plugin
standard ( id ) eventCorrelationId string The request id passed by NCMP
x X Mandatory. This is requestId that NCMP sent to client as an ACK.
Example example : “request-1234" (UUID)
extensions extension ( correlationid ) eventTarget string The destination topic of the client
x X Mandatory. TBC example: my-topic
extensions target TBC destination ) source string The source of the event
Optional Example example : dmi-plugin:enm-1 (dmi service name ) standard ( source ) eventTime string The timestamp when original event occurred
x Example example : 1985-04-12T23:20:50.52Z this represents 20 minutes and 50.52 seconds after the 23rd hour of April 12th, 1985 in UTC.
standard ( time ) eventType string The type of the
event x Mandatory. NCMP owns eventType that would be used by dmi-plugins event X Mandatory. NCMP owns eventType that would be used by dmi-plugins The Convention of eventType and Schema names is under discussion, see open issue #17 on CPS-1515 Spike standard ( type ) eventSchema string The event schema for async request response events
X Mandatory. The Convention of eventType and Schema names is under discussion, see open issue
#17on type eventSchema eventSchemaVersion string The event schema version for async request response events
x Mandatory. The Convention of eventType and Schema names is under discussion, see open issue #17on CPS-1515 Spike standard ( dataschema ) eventSchemaVersion string The event schema version for async request response events
x N/A included in 'dataschema' event Event The payload of an event x java object not yet defined by schema, see issue #2 standard ( data ) N/A N/A Version of CNCF standard (hardcode value) specversion Type: Event ( cps:org.onap.cps.ncmp.event.async:dmi-async-batch -response-event-schema:v1)
X N/A included in ' dataschema ' event Event The payload of an event X java object not yet defined by schema, see issue #2 standard ( data ) specversion String Version of CNCF spec X hardcoded value of 1.0 standard ( specversion )
Type: Event ( cps:org.onap.cps.ncmp.event.async:dmi-data-operation -event-schema:v1)
Field Type Description Header Payload Notes No Properties defined (Entire event treated as single object)
#7 Data Operation (response) Event (NCMP → Client App) Description Batch (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
Expandtitle NCMP Async Batch Response Event - Client Topic
NcmpDataOperationEvent Object
Kafka Event Field No Properties defined (Entire event treated as single object)
#7 Batch Response Event (NCMP → Client App) Description Batch (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
...
title NCMP Async Batch Response Event - Client Topic
BatchResponseEvent Object
...
The request id passed by NCMP
...
The event schema for async request response events
...
The event schema version for async request response events
...
Type: Event ( cps:org.onap.cps.ncmp.event.async:ncmp-async-batch -response-event-schema:v1)
...
CNCF Cloud Event alignment Introduction Image Removed
CNCF CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.
These cloud events will be applied to all the internal and external events we have in CPS , NCMP and DMI Plugin. Cloud events will be taking care of the fields which are part of kafka headers or part of the actual payload ( fields other than "data" are sent as kafka headers ) These CNCF cloud events will be applied to all the events listed in above sections ( LCM , DMI Data AVC etc. ) Library References https://github.com/cloudevents/spec
https://github.com/cloudevents/sdk-java https://mvnrepository.com/artifact/io.cloudevents Examples : https://github.com/cloudevents/sdk-java/tree/main/examples/kafka/src/main/java/io/cloudevents/examples/kafka The table below shows how previously proposed headers should be mapped to pre-defined CNFC headers.
...
Before
...
After
...
eventId
...
id
...
eventSource
...
source
...
N/A
...
specversion (default 1.0)
...
eventType
...
type
...
eventTime
...
time
...
eventSchema
...
dataschema
...
Optional includes the version of the schema
...
withDataContentType() ...
Optional This will be part of the extensions field in the cloud events and all the restrictions of the attribute field naming applies to it.
i.e these fields will be in the small case.
This is marked as optional as it only applies to some events.
...
CloudEvents Mapping eventID string The unique id identifying the event generated by DMI X standard ( id ) eventCorrelationId string The request id passed by NCMP
X extensions ( correlationid ) eventTime string The timestamp when original event occurred X standard ( time ) eventType string The type of the event X standard ( type ) source string The source of the event X NEW see decision #18, value 'ncmp' standard ( source ) eventSchema string The event schema for async request response events
X standard ( dataschema ) eventSchemaVersion string The event schema version for async request response events
X N/A included in ' dataschema ' event Event The payload of an event X Java object not yet defined by schema, see issue #2 standard ( data )
Type: Event ( cps:org.onap.cps.ncmp.event.async:ncmp-data-operation -event-schema:v1)
Field Type Description Header Payload Notes No Properties defined (Entire event treated as single object)
CNCF Cloud Event alignment Introduction Image Added
CNCF CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.
These cloud events will be applied to all the internal and external events we have in CPS , NCMP and DMI Plugin. Cloud events will be taking care of the fields which are part of Headers or part of the actual payload (fields other than "data" are sent as Headers) These CNCF cloud events will be applied to all the events listed in above sections (LCM , DMI Data AVC etc.) Library References https://github.com/cloudevents/spec
https://github.com/cloudevents/sdk-java https://mvnrepository.com/artifact/io.cloudevents examples : https://github.com/cloudevents/sdk-java/tree/main/Examples/kafka/src/main/java/io/cloudevents/Examples/kafka The table below shows how previously proposed headers should be mapped to pre-defined CNFC headers.
Before
After 1
CloudeEvent builder method Example Value Notes eventId
(ce_)id
.withId() Mandatory eventSource
(ce_)source
.withSource() Mandatory N/A
(ce_)specversion (default 1.0)
.v1() 1.0 Mandatory - This is the version of the cloud events eventType
(ce_)type
.withType() Mandatory eventTime
(ce_)time
.withTime() Optional (could be Mandatory for eventSchema
(ce_)dataschema
.withDataSchema() Optional includes the version of the schema
content-type 2 withDataContentType() application/json Optional eventCorrelationId (ce_)correlationid .withExtension() Optional This will be part of the extensions field in the cloud events and all the restrictions of the attribute field naming applies to it.
i.e these fields will be in the small case.
This is marked as optional as it only applies to some events.
event (ce_)data .withData(json TBC) Mandatory actual event/payload now would be under "data" field.
Note 1 all cloud-event headers will be prefixed during serialization with 'ce_' (this means when filtering on serialized Kafka-headers this prefix need to be applied) Note 2 content-type is a a 'default' header name no 'wrapped' by CloudEvents and hence the inconsistency in names and that is does NOT have the 'ce_' prefix. Common NCMP response staus code & message : Status-code 0-99 is reserved for any success response Status-code from 100 to 199 is reserved for any failed response. Status Code
Status Message
0 Successfully applied changes 100 cm handle id(s) is(are) not found 101 cm handle id(s) is(are) in non ready state 102 dmi plugin service is not responding 103 dmi plugin service is not able to read resource data
