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

Nested Racks, or Rack Adapters #11323

New Issue
Closed
opened 2025-12-29 21:43:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:43:38 +01:00
Owner
Copy Link

Originally created by @4o66 on GitHub (Jun 26, 2025).

NetBox version

v4.3.1

Feature type

New functionality

Proposed functionality

I work at an ISP. Because of legacy Telco standards, we have many sites with 23" wide racks. Some devices, Like DC PDUs, some switches, etc., have 23" rack ears, while newer equipment only has 19" rack ears. When we do need to mount 19" only equipment, we use rack adapters to reduce the width. If we know there may be a future need, we will get reducers for 5-10RU, even we only need 1 or 2 RU of reduced width.

In all cases, I can account for this in netbox today by making adapter devices that are "parent", but I then need to set all other devices as child, which is not likely to work for all users of netbox. Additionally, the device bays don't relate to U spaces.

Use case

For users that have multiple rack widths, and utilize physical adapters to adapt portions of racks, this would allow making sections of a rack into a sub-rack. This would alter the display of the rack elevation, and allow for tracking of how many RU are adapted and populated or free. It would be possible to see and add equipment to the open sub-slots. It should (unless elected as a checkbox) not permit devices who's U height exceeds available space to be mounted. (A 2U device could be mounted at the top U of an adapter and occupy the top U and the U directly above the adapter. Not great to do in practice, but the real world is messy.)

Database changes

Database structure may need to allow for a child/parent relationship of racks to other racks, with U height and starting U.

Subrack2 is a child of Rack100.05, and is 5U high, and begins at U24 of Rack100.05.

External dependencies

Unlikely to require a new dependency.

Originally created by @4o66 on GitHub (Jun 26, 2025). ### NetBox version v4.3.1 ### Feature type New functionality ### Proposed functionality I work at an ISP. Because of legacy Telco standards, we have many sites with 23" wide racks. Some devices, Like DC PDUs, some switches, etc., have 23" rack ears, while newer equipment only has 19" rack ears. When we do need to mount 19" only equipment, we use rack adapters to reduce the width. If we know there may be a future need, we will get reducers for 5-10RU, even we only need 1 or 2 RU of reduced width. In all cases, I can account for this in netbox today by making adapter devices that are "parent", but I then need to set all other devices as child, which is not likely to work for all users of netbox. Additionally, the device bays don't relate to U spaces. ### Use case For users that have multiple rack widths, and utilize physical adapters to adapt portions of racks, this would allow making sections of a rack into a sub-rack. This would alter the display of the rack elevation, and allow for tracking of how many RU are adapted and populated or free. It would be possible to see and add equipment to the open sub-slots. It should (unless elected as a checkbox) not permit devices who's U height exceeds available space to be mounted. (A 2U device could be mounted at the top U of an adapter and occupy the top U and the U directly above the adapter. Not great to do in practice, but the real world is messy.) ### Database changes Database structure may need to allow for a child/parent relationship of racks to other racks, with U height and starting U. Subrack2 is a child of Rack100.05, and is 5U high, and begins at U24 of Rack100.05. ### External dependencies Unlikely to require a new dependency.
adam added the type: featurestatus: duplicate labels 2025-12-29 21:43:38 +01:00
adam closed this issue 2025-12-29 21:43:39 +01:00
adam commented 2025-12-29 21:43:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 3, 2025):

I'm sorry but this has already been discussed at length and is not up for reconsideration. You'll need to create parent device types to represent any hardware into which child devices are installed.

@jeremystretch commented on GitHub (Jul 3, 2025): I'm sorry but this has already been discussed at length and is not up for reconsideration. You'll need to create parent device types to represent any hardware into which child devices are installed.
adam commented 2025-12-29 21:43:40 +01:00
Author
Owner
Copy Link

@4o66 commented on GitHub (Jul 6, 2025):

Ah. I was not aware of prior discussion, my apologies. Do you have a link
to that prior discussion so I can better understand why it was decided to
not support this? Thanks!

On Thu, Jul 3, 2025 at 10:21 Jeremy Stretch @.***>
wrote:

jeremystretch left a comment (netbox-community/netbox#19775)
https://github.com/netbox-community/netbox/issues/19775#issuecomment-3033009232

I'm sorry but this has already been discussed at length and is not up for
reconsideration. You'll need to create parent device types to represent any
hardware into which child devices are installed.

—
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/19775#issuecomment-3033009232,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXIEVLVM3LSB4JFPEY2FOL3GVRCDAVCNFSM6AAAAACAHLFW46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMZTGAYDSMRTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

@4o66 commented on GitHub (Jul 6, 2025): Ah. I was not aware of prior discussion, my apologies. Do you have a link to that prior discussion so I can better understand why it was decided to not support this? Thanks! On Thu, Jul 3, 2025 at 10:21 Jeremy Stretch ***@***.***> wrote: > *jeremystretch* left a comment (netbox-community/netbox#19775) > <https://github.com/netbox-community/netbox/issues/19775#issuecomment-3033009232> > > I'm sorry but this has already been discussed at length and is not up for > reconsideration. You'll need to create parent device types to represent any > hardware into which child devices are installed. > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/19775#issuecomment-3033009232>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABXIEVLVM3LSB4JFPEY2FOL3GVRCDAVCNFSM6AAAAACAHLFW46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMZTGAYDSMRTGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
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: duplicate 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#11323
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?