| Table of Contents |
|---|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
# | 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 Message. | Existing channel or channel owned by NCMP/DMI | Vishal Varvate to provide the topic details. | ||||||||
| 3 | How do we retreive the relevant information from the CM VES Message
| Only fields that seem to suggest to have these info. are.
Related work in ONAP suggests this possible alternative schema: So wanted to confirm if measurements.measurement-type-instance-reference is xpath? | The fields which are of importance are :
CM VES related details present in CM handling guide
Vishal Varvate to provide in few examples of the CM VES messages. More information is present in the meetings recording. | ||||||||
| 4 | - Is CMNotify Message same as CM VES Message and notify more about this if this is relevant. |
| Yes. CMNotify and CM VES message are the same. |
...
- 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.
Meetings
| # | Participants | Recording |
|---|---|---|
| 1 |