Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for a tenant field on interfaces #3059

Closed
yarnocobussen opened this issue Apr 11, 2019 · 1 comment
Closed

Add support for a tenant field on interfaces #3059

yarnocobussen opened this issue Apr 11, 2019 · 1 comment

Comments

@yarnocobussen
Copy link

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

@jeremystretch
Copy link
Member

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

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants