/
CPS-2675 OAM/SDNC/NCMP CM Stack Use Case

CPS-2675 OAM/SDNC/NCMP CM Stack Use Case

References

 

8.61. Service: VES Event Listener 7.2.1 — onap master documentation

VES Class Definition - part 2 — onap master documentation

VES 7.2 - ONAP Wiki - Confluence

Summary

Goal:

View topology based on a CM data export

Components:

OAM - Operation and Maintenance. According to the O-RAN OAM Architecture and the O-RAN OAM Interface Specification, the SMO implements a NETCONF Client for configuration and a HTTP/REST/VES server for receiving all kind of events in VES format.

DU and RU APPs interacts with OAM on the O1 interface for configuration, alarms and performance management.

SDNC - Software Defined Network Controller. A global network controller which manages, assigns and provisions network resources.

 

 

 

Open Questions

Question

Notes

Decision

Question

Notes

Decision

1

What to look for in the VES Event?

event.commonEventHeader.sourceName ?? to get the node name ?

Yes

2

What is the schema for the VES Event?

John will let me know.

 

3

How to ignore other events?

 

 

4

What is the topic ?

unauthenticated.VES_PNFREG_OUTPUT ??
Note : I see event for only one device on this topic.

unauthenticated.VES_O1_NOTIFY_PNF_REGISTRATION_OUTPUT and unauthenticated.VES_PNFREG_OUTPUT

5

Which datastore to be used in NCMP ?

passthrough-running → content=config

 

passthrough-operational → content=all

 

6

Do we need to use the options , include-descendants field in NCMP. and what does it correspond to in the SDNC side?

 

 

7

Any specific model to be used for the demo ?

for now we onboarded a simple bookstore model.

But can build examples around that if any specific model needs to be used.

 

8

Are there any events which can show the change in configuration in SDNC and can be listened back by NCMP to keep the cached data upto date.

 

 

 

Assumptions

Assumption

Note

Decision

Assumption

Note

Decision

1

 

 

 

2

 

 

 

3

 

 

 

 

Issues/Decisions

Issue

Notes

Decision

Issue

Notes

Decision

1

Onboard bookstores yang model.

 

@Priyank Maheshwari Able to onboard.

2

Register the device using the discovery process in NCMP.

 

@Priyank Maheshwari Done

3

Read the data from the device.

from parent node or child node or both ?

@Priyank Maheshwari Able to read from root and with filters as well.

4

Write the data to the device.

from parent node or child node or both ?

@Priyank Maheshwari Able to create and update.

5

Data sync for pynts-o-du-o1 device.

 

Cause : Root data endpoint for pynts-o-du-o1 is not working as expected.

6

Data validation during passthrough operations

 

@Priyank Maheshwari CPS-NCMP do not validates the data for passthrough operations.

But if we use the CPS cache then the validation is done. ( If we use the datasync flag )

 

Analysis

 

Use Case / Flow

Status

Comments

Use Case / Flow

Status

Comments

1

ONAP DMI Plugin connecting with SDNC

 

Verified using Manual Device Registration from ONAP-DMI-PLUGIN.

2

ONAP DMI Plugin listening to VES event for device registration

this is to automate the device registration.

 

3

Data Synchronization at NCMP side

Partially Failing
( works for 1 out of 2 devices )

in scope ??

 

4

Reading data from devices using CPS-NCMP

?

 

5

Writing data to devices using CPS-NCMP

?

 

Related content