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

Reservation Of Servers or devices #7702

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

Originally created by @johnnyrf on GitHub (Mar 2, 2023).

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Hello thank you for your time. Not sure if any new updates have addressed my request. Would like to see a feature for The data center Manager to reserve a Devide ie, Server or Switch, PDU KVM or NIC for a user or group for a specific amount of time . Example if a rack has many mixed type servers 1U 2U Mini appliances etc, and a request is made for a 2U single socket server along with a PDU which is already labeled and identified on the rack Would be a nice feature to reserve this rack for a specific user or group for a specific duration. The "device Reservation section could include custom fields as well. The reason is non of my users require to reserve an entire rack, but rather 1 or 2 servers for 1 to 2-3 months. If this could be extended to all Devices would also be a nice feature.

Use case

It addresses the need to be a little more granular precise on the status, purpose and use of the server or device.

Database changes

Perhaps a database field indicating or labeled "Reservation" "Reservation Status" sub field "Res Device type"

External dependencies

Don think it would require any additional python modules, I think only database entry and proper relationships.

Originally created by @johnnyrf on GitHub (Mar 2, 2023). ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality Hello thank you for your time. Not sure if any new updates have addressed my request. Would like to see a feature for The data center Manager to reserve a Devide ie, Server or Switch, PDU KVM or NIC for a user or group for a specific amount of time . Example if a rack has many mixed type servers 1U 2U Mini appliances etc, and a request is made for a 2U single socket server along with a PDU which is already labeled and identified on the rack Would be a nice feature to reserve this rack for a specific user or group for a specific duration. The "device Reservation section could include custom fields as well. The reason is non of my users require to reserve an entire rack, but rather 1 or 2 servers for 1 to 2-3 months. If this could be extended to all Devices would also be a nice feature. ### Use case It addresses the need to be a little more granular precise on the status, purpose and use of the server or device. ### Database changes Perhaps a database field indicating or labeled "Reservation" "Reservation Status" sub field "Res Device type" ### External dependencies Don think it would require any additional python modules, I think only database entry and proper relationships.
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:27:14 +01:00
adam closed this issue 2025-12-29 20:27:14 +01:00
adam commented 2025-12-29 20:27:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 6, 2023):

NetBox already offers the ability to define rack reservations for arbitrary units, as well as the ability to designate specific devices as reserved. Can you explain why these abilities do not meet your needs?

@jeremystretch commented on GitHub (Mar 6, 2023): NetBox already offers the ability to define [rack reservations](https://docs.netbox.dev/en/stable/models/dcim/rackreservation/) for arbitrary units, as well as the ability to designate specific devices as reserved. Can you explain why these abilities do not meet your needs?
adam commented 2025-12-29 20:27:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

Closing as there's been no further response.

@jeremystretch commented on GitHub (Mar 16, 2023): Closing as there's been no further response.
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: revisions needed 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#7702
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?