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

Allow Racks to show Device Front and Back Images based on Device #4008

New Issue
Closed
opened 2025-12-29 18:32:35 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:32:35 +01:00
Owner
Copy Link

Originally created by @a31amit on GitHub (Aug 21, 2020).

Environment

  • Python version: 3.8
  • NetBox version: 2.9

Proposed Functionality

Currently, Racks view shows Device Front and Back Images based on DeviceType however there is no way to use device image based on the device itself to display in Racks. This will help users see device pictures for customized hardware and commodity vendors.

Use Case

We are using some custom build hardware also many commodity vendors have allow their customers to use different chassis or form factors with customized hardware. Thus we had to create a custom device type based on their form factor as chassis type is a generic rather very specific model as this allow to put the same Motherboards and hardware parts in different form factor.

Hence servers with the same specs and same internal parts model can have different form factors for chassis. Allowing per Device Front / Back images would help users to see device images especially to see what are available ports / disks slots supported in chassis.

Example -

ServerA - 1U form factor with 2 disk slots with Motherboard Model XXXX1111
ServerB - 4U form factor with 24 disk slots with Motherboard Model XXXX1111

Please note that because commodity hardware vendors allow customization of hardware, most of time there is no Chassis Model available to query or see as these form factors are very generic or many times these were never been ever updated in DMI data by commodity hardware vendors.

Using existing methods to display images from DeviceType would lead users to a lot of custom DeviceType multiple to each Motherboard Model.

Database Changes

May be extending Models.

External Dependencies

Not sure

Originally created by @a31amit on GitHub (Aug 21, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.8 * NetBox version: 2.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Currently, Racks view shows Device Front and Back Images based on DeviceType however there is no way to use device image based on the device itself to display in Racks. This will help users see device pictures for customized hardware and commodity vendors. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case We are using some custom build hardware also many commodity vendors have allow their customers to use different chassis or form factors with customized hardware. Thus we had to create a custom device type based on their form factor as chassis type is a generic rather very specific model as this allow to put the same Motherboards and hardware parts in different form factor. Hence servers with the same specs and same internal parts model can have different form factors for chassis. Allowing per Device Front / Back images would help users to see device images especially to see what are available ports / disks slots supported in chassis. Example - ServerA - 1U form factor with 2 disk slots with Motherboard Model XXXX1111 ServerB - 4U form factor with 24 disk slots with Motherboard Model XXXX1111 Please note that because commodity hardware vendors allow customization of hardware, most of time there is no Chassis Model available to query or see as these form factors are very generic or many times these were never been ever updated in DMI data by commodity hardware vendors. Using existing methods to display images from DeviceType would lead users to a lot of custom DeviceType multiple to each Motherboard Model. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes May be extending Models. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Not sure
adam closed this issue 2025-12-29 18:32:35 +01:00
adam commented 2025-12-29 18:32:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 24, 2020):

This possibility was discussed under #1529 and it was decided to support images only per the device type model. Images are supported for convenience and cosmetic appeal only; they are not intended to convey meaningful data concerning the devices they represent.

We are using some custom build hardware also many commodity vendors have allow their customers to use different chassis or form factors with customized hardware.

These would need to be modeled as different device types anyway.

@jeremystretch commented on GitHub (Aug 24, 2020): This possibility was discussed under #1529 and it was decided to support images only per the device type model. Images are supported for convenience and cosmetic appeal only; they are not intended to convey meaningful data concerning the devices they represent. > We are using some custom build hardware also many commodity vendors have allow their customers to use different chassis or form factors with customized hardware. These would need to be modeled as different device types anyway.
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
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#4008
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?