starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 06:13:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Support for placing devices in 1/3 of a Rack Unit #10521

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

Originally created by @maxzapp on GitHub (Nov 27, 2024).

NetBox version

v4.1.7

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

At the moment devices can be placed bei 1/2 of a Unit in a Rack
Target should be devices can be placed bei 1/3 of a Unit in a Rack

Use case

Reality shows that devices have been places over the years by diffent people not exactly in the "official" 1U grid of the racks.
Thery are often shiftet bei 1/3 or 2/3 or 1/2 of an official Unit hight. The hight consumption an planning of free place would be more accurate.

Database changes

unknown

External dependencies

unknown

Originally created by @maxzapp on GitHub (Nov 27, 2024). ### NetBox version v4.1.7 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality At the moment devices can be placed bei 1/2 of a Unit in a Rack Target should be devices can be placed bei 1/3 of a Unit in a Rack ### Use case Reality shows that devices have been places over the years by diffent people not exactly in the "official" 1U grid of the racks. Thery are often shiftet bei 1/3 or 2/3 or 1/2 of an official Unit hight. The hight consumption an planning of free place would be more accurate. ### Database changes unknown ### External dependencies unknown
adam added the type: feature label 2025-12-29 21:32:33 +01:00
adam closed this issue 2025-12-29 21:32:33 +01:00
adam commented 2025-12-29 21:32:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 2, 2024):

I'm sorry but this has been proposed in the past and rejected. Our recommendation is to adhere to industry best practices and consume only whole or half rack units consistently.

@jeremystretch commented on GitHub (Dec 2, 2024): I'm sorry but this has been proposed in the past and rejected. Our recommendation is to adhere to industry best practices and consume only whole or half rack units consistently.
adam commented 2025-12-29 21:32:35 +01:00
Author
Owner
Copy Link

@maxzapp commented on GitHub (Dec 2, 2024):

That's bad, but your decision.

Why not let community decide what features should be implemented.

Your argument is a killer argument for everything if I rely on best practices an industry standards i would not need a tool like Netbox

@maxzapp commented on GitHub (Dec 2, 2024): That's bad, but your decision. Why not let community decide what features should be implemented. Your argument is a killer argument for everything if I rely on best practices an industry standards i would not need a tool like Netbox
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 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#10521
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?