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

Rack U numbering from top to bottom #191

Closed
yasa1987 opened this issue Jul 5, 2016 · 2 comments
Closed

Rack U numbering from top to bottom #191

yasa1987 opened this issue Jul 5, 2016 · 2 comments
Assignees
Milestone

Comments

@yasa1987
Copy link

yasa1987 commented Jul 5, 2016

Hello, in all our datacenters we are using Knurr racks and U numbering is from top to bottom : U01 is at top of rack and U41 is at rack bottom. In NetBox it's inverted.
Would it be possible to have an option to invert that to have U01 at top ? A 9U device starting at U02 will still end on U10 like now.

@jeremystretch jeremystretch added the type: feature Introduction of new functionality to the application label Jul 5, 2016
@jeremystretch
Copy link
Member

jeremystretch commented Jul 5, 2016

This would require a new boolean field on the Rack model, indicating the direction of increment (keeping bottom-to-top as the default). Rack elevations should be simple to flip upside down. I think the most confusing aspect is the treatment of multi-U devices.

Currently, multi-U devices are "attached" to the lowest-numbered RU that they occupy, which is also the physically lowest RU. In a top-to-bottom numbering scheme, this would be the physically highest RU. It should be fine if we're very clear in the documentation to always use the lowest numbered RU, but might still lead to confusion.

@yasa1987
Copy link
Author

yasa1987 commented Jul 6, 2016

Displaying something like "U2 to U10" in "Position" field of device instead just the starting U should remove any kind of confusion. By the way it would allow to remove positions that are impossible to start at regarding device's height.

@jeremystretch jeremystretch added new feature and removed type: feature Introduction of new functionality to the application labels Jul 13, 2016
@jeremystretch jeremystretch self-assigned this Oct 28, 2016
@jeremystretch jeremystretch added this to the v1.7 milestone Oct 28, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants