netbox icon indicating copy to clipboard operation
netbox copied to clipboard

Rack (inner) depth

Open sieuwe opened this issue 3 years ago • 5 comments

NetBox version

v3.2.7

Feature type

Data model extension

Proposed functionality

Currently we have a width and height option for inner sizing of a rack. And the outer width and outer depth is also available. What we are missing is the possibility to add the inner depth.

Use case

There are different inner depths possible. Some hardware only fits from a certain depth.

Database changes

Depth field needs to be added

External dependencies

No response

sieuwe avatar Jul 25 '22 12:07 sieuwe

This is a good idea, but your FR needs much more detail.

  • What field(s) are you proposing be added to the rack model?
  • Do we want to allow specifying the measurement unit as we do for the outer depth?
  • Should the use of this field be limited by rack type?

jeremystretch avatar Jul 25 '22 12:07 jeremystretch

  • What field(s) are you proposing be added to the rack model? I'd suggest using 'inner depth' since that would clarify the use and make it not confusing when using depth and outer depth.
  • Do we want to allow specifying the measurement unit as we do for the outer depth? The same measurement unit could apply as for the outer depth.
  • Should the use of this field be limited by rack type? This applies to al rack types.

sieuwe avatar Jul 25 '22 12:07 sieuwe

This applies to al rack types.

What about a freestanding two-post frame?

jeremystretch avatar Jul 26 '22 15:07 jeremystretch

What about a freestanding two-post frame?

Overlooked that one. That shouldn't have an inner dimension, all the other types should have one.

sieuwe avatar Jul 27 '22 06:07 sieuwe

This applies to al rack types.

What about a freestanding two-post frame?

I've worked in many broom closets that have limited space behind the two-post frame (a wall). Inner depth could be relevant still and may simplify the model. (I don't suppose it's truly any different than an outer depth in this case but some people may want to standardize checking against equipment depth on one field.)

I've made the necessary additions needed to submit a pull request assuming it is OK to have a dedicated "inner_unit" field. Otherwise we'll need to potentially complicate UI design and checks on whether fields are defined (which is fine will just need more careful planning)

gellis713 avatar Aug 11 '22 15:08 gellis713

Inner depth as in rail-to-rail distance or door-to-door? I would personally like to have rail-to-rail tracked, and maybe even have a min/max rail depth added to the device types. We currently document that through custom properties, but did not script any validation yet...

Some manufacturers have that information documented ( https://i.dell.com/sites/csdocuments/Business_solutions_engineering-Docs_Documents/en/rail-rack-matrix.pdf ) and we rely on that as we have hundreds of sites across the country with no unique rack model...

Having all that information added would be a plus, and that would also help to revisit https://github.com/netbox-community/netbox/issues/1627 ?

AnythingOverIP avatar Aug 23 '22 15:08 AnythingOverIP

Inner depth as in rail-to-rail distance or door-to-door?

Rail-to-rail

Having all that information added would be a plus, and that would also help to revisit #1627?

Possibly, but it would be best to submit a new FR after this one has been implemented.

jeremystretch avatar Oct 19 '22 15:10 jeremystretch