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

site/room/rack overview #519

New Issue
Closed
opened 2025-12-29 16:22:48 +01:00 by adam · 7 comments
adam commented 2025-12-29 16:22:48 +01:00
Owner
Copy Link

Originally created by @Armadill0 on GitHub (Nov 8, 2016).

It would be very handy if you could add some sort of overview about the rows and racks of a specific site. Maybe also a sub level like a room between a site and rack groups would be great to manage different rooms in a single data center.
The feature would be useful e.g. to plan cabling betweens racks, rows and so on.

Originally created by @Armadill0 on GitHub (Nov 8, 2016). It would be very handy if you could add some sort of overview about the rows and racks of a specific site. Maybe also a sub level like a room between a site and rack groups would be great to manage different rooms in a single data center. The feature would be useful e.g. to plan cabling betweens racks, rows and so on.
adam added the status: duplicate label 2025-12-29 16:22:48 +01:00
adam closed this issue 2025-12-29 16:22:48 +01:00
adam commented 2025-12-29 16:22:49 +01:00
Author
Owner
Copy Link

@xenuser commented on GitHub (Nov 8, 2016):

I highly second this. NetBox as a DCIM solution is there to give you an overview of what you have: You have n amount of servers, you have n switches and routers and firewalls and so forth. Maintaining this data within NetBox gives you an overview of your IT landscape - why not doing such a thing for your racks by creating a feature which draws some sort of "map" of a room with all the rack rows?

And if you think this further, it might also make sense to link your room to a building within a site.
This certainly would add more layers of abstractions and hierarchy, but it would help to be more specific when describing sites, rack rooms etc.

@xenuser commented on GitHub (Nov 8, 2016): I highly second this. NetBox as a DCIM solution is there to give you an overview of what you have: You have n amount of servers, you have n switches and routers and firewalls and so forth. Maintaining this data within NetBox gives you an overview of your IT landscape - why not doing such a thing for your racks by creating a feature which draws some sort of "map" of a room with all the rack rows? And if you think this further, it might also make sense to link your room to a building within a site. This certainly would add more layers of abstractions and hierarchy, but it would help to be more specific when describing sites, rack rooms etc.
adam commented 2025-12-29 16:22:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 8, 2016):

It would be very handy if you could add some sort of overview about the rows and racks of a specific site.

This is too vague to be actionable as a feature request. Please elaborate.

Maybe also a sub level like a room between a site and rack groups would be great to manage different rooms in a single data center.

I think the model we have now strikes a good balance. The hierarchy goes site -> rack group -> rack, where the context of a rack group is up to the user to define. (Also, #164 has been opened to add the concept of a region containing multiple sites.) We want to avoid the hierarchy getting too top-heavy.

@jeremystretch commented on GitHub (Nov 8, 2016): > It would be very handy if you could add some sort of overview about the rows and racks of a specific site. This is too vague to be actionable as a feature request. Please elaborate. > Maybe also a sub level like a room between a site and rack groups would be great to manage different rooms in a single data center. I think the model we have now strikes a good balance. The hierarchy goes site -> rack group -> rack, where the context of a rack group is up to the user to define. (Also, #164 has been opened to add the concept of a region containing multiple sites.) We want to avoid the hierarchy getting too top-heavy.
adam commented 2025-12-29 16:22:49 +01:00
Author
Owner
Copy Link

@54-68-65-20-53-74-61-67 commented on GitHub (Nov 9, 2016):

Maybe a top down view of your server room similar to the front/rear view of the racks. Sort of like a map for your server room.

@54-68-65-20-53-74-61-67 commented on GitHub (Nov 9, 2016): Maybe a top down view of your server room similar to the front/rear view of the racks. Sort of like a map for your server room.
adam commented 2025-12-29 16:22:50 +01:00
Author
Owner
Copy Link

@xenuser commented on GitHub (Nov 9, 2016):

A top down view of all racks is exactly what I have in mind, I guess it might be the same for Armadill0.

@xenuser commented on GitHub (Nov 9, 2016): A top down view of all racks is exactly what I have in mind, I guess it might be the same for Armadill0.
adam commented 2025-12-29 16:22:50 +01:00
Author
Owner
Copy Link

@drybjed commented on GitHub (Nov 9, 2016):

OpenDCIM has a similar functionality.

@drybjed commented on GitHub (Nov 9, 2016): [OpenDCIM](http://opendcim.org/) has [a similar functionality](http://opendcim.org/screenshots.html).
adam commented 2025-12-29 16:22:50 +01:00
Author
Owner
Copy Link

@Armadill0 commented on GitHub (Nov 9, 2016):

A top down view is exactly what I had in mind. 👍

@Armadill0 commented on GitHub (Nov 9, 2016): A top down view is exactly what I had in mind. 👍
adam commented 2025-12-29 16:22:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 9, 2016):

Marking this as a duplicate of #114 then.

@jeremystretch commented on GitHub (Nov 9, 2016): Marking this as a duplicate of #114 then.
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
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#519
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?