References
...
Proposed CM event |
---|
{ "eventId" : "9999", # some generic event uuid generated by DMI Plugin "event": { "push-change-update" : { "datastore-changes" : { {
} } } |
CM Change Event Subscription Proposal
Create Subscription
The Create Subscription event will
Create Subscription Format | Create Example |
---|---|
{ } | { } |
Update Subscription
Topics
Topic types
Topic Name | Description | Direction |
---|---|---|
cm- |
avc[-<targetgroup>] | topic for publication of events from NCMP to clients (suggest to rename existing topic from 'ncmp-events' to cm- |
avc). In preparation to future needs the there may be separate topics for different security groups. NCMP solution should consider this in its design this upfront. By default cm- |
avc is the default topic where ALL events are published by default. Different client may subscribe to different topics (ALL and/or target group specific). It is their responsibility to subscribe to the appropriate topics as new target groups come into existance. For now the only topic in scope of this story is the 'cm- |
avc' topic. | ncmp → client consumer | |
dmi-cm-events | internal topic for communications between dmi-plugin ↔ ncmp for avc and subscription events | ncmp→ dmi |
cm-avc-subscription | topic for avc event subscriptions. This topic may be (pre)defined external to NCMP. If |
externally defined topic then it |
shall be possible to tell NCMP the topic name and where to find it. | client → ncmp |
cm-avc-dmi- |
subscription |
topic for |
avc event subscriptions event toward dmi plugin(s). This topic is internally defined by NCMP. All CM AVC subscriptions will be sent from NCMP to DMI plugins via this topic. | ncmp → dmi for subscription LCM dmi → ncmp register device subscription in cmhandle |
Topic partitioning
All events for the same cmhandleId should be sent to the same partition. This will guarantee ordering. Ordering is only guaranteed per topic, not across topic (future consideration).
...