Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 21 Next »

References

CPS-1407 - Getting issue details... STATUS

CM VES Message

https://wiki.onap.org/rest/gliffy/1.0/embeddedDiagrams/1a4a429c-8822-4663-be6c-c0c979bda49b.png?utm_medium=live&utm_source=confluence

Assumptions

Issues & Decisions

#

Issue

Notes

Decisions

1.

CM VES Message format schema.

Who will own it ?

In order to process the message DMI plugin / NCMP should be aware of the schema of the incoming message it is going to be consume.
2.Topic from where we will receive the CM VES MessageNeed topic info to listen to. (NCMP will have a listener configured to listen to the message)
3.Does CPS raise any special event after the events are updated in CPS DB ?

4Does CPS care about all the attributes in the CM VES Message. If not then we need to list down the attributes which CPS cares about.The CM update expected would be a change for the GNBDUFunction/nrCellDU/nrPCI ** or for the GNBCUFunction/NRCellCU/NRCellRelation/isHOAllowed . Need to confirm with the stakeholders.
5Do we need to persist the CM VES Message ?

6Any Performance requirements ? 

7

- Is CMNotify Message same as CM VES Message.



8How to get the cmHandle and the xpaths from the CM VES Messages.

9


Overview

  • DMI Plugin to receive CM VES Message from the upstream( VES Collector ?? ) via a REST call or some other method. ( or also can generate a VES message for testing)
  • DMI Plugin will publish the CM VES Message to a topic which is agreed ( or to be agreed)
  • NCMP will have a listener to the topic and process the CM VES message.
  • CM VES Message should be understood by NCMP.
  • NCMP will process the VES message and call the CPS Core APIs to update the CPS DB.



Sample VES Message : sample_ves_message.json


Analysis

  • Dataspace : NFP-Operational , Schema-Set : cps-ran-schema-model , Anchor : ran-network-simulation
  • Yang Resource : cps-ran-schema-model ( tree form : cps-ran-schema-model_tree.txt ) existing ran-schema will be used.
  • We need to have a defined channel/topic where the VES messages are present , and NCMP should be able to listen , interpret/process and call the relevant CPS-Core APIs in order to publish the changes in the CPS DB.


  • No labels