CPS-1104 Agree LCM Event schemas

Use "Generic" Detail-fields or or more specific fields

@kieran mccarthy prefer to use specific terms like 'orginalState' instead of generic 'details'

how many event schema's for different events will there be?

e.g. 1 schema for state change, 1 other schema for public properties?
OR
a single schema with some fields not always of the used/compulsory

Need to discuss with @kieran mccarthy 

One single schema for all cmhandle LCM events : org.onap.ncmp:cmhandle-lcm-event:v1

what is the best term to use for change events 'original', 'previous' or something else

Team found term 'original' confusing and prefers 'previous' e.g. previousState

use 'oldValues' and 'newValues'.  See analysis below.

Should public properties be part of (same) structure as state

Team feels state and properties are very different and should not be combined into same structure
This also depends on open issue #2

Agreed at team meeting that all cmhandle metadata attributes to be managed in the same manner whether that is state or properties.

Should the schema version be separate from 'eventSchema'?

The event schema is defined like this : org.onap.ncmp:cmhandle-lcm-event:v1 where version is at the end of the schema string.  It would be better to split the schema version into its own header field.  e.g.

”eventSchema”               : “org.onap.ncmp:cmhandle-lcm-event",   
”eventSchemaVersion”   : “v1.0",   

@Toine Siebelink Can we split the schema version into its own field or is it a standard way to reference schema versions like the way CPS do it for their events (at least I think this is what they do?) like this : 'org.onap.ncmp:cmhandle-lcm-event:v1'

//priyank : Agreed to use the specified format in the notes in LCM Schema and also create a user story to handle the async schema on similar grounds.

Mentioning the mandatory and optional fields in our schemas.

Mandatory(M) and Optional(O)

Schema Sample : 

@kieran mccarthy  Please correct if something is wrong.

[kieran]  This looks good - the given eventSource may change but the format is fine.

Agree on the topic name where the events need to be published.

Previously we configured the topic name as "ncmp-events" , but since now we are calling these events as LcmEvents , I was wondering if the topic should reflect the same.

@Toine Siebelink  suggested "ncmp-lcm-events" as an alternative name.

@kieran mccarthy @Tony Finnerty  your thoughts on this ? 

@Priyank Maheshwari There is no reason to separate cm data events from these lcm events.  They are all ncmp events and the consumer may determine the nature of the event from eventType/eventSchema.  Sugegst to send them on ncmp-events topic.

How will the DELETING event look like ? 
It should be same as UPDATE event or some other handling is needed?

DELETING event

I just had this doubt and wanted to clarify.

@kieran mccarthy  @Toine Siebelink  @Tony Finnerty 

//priyank It will behave the same as update event. we discussed and clarified.

@Priyank Maheshwari The cmhandle LOCKED state should also be reflected in the event on the left (but ONLY if cmhandle LOCKED support is already implemented)