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

Device installed in device bay can block other device bays #5636

New Issue
Closed
opened 2025-12-29 19:30:23 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:30:23 +01:00
Owner
Copy Link

Originally created by @JulianJacobi on GitHub (Nov 9, 2021).

NetBox version

v3.0.9

Feature type

Data model extension

Proposed functionality

Add a possibility that a device installed to a device bay can block other device bays.

So it is possible to document a device, that is connected to on device bay, but has some kind of oversize to block one or more device bays.

I think an implementation where you can specify in the device-type/device how many device-bays this device will block is not possible due to the arbitrary way device bays are modeled. I think this model is a good choice to catch as many device bay use-cases as possible. So the only way to implement multiple-bays-blocking devices ist that you manually choose per device bay whether is it is blocked by a child device or not.

This issue was already discussed in #662 but this was closed and so I cannot write a comment there. Five years ago no-one was willing to implement an approach and open a pull request. I can do this, when it's desired.

Use case

Many bladecenters have blades with double with or double heigh or both.
Additionally in germany we have something like sub racks called Baugruppenträger, where you can insert devices with different sizes, that block any number of bays.
Actually there is no beautiful way to document this in Netbox.

Database changes

I would add a new field named blocked_by to DeviceBay model which is a foreign key to Device.
blocked_by and installed_device should be mutually_exclusive.

External dependencies

I don't see any external dependencies here.

Originally created by @JulianJacobi on GitHub (Nov 9, 2021). ### NetBox version v3.0.9 ### Feature type Data model extension ### Proposed functionality Add a possibility that a device installed to a device bay can block other device bays. So it is possible to document a device, that is connected to on device bay, but has some kind of oversize to block one or more device bays. I think an implementation where you can specify in the device-type/device how many device-bays this device will block is not possible due to the arbitrary way device bays are modeled. I think this model is a good choice to catch as many device bay use-cases as possible. So the only way to implement multiple-bays-blocking devices ist that you manually choose per device bay whether is it is blocked by a child device or not. This issue was already discussed in #662 but this was closed and so I cannot write a comment there. Five years ago no-one was willing to implement an approach and open a pull request. I can do this, when it's desired. ### Use case Many bladecenters have blades with double with or double heigh or both. Additionally in germany we have something like sub racks called Baugruppenträger, where you can insert devices with different sizes, that block any number of bays. Actually there is no beautiful way to document this in Netbox. ### Database changes I would add a new field named `blocked_by` to `DeviceBay` model which is a foreign key to `Device`. `blocked_by` and `installed_device` should be mutually_exclusive. ### External dependencies I don't see any external dependencies here.
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:30:23 +01:00
adam closed this issue 2025-12-29 19:30:24 +01:00
adam commented 2025-12-29 19:30:24 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 11, 2022):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 11, 2022): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:30:24 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 10, 2022):

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 (Feb 10, 2022): 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#5636
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?