starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Rack Tenants #1690

New Issue
Closed
opened 2025-12-29 16:34:27 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:34:27 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Apr 23, 2018).

Issue type

[ X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.4.8
  • NetBox version: 2.3.3

Description

We are selling Colocation Space, 1/1 Racks, 1/2 Racks, 1/4 Racks and single Units. At the Moment we are facing a documentation problem in Netbox. We are creating for each customer a device and racking them into the rack but if we have to document the server setup with single servers, too we can't mount them on these Units because they are already in use. You can assign only a complete rack with a tenant.

Idea is that there is a tenant function 1:1 like the reservation function.
It would be create if there is a function to assign single or multiple Units to a tenant.

Originally created by @ghost on GitHub (Apr 23, 2018). ### Issue type [ X ] Feature request [ ] Bug report [ ] Documentation ### Environment * Python version: 3.4.8 * NetBox version: 2.3.3 ### Description We are selling Colocation Space, 1/1 Racks, 1/2 Racks, 1/4 Racks and single Units. At the Moment we are facing a documentation problem in Netbox. We are creating for each customer a device and racking them into the rack but if we have to document the server setup with single servers, too we can't mount them on these Units because they are already in use. You can assign only a complete rack with a tenant. Idea is that there is a tenant function 1:1 like the reservation function. It would be create if there is a function to assign single or multiple Units to a tenant.
adam closed this issue 2025-12-29 16:34:27 +01:00
adam commented 2025-12-29 16:34:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 23, 2018):

This would require substantial changes to the database schema as NetBox does not represent individual rack units as discrete objects. As an alternate solution, I suggest creating rack objects which represent only a portion of a real rack. For example, if Rack A123 is split in half between two tenants, create A123:1 and A123:2, and assign each to its respective tenant. It's not an ideal solution, but the value of implementing this relatively niche feature doesn't justify the development effort needed to rework the database scheme.

@jeremystretch commented on GitHub (Apr 23, 2018): This would require substantial changes to the database schema as NetBox does not represent individual rack units as discrete objects. As an alternate solution, I suggest creating rack objects which represent only a portion of a real rack. For example, if Rack A123 is split in half between two tenants, create A123:1 and A123:2, and assign each to its respective tenant. It's not an ideal solution, but the value of implementing this relatively niche feature doesn't justify the development effort needed to rework the database scheme.
adam commented 2025-12-29 16:34:28 +01:00
Author
Owner
Copy Link

@tobzsc commented on GitHub (Apr 24, 2018):

@jeremystretch Sad news... You are speaking about niche feature. How comes? Where do you have that information from that this may or may not be requested by other users?

@tobzsc commented on GitHub (Apr 24, 2018): @jeremystretch Sad news... You are speaking about niche feature. How comes? Where do you have that information from that this may or may not be requested by other users?
adam commented 2025-12-29 16:34:28 +01:00
Author
Owner
Copy Link

@tobzsc commented on GitHub (Apr 24, 2018):

@jeremystretch do you see a chance for a sponsoring here? We are really interested in such a feature.

@tobzsc commented on GitHub (Apr 24, 2018): @jeremystretch do you see a chance for a sponsoring here? We are really interested in such a feature.
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#1690
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?