Skip to content
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

Closed
jeremystretch opened this issue Aug 10, 2016 · 6 comments
Closed

Extend rack model to define outer width and depth #450

jeremystretch opened this issue Aug 10, 2016 · 6 comments
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@jeremystretch
Copy link
Member

jeremystretch commented Aug 10, 2016

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:

  • outer_width
  • outer_depth
  • outer_unit

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:

  • Metric
    • 600mm
    • 750mm
    • 800mm
  • Imperial
    • 24"
    • 30"

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.

@jeremystretch jeremystretch added the type: feature Introduction of new functionality to the application label Aug 10, 2016
@jeremystretch
Copy link
Member Author

This link has some examples of varying rack dimensions: http://www.42u.com/42U-cabinets.htm

@LukeDRussell
Copy link

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.

@iamdadmin
Copy link

iamdadmin commented Sep 1, 2016

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.

@trikinov
Copy link

trikinov commented Dec 21, 2016

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

@jeremystretch
Copy link
Member Author

@trikinov Never seen that before. What would you use it for?

@trikinov
Copy link

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..

@jeremystretch jeremystretch modified the milestone: v2.1 Jun 9, 2017
@jeremystretch jeremystretch removed this from the v2.1 milestone Jun 23, 2017
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Jan 26, 2018
@jeremystretch jeremystretch added this to the v2.5 milestone Aug 3, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants