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 Tenant to Location Model #5131

New Issue
Closed
opened 2025-12-29 19:24:35 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:24:35 +01:00
Owner
Copy Link

Originally created by @sleepinggenius2 on GitHub (Aug 3, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.10

Feature type

Data model extension

Proposed functionality

Add a Tenant field to the existing Location model.

Use case

In a colocation environment, customers can be assigned their own cages, typically containing one or more racks, as well as other items, like power panels. It would be nice to be able to create a location to represent such a cage within a site and assign racks, power panels, devices, etc. to it, while also tracking the customer assigned to that location. Racks and devices can be assigned to a tenant today, but power panels cannot, and they can all be assigned to a location. Using a site to represent this situation is cumbersome, as a lot of the fields would need to be duplicated among the site objects and it doesn't really seem right conceptually.

Database changes

Add a Tenant field to the existing Location model.

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Aug 3, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.10 ### Feature type Data model extension ### Proposed functionality Add a *Tenant* field to the existing *Location* model. ### Use case In a colocation environment, customers can be assigned their own cages, typically containing one or more racks, as well as other items, like power panels. It would be nice to be able to create a location to represent such a cage within a site and assign racks, power panels, devices, etc. to it, while also tracking the customer assigned to that location. Racks and devices can be assigned to a tenant today, but power panels cannot, and they can all be assigned to a location. Using a site to represent this situation is cumbersome, as a lot of the fields would need to be duplicated among the site objects and it doesn't really seem right conceptually. ### Database changes Add a *Tenant* field to the existing *Location* model. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:24:35 +01:00
adam closed this issue 2025-12-29 19:24:35 +01:00
adam commented 2025-12-29 19:24:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 4, 2021):

We already have tenancy assignment for racks and sites. Seems like it would make sense to support locations as well.

@jeremystretch commented on GitHub (Aug 4, 2021): We already have tenancy assignment for racks and sites. Seems like it would make sense to support locations as well.
adam commented 2025-12-29 19:24:36 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Aug 6, 2021):

Let's add Region tenancy as well?

@sdktr commented on GitHub (Aug 6, 2021): Let's add Region tenancy as well?
adam commented 2025-12-29 19:24:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2021):

Regions and site groups exist above the site model in the hierarchy, and are intended to group sites. It would not make sense to assign tenants to these models. (This proposal is out of scope for this FR, anyway.)

@jeremystretch commented on GitHub (Aug 6, 2021): Regions and site groups exist above the site model in the hierarchy, and are intended to group sites. It would not make sense to assign tenants to these models. (This proposal is out of scope for this FR, anyway.)
adam commented 2025-12-29 19:24:37 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Sep 20, 2021):

Just found this FR when trying to add a tenant to a location...
Hope to get this soon :)

@jcralbino commented on GitHub (Sep 20, 2021): Just found this FR when trying to add a tenant to a location... Hope to get this soon :)
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#5131
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?