starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Extend rack model to define outer width and depth #347

New Issue
Closed
opened 2025-12-29 16:21:07 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:21:07 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (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.

Originally created by @jeremystretch on GitHub (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.
adam added the status: acceptedtype: feature labels 2025-12-29 16:21:07 +01:00
adam closed this issue 2025-12-29 16:21:08 +01:00
adam commented 2025-12-29 16:21:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2016):

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

@jeremystretch commented on GitHub (Aug 10, 2016): This link has some examples of varying rack dimensions: http://www.42u.com/42U-cabinets.htm
adam commented 2025-12-29 16:21:08 +01:00
Author
Owner
Copy Link

@LukeDRussell commented on GitHub (Aug 10, 2016):

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.

@LukeDRussell commented on GitHub (Aug 10, 2016): 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.
adam commented 2025-12-29 16:21:08 +01:00
Author
Owner
Copy Link

@iamdadmin commented on GitHub (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.

@iamdadmin commented on GitHub (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.
adam commented 2025-12-29 16:21:08 +01:00
Author
Owner
Copy Link

@trikinov commented on GitHub (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

@trikinov commented on GitHub (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
adam commented 2025-12-29 16:21:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2016):

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

@jeremystretch commented on GitHub (Dec 21, 2016): @trikinov Never seen that before. What would you use it for?
adam commented 2025-12-29 16:21:09 +01:00
Author
Owner
Copy Link

@trikinov commented on GitHub (Dec 21, 2016):

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

@trikinov commented on GitHub (Dec 21, 2016): 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..
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#347
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?