Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 4 Next »

Extend inventory handling

CCSDK-3223 - Getting issue details... STATUS

Inventory of a device should not langer be handled as an independent list of equipment entries.

Problem to be solved:
* Inventory "treeview" requires consistent relations between different inventory modules data fields.
* Actually there is no verification of this structure and ODLUX Invetory treeview has "strange" output elements.

Solution implemented in data-provider:
* Interface changed to write all inventory items by one call
* Add new interface type DeviceInventory to data-provider yang
* If write is called the existing" List will be removed for device.
* data-provider is implementing a consistency check between single inventory elements.

data-provider model for inventory is "grouping inventory-entity".

The following elements contain information for building the odlux treeview:

leaf (Tree view key is bold)

Table column

Description

uuidName

Unique inventory id of this equipment, provided by network element

parent-uuidParentUnique (network element) inventory id of holder. 
Not existing or null parent-uuid are root elements.
tree-levelContainment LevelStarting with 0 .. ( 0 :root level)
list contained-holder
List of uuid of contained equipment.
iddatabaseIdnot used in read direction. Needs to be null.
node-idNodeId of devicenodeId to identify owner of inventory
  • No labels