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

Rack View Two Servers One U #1027

New Issue
Closed
opened 2025-12-29 16:28:04 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:28:04 +01:00
Owner
Copy Link

Originally created by @MrEsL on GitHub (Jun 14, 2017).

Hello,

I am researching open source solutions for inventory managing of hardware devices in racks etc, and Netbox looks very promising.

We have a server that takes 2 U but has 4 servers/blades inside of it. is it possible to put two servers in a one U slot? or one server that takes 2 U but is divided into 4?

Attached is an image describing what I need.

Thank you very much.
rack

Originally created by @MrEsL on GitHub (Jun 14, 2017). Hello, I am researching open source solutions for inventory managing of hardware devices in racks etc, and Netbox looks very promising. We have a server that takes 2 U but has 4 servers/blades inside of it. is it possible to put two servers in a one U slot? or one server that takes 2 U but is divided into 4? Attached is an image describing what I need. Thank you very much. ![rack](https://user-images.githubusercontent.com/22653446/27131880-5546a2c2-5115-11e7-8cb8-f63723557fd7.jpg)
adam closed this issue 2025-12-29 16:28:04 +01:00
adam commented 2025-12-29 16:28:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2017):

NetBox allows you to create a parent device with device bays, and install child devices into these bays. Each child device is still managed as an independent entity with its own interfaces, IP addresses, etc. This is ideal for representing blade servers.

However, NetBox does not display the individual child devices in the rack elevation due to space constraints. (Longer device names would have to be extremely truncated.) The parent device is displayed in the rack elevation along with a count of populated and total device bays.

@jeremystretch commented on GitHub (Jun 14, 2017): NetBox allows you to create a parent device with device bays, and install child devices into these bays. Each child device is still managed as an independent entity with its own interfaces, IP addresses, etc. This is ideal for representing blade servers. However, NetBox does not display the individual child devices in the rack elevation due to space constraints. (Longer device names would have to be extremely truncated.) The parent device is displayed in the rack elevation along with a count of populated and total device bays.
adam commented 2025-12-29 16:28:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2017):

Aside from the space constraint, there's also the matter of indicating how child devices would be displayed. For instance, suppose you have a parent device with four bays numbered 1-4. Should they be displayed like this?

+-----+-----+
|  1  |  2  |
+-----+-----+
|  3  |  4  |
+-----+-----+

Or like this?

+-----+-----+
|  1  |  3  |
+-----+-----+
|  2  |  4  |
+-----+-----+

Or like this?

+---+---+---+---+
| 1 | 2 | 3 | 4 |
+---+---+---+---+

IMO the extra logic needed to ensure the proper representation of a device isn't worth the gain of a minor convenience.

@jeremystretch commented on GitHub (Jun 14, 2017): Aside from the space constraint, there's also the matter of indicating how child devices would be displayed. For instance, suppose you have a parent device with four bays numbered 1-4. Should they be displayed like this? ``` +-----+-----+ | 1 | 2 | +-----+-----+ | 3 | 4 | +-----+-----+ ``` Or like this? ``` +-----+-----+ | 1 | 3 | +-----+-----+ | 2 | 4 | +-----+-----+ ``` Or like this? ``` +---+---+---+---+ | 1 | 2 | 3 | 4 | +---+---+---+---+ ``` IMO the extra logic needed to ensure the proper representation of a device isn't worth the gain of a minor convenience.
adam commented 2025-12-29 16:28:05 +01:00
Author
Owner
Copy Link

@MrEsL commented on GitHub (Jun 15, 2017):

Thank you for clarifying the issue.

@MrEsL commented on GitHub (Jun 15, 2017): Thank you for clarifying the issue.
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
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#1027
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?