portrayal.dev
Portrayal is the source of truth for the physical facts; a DCIM is one consumer of them.
This is what spec/tools/portrayal/dcim_export.py writes at build time, in the
schema shared by netbox-community/devicetype-library and
nautobot/devicetype-library. One device type per SKU, so an AC front-to-back
and a DC back-to-front are separate entries with their own part numbers and images.
A NOS vendor that lists a box exports it again under its own name, with its own part numbers
and interface names: the same UfiSpace switch is UfiSpace/S9510-28DC-BN0B as its
maker sells it and Arrcus/S9510-28DC-BN0B as Arrcus sells it with ArcOS. Both
describe one copy of the metal, which is how NetBox and Nautobot file a disaggregated box.
Shown here is one device type. The bundle carries more than the page can show: module types,
rendered images, and fibre-maps/ — which front port of a fibre cassette reaches
which fibre of its trunk. That last one has no home in either library's YAML
(netbox#20564 made the front-to-rear link a bidirectional M2M, and the front-port
entry is {name, type, positions} with additionalProperties: false), so it
ships beside the type as a flat row list and travels with both targets.
loading…