Skip to content

Allow filtering cables by tenant of connected device #3021

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

Closed
xonacs opened this issue Mar 22, 2019 · 2 comments · Fixed by #3887
Closed

Allow filtering cables by tenant of connected device #3021

xonacs opened this issue Mar 22, 2019 · 2 comments · Fixed by #3887
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@xonacs
Copy link

xonacs commented Mar 22, 2019

Environment

  • Python version: 3.6.6
  • NetBox version: 2.5.8

Proposed Functionality

Currently, a tenant's device might be linked to another tenant or provider device via one ore more cables. It is not possible to see easily identify all connections across tenants. Therefore Cables need to have a tenant ownership or else there needs to be a view that shows all cables related to a tenant.

Use Case

As a data center and that uses Netbox we maintain a full list of equipment, customer and own. Currently it is possible to assign an ID to all services provided to a customer (tenant). Prior to the introduction of cables in Netbox, a Circuit (type: "Uplink") was used to indicate the physical link providing the customer connectivity. The tenant of such an ID was the customer. This allows for a comprehensive view of everything a customer(tenant) has, i.e. all devices, racks, vlans, IPs, physical uplinks, circuits etc.

Having a cable that is assignable to a tenant or being able to filter all cables connecting to a tenant's device would restore this ability without having to resort to using Circuits (which is incorrect as it creates two cables when there would be one).

Database Changes

External Dependencies

@jeremystretch
Copy link
Member

There is no need to declare an explicit relationship to a tenant on the cable model, as the endpoints of a cable already have this association. (It also begs the question: who would own a cable connecting tenants A and B?)

It sounds like you want to be able to filter cables based on the tenant assigned to either end. If this is the case, please revise your FR to better capture the use case and remove the proposed relationship (or close this and open a new FR if you prefer).

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Mar 22, 2019
@xonacs
Copy link
Author

xonacs commented Mar 23, 2019

Updated FR, thanks.

@jeremystretch jeremystretch removed the status: revisions needed This issue requires additional information to be actionable label Mar 25, 2019
@jeremystretch jeremystretch changed the title Ownership of Cables / Tenant view Allow filtering cables by tenant of connected device Jun 24, 2019
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Oct 15, 2019
jeremystretch added a commit that referenced this issue Jan 13, 2020
Fixes #3021: Added tenancy filter for cables
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants