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

Enable creation of topology maps for PDUs and Console connections #78

Closed
candlerb opened this issue Jun 28, 2016 · 1 comment
Closed
Labels
status: accepted This issue has been accepted for implementation

Comments

@candlerb
Copy link
Contributor

It could be interesting (maybe even useful) to visualise PDU and Console connections, even if they are only just star topologies. It would at least let you see which boxes are not served.

Simple solution: add checkboxes in the Map definition for which types of connection to show - and use different edge colours, in case displaying multiple types in the same diagram.

Aside: filtering by Device Role, rather than regexps of device name, might be simpler.

@mdlayher mdlayher changed the title [Feature] Topology maps for PDUs and Console connections Enable creation of topology maps for PDUs and Console connections Jun 30, 2016
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Jan 26, 2018
@jeremystretch
Copy link
Member

It would at least let you see which boxes are not served.

This is better handled by validation reports today.

Simple solution: add checkboxes in the Map definition for which types of connection to show - and use different edge colours, in case displaying multiple types in the same diagram.

Trying to incorporate all types of connections in a single map isn't going to work well. Each map can only have one type.

Aside: filtering by Device Role, rather than regexps of device name, might be simpler.

It would, but it would also be much less flexible. Sometimes we only want to include a subset of a type of devices (e.g. the first rack or two in a site).

@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 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
Projects
None yet
Development

No branches or pull requests

3 participants