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

Have rack reservations count against utilization #2695

New Issue
Closed
opened 2025-12-29 18:21:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:10 +01:00
Owner
Copy Link

Originally created by @swerveshot on GitHub (Jun 26, 2019).

Environment

  • NetBox version: 2.6.1

Proposed Functionality

As a follow-up to issue #1311 where things were becoming a bit vague I'd like to request the following feature.

I would very much like to have RU reservations count against utilization.

Use Case

Having this feature in NetBox gives a user the ability to:

  • Make a rack appear as 100% utilized even if this only administratively. Think of use cases where a rack is limited by the maximum weight or power capacity before all the RUs are actually used.
  • Directly see from the rack overview page how much of a rack is utilized. Even if part of that utilization is a reservation.
Originally created by @swerveshot on GitHub (Jun 26, 2019). ### Environment * NetBox version: 2.6.1 ### Proposed Functionality As a follow-up to issue #1311 where things were becoming a bit vague I'd like to request the following feature. I would very much like to have RU reservations count against utilization. ### Use Case Having this feature in NetBox gives a user the ability to: * Make a rack appear as 100% utilized even if this only administratively. Think of use cases where a rack is limited by the maximum weight or power capacity before all the RUs are actually used. * Directly see from the rack overview page how much of a rack is utilized. Even if part of that utilization is a reservation.
adam added the status: acceptedtype: feature labels 2025-12-29 18:21:10 +01:00
adam closed this issue 2025-12-29 18:21:10 +01:00
adam commented 2025-12-29 18:21:11 +01:00
Author
Owner
Copy Link

@swerveshot commented on GitHub (Oct 2, 2019):

Nice one @jeremystretch! Thanks for implementing this enhancement. Just upgraded and it works perfectly.

@swerveshot commented on GitHub (Oct 2, 2019): Nice one @jeremystretch! Thanks for implementing this enhancement. Just upgraded and it works perfectly.
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#2695
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?