You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
The size of the object shown on the floor plan should come from the rack/device being added to the map. At the moment when you place a rack, it comes into the map as 24x36", even if the Rack's dimensions are specified as 19x6 (a 2 post rack for example)
The text was updated successfully, but these errors were encountered:
Something to discuss @tbotnz - what's your vision for handling non-racked devices? They don't have a true size construct in Netbox, and I know teams all handle them somewhat differently....
The two main ones I've seen:
Custom Fields
Fake Racks- i.e. build a custom "rack" the size of say... a CRAC- and then place a "device" within it, filling the unit.
The other option may be just to allow manual resize of the object if it's not a rack? Maybe an additonal custom_meta with "resizeable": true or similar?
@justin-davisibm I think for now we just allow non racled devices to have their width / depth changed on thr floorplan through dragging. Once netbox adds support on thr device type then we can update accordingly
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The size of the object shown on the floor plan should come from the rack/device being added to the map. At the moment when you place a rack, it comes into the map as 24x36", even if the Rack's dimensions are specified as 19x6 (a 2 post rack for example)
The text was updated successfully, but these errors were encountered: