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

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

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

Originally created by @candlerb on GitHub (Jun 28, 2016).

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.

Originally created by @candlerb on GitHub (Jun 28, 2016). 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.
adam added the status: accepted label 2025-12-29 15:30:42 +01:00
adam closed this issue 2025-12-29 15:30:42 +01:00
adam commented 2025-12-29 15:30:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 15, 2018):

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).

@jeremystretch commented on GitHub (Feb 15, 2018): > 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).
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 status: accepted
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#50
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?