ietf-ivy-wg / network-inventory-yang

Other
0 stars 3 forks source link

Configuration Capability of Inventory Data Model #14

Open YuChaode opened 1 year ago

YuChaode commented 1 year ago
  1. The name of our current data model infers it supports retrieval function only, and currently, all the attributes defined in our data model are all read only. Will inventory data model support configuration for some attributes in the future? Or should these configurations be supported by some other data models?
  2. There could be some configuration requirement for NE/board/port name, location, description, alias, etc. An alternative way to support these configuration is configuring from network topology data model, but there are two things we need to consider more: (1) A NE/port could be multiple nodes/TPs in different layers of topology, it is not quite convenient to modify all the nodes/TPs. (2) Board object is not defined in network topology data model and there could be some other configuration requirement besides name, location, description, alias, E.G. board's working mode .etc.
  3. Another alternative way to support configuration function is configuring through ietf-hardware data model in RFC8348. But it is still not able to support configuration for equipment room, rack and NE, because hardware data model is a NE-level data model.
YuChaode commented 7 months ago

Analysis of attributes' configuration scenario.xlsx Discussion of configurations capabilities of inventory base model.pptx

The material discussed on the meeting at Nov.30th, 2023.