-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend rack model to define outer width and depth #450
Comments
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 ? 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.. |
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.
Option A: Store dimensions in millimeters only
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.
Option B: Store the unit along with the dimensions
This would entail adding three fields to the Rack model:
Option C: Define a list of standard widths and depths
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.
The text was updated successfully, but these errors were encountered: