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

Add Tenant to Cable Model #5051

New Issue
Closed
opened 2025-12-29 19:23:33 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:23:33 +01:00
Owner
Copy Link

Originally created by @nbogle on GitHub (Jul 7, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.8

Feature type

New functionality

Proposed functionality

I would like to see the ability to assign cables in Netbox to a tenant.

This would involve adding a link between the tenancy.tenant model and the dcim.Cable model.

Use case

I use Netbox in a datacenter setting, and I would like to be able to assign cross connections (in netbox as cables) to tenants, so you can see all cross connects a tenant might have, or what cables were put in for which client.

Database changes

I don't believe this would require any database changes

External dependencies

No.

Originally created by @nbogle on GitHub (Jul 7, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.8 ### Feature type New functionality ### Proposed functionality I would like to see the ability to assign cables in Netbox to a tenant. This would involve adding a link between the tenancy.tenant model and the dcim.Cable model. ### Use case I use Netbox in a datacenter setting, and I would like to be able to assign cross connections (in netbox as cables) to tenants, so you can see all cross connects a tenant might have, or what cables were put in for which client. ### Database changes I don't believe this would require any database changes ### External dependencies No.
adam added the status: acceptedtype: feature labels 2025-12-29 19:23:33 +01:00
adam closed this issue 2025-12-29 19:23:34 +01:00
adam commented 2025-12-29 19:23:34 +01:00
Author
Owner
Copy Link

@eronlloyd commented on GitHub (Jul 18, 2021):

Strongly agree. We are a service provider with many leased lines (dark and lit) dedicated to customers and peers. Knowing at the cable level what's assigned to specific tenants would be very helpful for planning and auditing.

@eronlloyd commented on GitHub (Jul 18, 2021): Strongly agree. We are a service provider with many leased lines (dark and lit) dedicated to customers and peers. Knowing at the cable level what's assigned to specific tenants would be very helpful for planning and auditing.
adam commented 2025-12-29 19:23:34 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 29, 2021):

This would be a welcome add to associate and track cross connects to tenants.

@bellwood commented on GitHub (Jul 29, 2021): This would be a welcome add to associate and track cross connects to tenants.
adam commented 2025-12-29 19:23:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

Somewhat related to #5140.

I'm not sure it makes sense to associate a cable with a tenant directly, rather than inferring from the tenant which owns either of its endpoints. Though that raises the question: if a cable connects devices belong to two different tenants, which one owns the cable?

@jeremystretch commented on GitHub (Jul 29, 2021): Somewhat related to #5140. I'm not sure it makes sense to associate a cable with a tenant directly, rather than inferring from the tenant which owns either of its endpoints. Though that raises the question: if a cable connects devices belong to two different tenants, which one owns the cable?
adam commented 2025-12-29 19:23:35 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 29, 2021):

I would proffer whomever installs the cable would be the owner. That could either be the A tenant, the Z tenant or perhaps the facility making the connection.

@bellwood commented on GitHub (Jul 29, 2021): I would proffer whomever installs the cable would be the owner. That could either be the A tenant, the Z tenant or perhaps the facility making the connection.
adam commented 2025-12-29 19:23:35 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 29, 2021):

I suppose, too, for our intended purposes of tracking cross connects, those could be entered as circuits, which do support tenants.

@bellwood commented on GitHub (Jul 29, 2021): I suppose, too, for our intended purposes of tracking cross connects, those could be entered as circuits, which do support tenants.
adam commented 2025-12-29 19:23:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

I'm not really opposed to adding a tenant relationship on the cable model. I think it's perhaps suboptimal, but as discussed in #5140 there are other issues with filtering by tenancy of related objects.

@jeremystretch commented on GitHub (Jul 29, 2021): I'm not really opposed to adding a tenant relationship on the cable model. I think it's perhaps suboptimal, but as discussed in #5140 there are other issues with filtering by tenancy of related objects.
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#5051
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?