This was spun off from #180, which introduced rack type and rail-to-rail width.
Rack/cabinet width and depth is defined in either millimeters or inches, depending on the manufacturer. We have three options for handling this.
We could simply store a 24" wide cabinet as 610mm, and a 30" wide cabinet as 762mm, for example. This would require displaying both metric and imperial units to the user.
This would entail adding three fields to the Rack model:
This option forces the user to select from a static list of common rack widths and depths. For example, the list of rack widths might look like this:
Obviously, it would be impractical to include _all_ possible values, but this might be an acceptable solution if users are satisfied with choosing the options nearest to the actual dimensions.
This link has some examples of varying rack dimensions: http://www.42u.com/42U-cabinets.htm
My vote is for Option C - with administratively defined rack sizes, like a template. As an example, we make extensive use of Class C racks, which are generally externally oversized compared to typical.
Vote Option C, although perhaps with the flexibility Django gives, you might be able to make the rack types customizable from default in the backend for superuser access only? Then if anyone did need to add anything non-standard they could.
Is it possible to add 10'' wide racks, sometime used in SOHO etc ?
Such as: http://www.netshop.co.uk/product/170/mpe08f
Today only 19'' and 23'' is supported
@trikinov Never seen that before. What would you use it for?
Used in Europe for smaller offices and homes, for patchpanel, switch, small routers, TV distribution etc etc. Allows for smaller racks / cabinets in apartments etc..
Most helpful comment
Used in Europe for smaller offices and homes, for patchpanel, switch, small routers, TV distribution etc etc. Allows for smaller racks / cabinets in apartments etc..