...
| # | 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. |
| 4 | Event Flow Overview (Flow 1 and 2 ) | We will need for ONAP specific solution for that and we need to check with E2E Slicing Team on how the DMI would receive the Network Changle Cm Notification ( via message bus or something else ) , how will it look.. etc etc. | |
| 5 | CM Avc Subscriptions Event Structure | Cm Subscription Event schema is been dictated by DME (onap component which dictates event schema) so NCMP shall adhere to the schema. |
Event Flow Overview
CM Event Specification Outline
...
The subscription may be different on the device if setting up a subscription toward different datastores. If the device only supports running datastore (non-NMDA) then all subscriptions are directed toward the running datastore regardless of whether passthrough-running or passthrough-operational is specified in the subscription. It would mean that the same notification would be sent twice but the eventSource would differ (passthrough-operational and passthrough-running). However, this is a concern for the dmi plugin only - not for NCMP.
Recordings
| Spike Review(Session-1) | Internal link |
|---|---|
| Spike Review(Session-2) | CPS-1065 _ Spike Review _ CM Data Change Notifications _ Subscriptions-20220825_084446-Meeting Recording.mp4 |