UX Inventory

User documentation

The application offers basic inventory management of devices supporting ONF-TR-512.

In inventory basically serial-numbers and manufacturer details are displayed according to the containment of the equipment.

Test environment

This app gets information from SDN-R database in a generalized form. Specific Devicemanager needs to map the information from specific device model into the database from.

Devicemanagers prepared for inventory are ONF12, ONF14, Openroadm, Openroadm71

For test purpose simulators can be used as provided in the OAM CSIT tests: 

• Docker container from here: https://hub.docker.com/search?q=hightec%2Fnts
• Instructions how to start can be found in [sdnc/oam.git] / csit / plans / sdnr / setup.sh in script nts_networkfunctions_launch
• Netconserversimulator ONF12 

Running SDNR see here: SDN-R on docker-compose

Planning

Description for ONAP Frankfurt.

Extension planned for ONAP Guilin: ODLUX Inventory enhancement with treeview

Specification

The graphical user interface has a Table view and Tree view.

Table View

The table view implements the common ux-framework-table supporting sorting, filtering and pagination on the server.

The view shows the below fields.

1. Node Name
2. Manufacturer
3. Parent
4. Name
5. Serial
6. Version
7. Date
8. Description
9. Part Type Id
10. Model Identifier
11. Type
12. Containment Level

Reload Button: Reloads/Refresh the Inventory

By right-click on the rowdata, navigation to the tree view is available by context menu 'View in Treeview',

which displays the tree view.

Tree View

The Tree View shows the below fields

1. Node Name
2. Required
3. Host
4. Port
5. Core Model
6. Type

Only the Connected devices are available in this Tree View.

When clicked on the rowdata, it navigates to the Tree view of that particular row element which by default shows the root element in the tree view.

The search is also available where you can search for the particular name.

Behaviour

The inventory is loaded or refreshed during startup phase into the database.

A change of the inventory for a mountpoint would be added to the existing modules during next startup.

The Inventory data is not removed if network element is unmounted or deleted.

The implementation is rudimental, because ONAP DCAE should be used for inventory if fully available.

Data Provider

The inventory data is stored in an ElasticSearch database. A REST-API to access the values is provided by the Data-Provider.

To get the inventory list: read-inventory-list

The inventory is loaded or refreshed during startup phase into the database.

The Inventory data is not removed if network element is unmounted or deleted.