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 support for a tenant field on interfaces #2511

New Issue
Closed
opened 2025-12-29 18:19:30 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:19:30 +01:00
Owner
Copy Link

Originally created by @yarnocobussen on GitHub (Apr 11, 2019).

Environment

  • Python version: 3.5.6
  • NetBox version: 2.5.10

Proposed Functionality

Adding support for a tenant field on interfaces for the purpose of tenant administration.

Use Case

A tenant can use an interface on a device owned by another tenant. For purposes such as maintenance announcements, monitoring and (traffic) billing on the tenant level, it is useful to connect ownership information to the interface.

Example:
A datacenter provider is the tenant for an access switch. A customer with rackspace in the datacenter is assigned a (virtual) interface on that switch for internet connectivity. For purposes mentioned earlier, the tenancy of this interface needs to be known.

When reviewing this request, consider that gathering this information via other means is inconsistent and may not always be possible. It would require an indirect relation to something owned by the customer tenant, such as a cable, address within a prefix or a VLAN. Those may not exist and may not be owned by that specific tenant either. Therefore, my conclusion was to request this additional field.

Database Changes

This field already exists for other objects and I can't think of any conflicts with other functionality in Netbox. I guess it would simply mean adding a single column to the interface table?

External Dependencies

N/A

Originally created by @yarnocobussen on GitHub (Apr 11, 2019). ### Environment * Python version: 3.5.6 * NetBox version: 2.5.10 ### Proposed Functionality Adding support for a tenant field on interfaces for the purpose of tenant administration. ### Use Case A tenant can use an interface on a device owned by another tenant. For purposes such as maintenance announcements, monitoring and (traffic) billing on the tenant level, it is useful to connect ownership information to the interface. Example: A datacenter provider is the tenant for an access switch. A customer with rackspace in the datacenter is assigned a (virtual) interface on that switch for internet connectivity. For purposes mentioned earlier, the tenancy of this interface needs to be known. When reviewing this request, consider that gathering this information via other means is inconsistent and may not always be possible. It would require an indirect relation to something owned by the customer tenant, such as a cable, address within a prefix or a VLAN. Those may not exist and may not be owned by that specific tenant either. Therefore, my conclusion was to request this additional field. ### Database Changes This field already exists for other objects and I can't think of any conflicts with other functionality in Netbox. I guess it would simply mean adding a single column to the interface table? ### External Dependencies N/A
adam closed this issue 2025-12-29 18:19:30 +01:00
adam commented 2025-12-29 18:19:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 11, 2019):

NetBox only supports tenancy assignment at the device level. Tenancy would be inferred from the device connected to the interface.

@jeremystretch commented on GitHub (Apr 11, 2019): NetBox only supports tenancy assignment at the device level. Tenancy would be inferred from the device connected to the interface.
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#2511
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?