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

Reintroduce the concept of rack groups #11916

New Issue
Open
opened 2025-12-29 21:51:28 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:51:28 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 10, 2025).

NetBox version

v4.4.8

Feature type

Data model extension

Proposed functionality

Introduce a "new" RackGroup model that can be used to group racks by their physical placement. This would be a flat organizational model similar to RackRole that serves merely as another dimension of categorization. The Rack model would be extended with a nullable ForeignKey to RackGroup.

("New" is in quotes here because NetBox previously had a RackGroup model, which became the Location model way back in NetBox v2.11.)

The RackGroup model could also function as a scope for a VLANGroup, to help better model L2 domains spanning rows or pairs of racks.

Use case

This would afford users (particularly datacenter operators) a secondary means beside Location to organize their racks. This can be helpful because a DC operator might want to group racks by row, for example, but still assign the racks in several rows to the same location (e.g. a cage or room).

Database changes

  • Introduce a new RackGroup model subclassing OrganizationalModel with no additional fields
  • Add a nullable (optional) ForeignKey on Rack pointing to RackGroup
  • Add the RackGroup model to VLANGROUP_SCOPE_TYPES

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Dec 10, 2025). ### NetBox version v4.4.8 ### Feature type Data model extension ### Proposed functionality Introduce a "new" RackGroup model that can be used to group racks by their physical placement. This would be a flat organizational model similar to RackRole that serves merely as another dimension of categorization. The Rack model would be extended with a nullable ForeignKey to RackGroup. ("New" is in quotes here because NetBox previously had a RackGroup model, which became the Location model way back in [NetBox v2.11](https://github.com/netbox-community/netbox/issues/5895).) The RackGroup model could also function as a scope for a VLANGroup, to help better model L2 domains spanning rows or pairs of racks. ### Use case This would afford users (particularly datacenter operators) a secondary means beside Location to organize their racks. This can be helpful because a DC operator might want to group racks by row, for example, but still assign the racks in several rows to the same location (e.g. a cage or room). ### Database changes - Introduce a new RackGroup model subclassing OrganizationalModel with no additional fields - Add a nullable (optional) ForeignKey on Rack pointing to RackGroup - Add the RackGroup model to `VLANGROUP_SCOPE_TYPES` ### External dependencies N/A
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@NSpikings-dB commented on GitHub (Dec 19, 2025):

I can't think of a use case right now, so just for understanding - would a rack only be able to belong to one RackGroup, or multiple of them?

@NSpikings-dB commented on GitHub (Dec 19, 2025): I can't think of a use case right now, so just for understanding - would a rack only be able to belong to one RackGroup, or multiple of them?
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2025):

A rack would be assigned to a single rack group, generally indicating its row or pod.

@jeremystretch commented on GitHub (Dec 22, 2025): A rack would be assigned to a single rack group, generally indicating its row or pod.
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 complexity: low needs milestone netbox 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#11916
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?