...
...
...
...
...
...
Table of Contents |
---|
References
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
# | Issue | Notes | Decision |
---|---|---|---|
1 | List scenarios | Need to clarify scenarios | Refer to Internal study |
2 | Topics | what topics are used in what scenario (topic for each Datastore ?) | See Topics section below.
cm-events topic name should be configurable in deployment settings.
|
3 | Handle unknown event schemas | Wrap event? | Unsupported for now. Thrown exception and log error. |
Event Flow Sketch
CM Event Specification Outline
...
Proposed CM event |
---|
{ "eventId" : "9999", # some generic event uuid generated by DMI Plugin "event": { "push-change-update" : { "datastore-changes" : { {
} } } |
...
Data similar to the below needs to be reflected in the related cmhandle data model
{ "subscriptions" : { "running" : { # 'local' ncmp subscription is required with the cmhandle - store subId separately? "passthrough-operational" : { "passthrough-running" : { } |
---|
The subscriptionId in the passthrough-* datastore subscription information represents the subscription created on the remote device.
...