half-width devices in rack and create blindpanels / cable guides with using it as an "device" #4995

New Issue

adam · 2025-12-29T19:23:00+01:00

adam commented

2025-12-29 19:23:00 +01:00

Originally created by @chesronw on GitHub (Jun 11, 2021).

NetBox version

V2.11.3

Feature type

New functionality

Proposed functionality

Hi,

We would like to add half-width devices without using a parent device.
This because the parent isn't a device but a mounting kit where we can add 2 devices on it.

To work with nonparent devices we cleaning up all the fake devices that are used as a "device" but are not a device.
It is more rack equipment or tooling.
This is also a good request to add nondevices in racks like blind panels, or cable guides.

So we keep the device list clean with only real devices.

hopefully, you also see the value in it.

Use case

Use case is verry simple.
i assume that everyone that is working with netbox are also using this tool to have a complete view of all the racks that they have and how the layout is of the racks. include of all the blind panels and cable managers.

It's just really weird to create for each blind panel and cable manager an device..
Or make the option that you can add a device in multiple racks.

Then we have also the half-width devices.
These devices are currently not supported in Netbox.. well with a dirty solution to have a parent (Non-device) but this really creates a huge mess in the device list.
To prevent this.. it better to give the option that the device is a half-width device that you can add to a rack.. on the left or right. in that case you can add two half-width devices on the same HE in the RACK

Database changes

No response

External dependencies

No response

Originally created by @chesronw on GitHub (Jun 11, 2021). ### NetBox version V2.11.3 ### Feature type New functionality ### Proposed functionality Hi, We would like to add half-width devices without using a parent device. This because the parent isn't a device but a mounting kit where we can add 2 devices on it. To work with nonparent devices we cleaning up all the fake devices that are used as a "device" but are not a device. It is more rack equipment or tooling. This is also a good request to add nondevices in racks like blind panels, or cable guides. So we keep the device list clean with only real devices. hopefully, you also see the value in it. ### Use case Use case is verry simple. i assume that everyone that is working with netbox are also using this tool to have a complete view of all the racks that they have and how the layout is of the racks. include of all the blind panels and cable managers. It's just really weird to create for each blind panel and cable manager an device.. Or make the option that you can add a device in multiple racks. Then we have also the half-width devices. These devices are currently not supported in Netbox.. well with a dirty solution to have a parent (Non-device) but this really creates a huge mess in the device list. To prevent this.. it better to give the option that the device is a half-width device that you can add to a rack.. on the left or right. in that case you can add two half-width devices on the same HE in the RACK ### Database changes _No response_ ### External dependencies _No response_

adam added the type: feature status: duplicate labels 2025-12-29 19:23:00 +01:00

adam closed this issue

2025-12-29 19:23:00 +01:00

adam commented

2025-12-29 19:23:01 +01:00

@jeremystretch commented on GitHub (Jun 11, 2021):

This was proposed back in #2467 and rejected as it violates one of NetBox's core design tenets: closely modeling the real world.

This because the parent isn't a device but a mounting kit where we can add 2 devices on it.

But it is a device, and must be modeled as such. It is impossible to physically mount a child device without it, and it is impossible to install a non-child device in a rack unit where such a mount kit has been installed.

The simple solution is to create these mounting kits as parent devices, and model the devices within them as children.

@jeremystretch commented on GitHub (Jun 11, 2021): This was proposed back in #2467 and rejected as it violates one of NetBox's core design tenets: closely modeling the real world. > This because the parent isn't a device but a mounting kit where we can add 2 devices on it. But it _is_ a device, and must be modeled as such. It is impossible to physically mount a child device without it, and it is impossible to install a non-child device in a rack unit where such a mount kit has been installed. The simple solution is to create these mounting kits as parent devices, and model the devices within them as children.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#4995