search

ietf-ccamp-wg / ietf-network-inventory

3 stars 5 forks source link

Where to put the component list? #9

Closed italobusi closed 2 years ago

italobusi commented 2 years ago

Evaluate whether the component list shall be under the node (i.e., NE) or under the network

Note that equipment rooms and racks (see #8) do not belong to any NE

italobusi commented 2 years ago

If the component list is placed under the network with a leafref to the NE the component belongs to, it would be straightforward to retrieve the list of components of a given type within the whole network as well as within a given NE (using filters).

If the component list is placed under the NE, it would be straightforward to retrieve the list of components of a given type within a given NE (using filters) but it would require multiple queries to get the list of components of a given type within the whole network.

italobusi commented 2 years ago

Network Inventory weekly call (October 6, 2021)

Jeff the master of the model should the "node" and related information.

Fabio: the network is quite big so you can get a lot of components within the network. If the component list is placed under the node it will smaller

Aihua: the issue may be due to the implementation efficiency

Need to get further investigation from the vendors if there are performance penalties with a model where the component list is defined under the network instead of under the node

italobusi commented 2 years ago

Network Inventory weekly call (October 13, 2021)

Jeff: OSS people prefer to have the list of component under the node and not under the network

Agreement to define the component list under the node for the -00 and to keep the option open for further discussion/investigation

italobusi commented 2 years ago

It may be worthwhile to check if it is still possible to retrieve the list of components of a given type within the network using wildcard filters, something like {{restconf}}/data/ietf-network:network/network-id=network-id/ ietf-network:node/node-id=*/components?fields=component&filter=class=’component-type’

For further discussion after IETF 112

YuChaode commented 2 years ago

I wrote an email to the RESTCONF authors, one of them replied that the filtering of list on the server side is not defined in standard. The usage of filter parameter in this URL is not correct. I think maybe we need to define a RPC operation to do the filtering.

italobusi commented 2 years ago

The component list has been agreed to be under the network-element