...
| # | 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. We have add/remove and attribute-value changes(AVCs) . A&AI supports add/remove part. Need to check for AVCs. | |
| 5 | CM Avc Subscriptions Event Structure | Cm Subscription Event schema is been dictated by ORAN-DME (onap component which dictates event schema) so NCMP shall adhere to the schema. | We have to make up something similar( since this schema may/ may not be ready yet ) and check with Kieran on details here. |
| 6 | E2E Slicing needs to persist the data | We need to check if we need to persist the data in flow-point #5 (Also depends on question #4) | |
| 7 | Scope of the notifications ? | Need to check if these are only AVCs ( as the schema name suggests) Or CRUD or both. |
Event Flow Overview
CM Event Specification Outline
...