Rack unit tenants #3616

Closed
opened 2025-12-29 18:30:11 +01:00 by adam · 2 comments
Owner

Originally created by @kmorin18 on GitHub (Apr 28, 2020).

Environment

N/A

Proposed Functionality

Extend the "tenant" feature on a "per U" basis.

Currently, the "tenant" feature only allows users to assign a tenant to a full cabinet.
It would be nice to be able to set tenant X in U's 1-20 in rack A.

A workaround is to set a reservation, but it makes it so the reservation feature can't be used.

Use Case

Allow users to set tenants on a "per rack unit" basis. Practical for data center colocation providers.

Database Changes

N/A

External Dependencies

N/A

Originally created by @kmorin18 on GitHub (Apr 28, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment N/A ### Proposed Functionality Extend the "tenant" feature on a "per U" basis. Currently, the "tenant" feature only allows users to assign a tenant to a full cabinet. It would be nice to be able to set tenant X in U's 1-20 in rack A. A workaround is to set a reservation, but it makes it so the reservation feature can't be used. ### Use Case Allow users to set tenants on a "per rack unit" basis. Practical for data center colocation providers. ### Database Changes N/A ### External Dependencies N/A
adam added the pending closure label 2025-12-29 18:30:11 +01:00
adam closed this issue 2025-12-29 18:30:11 +01:00
Author
Owner

@jeremystretch commented on GitHub (Apr 28, 2020):

Thank you for the suggestion, however this would be too stark a departure from the established data model. It is recommended to assign tenants to racks only when the entire rack belongs to the tenant; otherwise, the tenant assignment is done at the device level.

@jeremystretch commented on GitHub (Apr 28, 2020): Thank you for the suggestion, however this would be too stark a departure from the established data model. It is recommended to assign tenants to racks only when the entire rack belongs to the tenant; otherwise, the tenant assignment is done at the device level.
Author
Owner

@stale[bot] commented on GitHub (May 12, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (May 12, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3616