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

Racks with units starting > 1 #12175

Closed
bebehei opened this issue Apr 5, 2023 · 2 comments
Closed

Racks with units starting > 1 #12175

bebehei opened this issue Apr 5, 2023 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@bebehei
Copy link

bebehei commented Apr 5, 2023

NetBox version

87e7cc4867d1 (v3.4.6)

Feature type

Data model extension

Proposed functionality

Currently, it is possible to assign a rack an arbitrary number of height units (usually 42 or 47). The starting point is fixed to 1, so all Devices in this Rack are located in RU {1..Y}.

This GitHub issue requests, that the starting point does not start hard coded from 1.

Use case

If you rent a quarter half/quarter/third rack, the starting point is not fixed necessarily fixed to Rack Unit 1. To talk to remote hands, this is quite confusing.

Current possible workarounds:

  • You could currently work around by creating a full rack and assigning Rack Reservations.
    • CON: This will falsely blow up the actual space utilisation of your rack. (e.g. quarter rack used with 2 Rack units displays 80% Rack Usage, while actually only 10% are used.)
  • Assign the rack the actual height and use instead of 41-60 the units 1-20.
    • CON: You have to convert this when talking to remote hands (error prone).
    • CON: Rack Photos show the actual rack unit and not the virtual unit
  • Tenancy should be a possibilty, but I haven't found anything to work around this with tenancy.

Database changes

No response

External dependencies

No response

@bebehei bebehei added the type: feature Introduction of new functionality to the application label Apr 5, 2023
@jeremystretch jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Apr 6, 2023
@jeremystretch
Copy link
Member

jeremystretch commented May 4, 2023

It sounds like adding a starting_unit integer field (defaulting to 1) to the Rack model would suffice. We'd no doubt have to dig through a lot of logic that assumes a starting unit of 1, but it should be feasible.

@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels May 4, 2023
@jeremystretch jeremystretch added this to the v3.6 milestone May 5, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels May 5, 2023
@arthanson arthanson self-assigned this May 31, 2023
@bebehei
Copy link
Author

bebehei commented Jun 23, 2023

Thank you all for adding this feature!

jeremystretch added a commit that referenced this issue Aug 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
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

3 participants