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

Add support for reserving rack space #22

New Issue
Closed
opened 2025-12-29 15:29:54 +01:00 by adam · 2 comments
adam commented 2025-12-29 15:29:54 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 27, 2016).

Currently, space within a rack can only be either unoccupied or occupied (having been consumed by a device). It would be helpful to allow users to reserve arbitrary swaths of rack space with a comment indicating its intended use. This could also be used to designate unallocated rack space (for instance, because the rack has been damaged).

Originally created by @jeremystretch on GitHub (Jun 27, 2016). Currently, space within a rack can only be either unoccupied or occupied (having been consumed by a device). It would be helpful to allow users to reserve arbitrary swaths of rack space with a comment indicating its intended use. This could also be used to designate unallocated rack space (for instance, because the rack has been damaged).
adam closed this issue 2025-12-29 15:29:55 +01:00
adam commented 2025-12-29 15:29:56 +01:00
Author
Owner
Copy Link

@colawebrunner commented on GitHub (Jul 9, 2016):

Think this would be a great feature, as working for an MSP we want to be able to reserve racks/rack space for potential customers.

@colawebrunner commented on GitHub (Jul 9, 2016): Think this would be a great feature, as working for an MSP we want to be able to reserve racks/rack space for potential customers.
adam commented 2025-12-29 15:29:56 +01:00
Author
Owner
Copy Link

@MaXFalstein commented on GitHub (Jul 9, 2016):

I think this feature should be worked on sooner than some of the other "issues" raised.

Support for rack space reservation will enable blanking and adding of future network provisions in rack or in dedicated network racks.

@MaXFalstein commented on GitHub (Jul 9, 2016): I think this feature should be worked on sooner than some of the other "issues" raised. Support for rack space reservation will enable blanking and adding of future network provisions in rack or in dedicated network racks.
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
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#22
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?