References
Jira |
---|
server | ONAP 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 | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1065 |
---|
|
...
# | 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. All NCMP notifications to be published on the public cm-events topic by default regardless of data type, notification type or datastore the change came from. This topics acts as the TBAC_ALL topic.
cm-events topic name should be configurable in deployment settings. Future : In future NCMP shall publish the notification based on TBAC where the notification is published on the appropriate target group topic cm-events[-<target-group-name>] matching the target group(s) the data type(s) is associated with. Not in scope of this story.
|
---|
3 | Handle unknown event schemas | Wrap event? | Unsupported for now. Thrown exception and log error. |
---|
Event Flow Sketch
![](/download/attachments/137200699/Notif-flow.jpg?version=1&modificationDate=1659399565000&api=v2)
CM Event Specification Outline
...
Data similar to the below needs to be reflected in the related cmhandle data model
{ "cmhandleId" : <cmhandle-id> "subscriptions" : { "operational" : { # 'local' ncmp subscription is required with the cmhandle - store separately? "administrativeState" : "active", "datastore-xpath-filter" : <xpath-filter> }, "running" : { # 'local' ncmp subscription is required with the cmhandle - store subId separately? "administrativeState" : "active", "datastore-xpath-filter" : <xpath-filter> }, "passthrough-operational" : { "administrativeState" : "updating", # if 'updating' then block/queue new sub's until 'active' "subscriptionId" : "cc77765sddf" , "datastore-xpath-filter" : <xpath-filter> }, "passthrough-running" : { "administrativeState" : "active", "subscriptionId" : <sub-id-of-device">, "datastore-xpath-filter" : <xpath-filter> } } } |
---|
The subscriptionId in the passthrough-* datastore subscription information represents the subscription created on the remote device.
...