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

SVG Rack Display - Show VC Member Name #8601

New Issue
Closed
opened 2025-12-29 20:38:42 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:38:42 +01:00
Owner
Copy Link

Originally created by @shepherdjay on GitHub (Sep 11, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

Per #13725 the Rack View shows a virtual chassis name and position instead of the device name.

Proposal is to remove this section of code that makes that distinction

a8a36c0a8f/netbox/dcim/svg/racks.py (L32-L33)

Use case

Rack diagrams should reflect, as much as possible, the real world labeling that might exist on a device in a rack. Users who wish to use the labeling format of {device.virtual_chassis.name}:{device.vc_position} are able to name the devices in that manner.

Database changes

None

External dependencies

None

Originally created by @shepherdjay on GitHub (Sep 11, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality Per #13725 the Rack View shows a virtual chassis name and position instead of the device name. Proposal is to remove this section of code that makes that distinction https://github.com/netbox-community/netbox/blob/a8a36c0a8fa39250792abeb493ed3065bf0d9fdc/netbox/dcim/svg/racks.py#L32-L33 ### Use case Rack diagrams should reflect, as much as possible, the real world labeling that might exist on a device in a rack. Users who wish to use the labeling format of `{device.virtual_chassis.name}:{device.vc_position}` are able to name the devices in that manner. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:38:42 +01:00
adam closed this issue 2025-12-29 20:38:42 +01:00
adam commented 2025-12-29 20:38:43 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 11, 2023):

Rack diagrams should reflect, as much as possible, the real world labeling that might exist on a device in a rack. Users who wish to use the labeling format of {device.virtual_chassis.name}:{device.vc_position} are able to name the devices in that manner.

I would like to add a counter point:

"Real World", the labelling would likely be the VC name, not the individual switch name.

VC is meant to capture the usage of technologies like "Stackwise" and "Virtual Stackwise" (I cannot speak to Juniper or HP as I have never stacked those), both of which only have a single name for both the VC and the individual switch hostname. It is not meant for: vPC/MC-LAG, Firewall HA (in most cases), or similar situated technologies.

So, outside of corner cases where people are not using the VC as intended (to show a cluster between firewalls for example), the real world would actually be to show the VC name and annotate the rack drawing with a position indicator

@DanSheps commented on GitHub (Sep 11, 2023): > Rack diagrams should reflect, as much as possible, the real world labeling that might exist on a device in a rack. Users who wish to use the labeling format of `{device.virtual_chassis.name}:{device.vc_position}` are able to name the devices in that manner. I would like to add a counter point: "Real World", the labelling would likely be the VC name, not the individual `switch name`. VC is meant to capture the usage of technologies like "Stackwise" and "Virtual Stackwise" (I cannot speak to Juniper or HP as I have never stacked those), both of which only have a single name for both the VC and the individual switch hostname. It is not meant for: vPC/MC-LAG, Firewall HA (in most cases), or similar situated technologies. So, outside of corner cases where people are not using the VC as intended (to show a cluster between firewalls for example), the real world would actually be to show the VC name and annotate the rack drawing with a position indicator
adam commented 2025-12-29 20:38:43 +01:00
Author
Owner
Copy Link

@shepherdjay commented on GitHub (Sep 11, 2023):

the real world would actually be to show the VC name and annotate the rack drawing with a position indicator

This use case is still available if the code is removed. If you name your member devices in the same format Netbox currently imposes then there will be no change to the rack diagrams for that use case.

...the real world would actually be to show the VC name and annotate the rack drawing with a position indicator

For better or worse we have physically labeled our members differently than <vc_name>:<position> on our switch stacks. Similarly, others might have yet other ways they physically label the member devices (or don't label at all).

@shepherdjay commented on GitHub (Sep 11, 2023): > the real world would actually be to show the VC name and annotate the rack drawing with a position indicator This use case is still available if the code is removed. If you name your member devices in the same format Netbox currently imposes then there will be no change to the rack diagrams for that use case. > ...the real world would actually be to show the VC name and annotate the rack drawing with a position indicator For better or worse we have physically labeled our members differently than `<vc_name>:<position>` on our switch stacks. Similarly, others might have yet other ways they physically label the member devices (or don't label at all).
adam commented 2025-12-29 20:38:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 11, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 11, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:38:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 10, 2024):

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[bot] commented on GitHub (Jan 10, 2024): 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.
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 pending closure status: under review type: feature
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#8601
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?