ConfigDB and impact on SDN-R

Why ConfigDB?

The OOF-SON implementations and the wireless technology (wt) implementations on SDN-R using external database to store different kinds of information.

This page shows some of the current stored info and its visualization in dashboards.

With respect to ConfigDB the following questions should be answered:

1. What issue will a ConfigDB solve?

   1. It could act as "cache" for configuration data, so that other ONAP components do not need to request data directly from the network. Such concept potentially can reduce the number of active connections from ONAP to devices.

   2. more...

2. What data should be stored?

   1. The name already defines already the scope. Configuration data should be stored only. As a consequence network status data must inquired from network always.

   2. The configuration data are data of the network/devices not the data of the controller or other ONAP components.

   3. Open: What about important status data - e.g life cycle, operational status, alarm status, device capabilities, ...)?

3. Does ConfigDB store network actual or network target data?

   1. Both, there must be section to store the actual data and in the same format the target data, in order to view discrepancies in the network. Please see chapter 6.9 Application for Showing Aberrancies.

   2. The actual data is updated by controllers. The target data is updated by SO and ONAP design components.

4. Which schema is used to store the data?

   1. good question  → ConfigDB should differentiate technology agnostic data from technology specific data. 

      1. Examples for technology agnostic data: hardware inventory, software inventory - only those which are not stored in A&AI, device identifiers, device life cycle, neighbor relations

      2. Examples for technology specific data: frequencies, channel plans, interface capacities

@Joanna Xu @N.K. Shankaranarayanan @all: Please correct, update, comment, object, .....