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

Swap Terminating Ends of Cable #4890

Closed
iunderwood opened this issue Jul 23, 2020 · 10 comments
Closed

Swap Terminating Ends of Cable #4890

iunderwood opened this issue Jul 23, 2020 · 10 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application

Comments

@iunderwood
Copy link

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.8

Proposed Functionality

Add the capability to swap the A and Z end of a terminating cable.

Use Case

Connecting two devices together is great, but it would be nice to be able to swap the A and Z ends of a connection for the presentation of data uniformity.

For instance, when I build out a cable plant from an IDF to an MDF, I might build that cable out starting from a point in my IDF, and terminating that in my MDF. That makes the A end in the IDF, when it's really in the MDF. It would be handy to just swap the ends without having to delete and rebuilt the whole cable.

Database Changes

None that I am aware of.

External Dependencies

None that I am aware of.

@jeremystretch
Copy link
Member

Cables do not imply any direction: there are A and B ends, however these are arbitrary designations and exist as unique values solely to accommodate two terminations. The NetBox UI intentionally does not reveal to the user which end of a cable receives which designation.

@iunderwood
Copy link
Author

The observation of the A and B ends comes up in the cable list.

I found I built some cables starting in one of my IDFs to the MDF in question and some in the other direction. It would be nice to make these more uniform without having to rebuild the cable.

It is not a high-priority feature request.

@jeremystretch
Copy link
Member

The observation of the A and B ends comes up in the cable list.

That's true, but again, these don't indicate a particular direction. For instance, the Cable model could just as easily use an alternate approach where up to two terminations are assigned to a cable, as opposed using discrete fields on the model. In such a case, we'd still likely label the columns "A" and "B" just to differentiate between them. (I'm not suggesting we're going to do this in the future, but it's a possibility.)

@jeremystretch jeremystretch added status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application labels Jul 24, 2020
@wols
Copy link

wols commented Jul 26, 2020

This is a nice feature and I see two use cases:

  • a form of consitend documentation (@iunderwood: A is MDF, B is IDF ever)
  • users - like me - can map the signal direction (A: source, B: destination)
    -- I have a lot of cables between IN/OUT interfaces

@cpmills1975
Copy link
Contributor

IT tends to attract people with certain diverse characteristics.

I've seen people get quite upset at others for using the switch as the A end when it should have been the server or vice versa. Providing a simple means to swap ends would serve to placate some emotions!

@iunderwood
Copy link
Author

@cpmills1975 - Never underestimate how much someone can be affected by their CDO.

@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Aug 18, 2020
@jeremystretch
Copy link
Member

Blocked by #4900

@cpmills1975
Copy link
Contributor

Is this still blocked?

@jeremystretch jeremystretch removed the status: blocked Another issue or external requirement is preventing implementation label Mar 25, 2021
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 21, 2021
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jul 21, 2021
@github-actions
Copy link
Contributor

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants