Versions Compared

Version Old Version 48 New Version 49
Changes made by

Priyank Maheshwari

Priyank Maheshwari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#IssueNotesDecision
1List scenariosNeed to clarify scenariosRefer to Internal study
2Topicswhat 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.

3Handle unknown event schemasWrap event?Unsupported for now.  Thrown exception and log error.
4Event 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.


5CM Avc Subscriptions Event StructureCm 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.
6E2E Slicing needs to persist the dataWe need to check if we need to persist the data in flow-point #5 (Also depends on question #4)

Event Flow Overview


CM Event Specification Outline

...