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

Support for half-width device type v2 #9582

New Issue
Closed
opened 2025-12-29 21:19:14 +01:00 by adam · 7 comments
adam commented 2025-12-29 21:19:14 +01:00
Owner
Copy Link

Originally created by @vinceberg on GitHub (May 3, 2024).

NetBox version

v3.7.3

Feature type

Data model extension

Proposed functionality

Under Device Type, add a check box "Is Half-width".
Under Device\Location, change "Position" to include "Left" and "Right" in the drop down when the device type is half-width.

Use case

The currently supported approach to modeling half-width devices does not support modular chassis.
We do have HP EL8000 Chassis that have 8 half U bays(https://www.hpe.com/psnow/doc/a00067727enw). If I create a parent device as a place holder for the right and left chassis, I cannot create the chassis as a parent and therefore cannot install the blade server childs.

Database changes

No response

External dependencies

No response

Originally created by @vinceberg on GitHub (May 3, 2024). ### NetBox version v3.7.3 ### Feature type Data model extension ### Proposed functionality Under Device Type, add a check box "Is Half-width". Under Device\Location, change "Position" to include "Left" and "Right" in the drop down when the device type is half-width. ### Use case The currently supported approach to modeling half-width devices does not support modular chassis. We do have HP EL8000 Chassis that have 8 half U bays(https://www.hpe.com/psnow/doc/a00067727enw). If I create a parent device as a place holder for the right and left chassis, I cannot create the chassis as a parent and therefore cannot install the blade server childs. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:19:14 +01:00
adam closed this issue 2025-12-29 21:19:14 +01:00
adam commented 2025-12-29 21:19:15 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 6, 2024):

This FR will need significant expansion if we're to accept it. The flexibility required to support this kind of device simply isn't supported at the moment, so many aspects of the NetBox model for racks and devices would need updating.

As a starting point, we need a reasonably detailed outline of a proposal for fundamentally overhauling our current approach to modeling the racking of devices, so that it accommodates things that behave like half-width blade servers. Your use case would also need to articulate additional examples of device types that behave this way, so that the team knows they're not sinking a huge amount of work into enabling a niche use case.

@jeffgdotorg commented on GitHub (May 6, 2024): This FR will need significant expansion if we're to accept it. The flexibility required to support this kind of device simply isn't supported at the moment, so many aspects of the NetBox model for racks and devices would need updating. As a starting point, we need a reasonably detailed outline of a proposal for fundamentally overhauling our current approach to modeling the racking of devices, so that it accommodates things that behave like half-width blade servers. Your use case would also need to articulate additional examples of device types that behave this way, so that the team knows they're not sinking a huge amount of work into enabling a niche use case.
adam commented 2025-12-29 21:19:16 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (May 6, 2024):

some examples of half-width devices ive seen:

opengear om1200's - https://resources.opengear.com/om/datasheets/om1200/ (there's quite a few opengear devices based on this chassis)
ecler gear https://www.ecler.com/products/1uhrmkit/ ( a lot of audio industry devices are half-width )
qnap m2106pr-2s2t https://www.qnap.com/en/product/qsw-m2106pr-2s2t

its not uncommon to see the above devices mounted with just one "ear" depending on the side of the rack it's mounted to

@ITJamie commented on GitHub (May 6, 2024): some examples of half-width devices ive seen: opengear om1200's - https://resources.opengear.com/om/datasheets/om1200/ (there's quite a few opengear devices based on this chassis) ecler gear https://www.ecler.com/products/1uhrmkit/ ( a lot of audio industry devices are half-width ) qnap m2106pr-2s2t https://www.qnap.com/en/product/qsw-m2106pr-2s2t its not uncommon to see the above devices mounted with just one "ear" depending on the side of the rack it's mounted to
adam commented 2025-12-29 21:19:16 +01:00
Author
Owner
Copy Link

@DrDoc777 commented on GitHub (May 10, 2024):

We also have half-width devices in racks (e.g. RME ADI-4 DD & MOXA UPort 1610-8 ) and still haven't found a no solution how to get these documented on same RU in netbox.
There's definitely a use-case for half-width devices.
If it's possible to define "front-side" & "rear-side" as installation in a rack, then "left-side" & "right-side" should be possible too. Tricky part might be the appropriate visualization in the rack-view.

@DrDoc777 commented on GitHub (May 10, 2024): We also have half-width devices in racks (e.g. RME ADI-4 DD & MOXA UPort 1610-8 ) and still haven't found a no solution how to get these documented on same RU in netbox. There's definitely a use-case for half-width devices. If it's possible to define "front-side" & "rear-side" as installation in a rack, then "left-side" & "right-side" should be possible too. Tricky part might be the appropriate visualization in the rack-view.
adam commented 2025-12-29 21:19:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2024):

@vinceberg as @jeffgdotorg points out above, this FR requires a much more detailed technical proposal to move forward. Please spend some time getting familiar with how NetBox currently models racked devices, consider how this model might be expanded to serve your use case, and update your proposal above accordingly. If you're not yet ready to submit a concrete feature request, please consider starting a discussion to exchange ideas with other users instead.

@jeremystretch commented on GitHub (May 17, 2024): @vinceberg as @jeffgdotorg points out above, this FR requires a _much_ more detailed technical proposal to move forward. Please spend some time getting familiar with how NetBox currently models racked devices, consider how this model might be expanded to serve your use case, and update your proposal above accordingly. If you're not yet ready to submit a concrete feature request, please consider starting a [discussion](https://github.com/netbox-community/netbox/discussions/new/choose) to exchange ideas with other users instead.
adam commented 2025-12-29 21:19:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 2024):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (May 25, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:19:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 1, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jun 1, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
adam commented 2025-12-29 21:19:17 +01:00
Author
Owner
Copy Link

@ymjpajak commented on GitHub (Jul 4, 2024):

Is it possible to add this feature to NetBox? I need to visualize a rack with 8 chassis , four on the left and four on the right side, and I already use device bays (parent-child relation) to implement blades in the chassis ( and inventory items for servers in the blade).

@ymjpajak commented on GitHub (Jul 4, 2024): Is it possible to add this feature to NetBox? I need to visualize a rack with 8 chassis , four on the left and four on the right side, and I already use device bays (parent-child relation) to implement blades in the chassis ( and inventory items for servers in the blade).
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: revisions needed 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#9582
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?