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

Multiple rack roles for one rack #11382

New Issue
Closed
opened 2025-12-29 21:44:26 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:44:26 +01:00
Owner
Copy Link

Originally created by @snwiem on GitHub (Jul 15, 2025).

NetBox version

v4.3.3

Feature type

Data model extension

Proposed functionality

Allow assignment of multiple 'rack roles' to a single 'rack instance' (similar to 'contact groups' and 'contact').

Use case

I'm using rack roles such as 'Infrastructure', 'Storage', 'Compute', 'Server', etc, but only very rarely the racks I'm maintaining are provisioned with only one of those rack roles, but most of the time are a mixed setup of infrastructure, storage and server equipment.
At the moment I'm circumventing the unique rack roles by using tags. But this gets very messy especially if using tags very extensively like I do for many other operational and organizational purpose.
The benefit would be more flexibility in structuring the racks.

Database changes

rack (1) ------ (0..n) rack role

External dependencies

No response

Originally created by @snwiem on GitHub (Jul 15, 2025). ### NetBox version v4.3.3 ### Feature type Data model extension ### Proposed functionality Allow assignment of multiple 'rack roles' to a single 'rack instance' (similar to 'contact groups' and 'contact'). ### Use case I'm using rack roles such as 'Infrastructure', 'Storage', 'Compute', 'Server', etc, but only very rarely the racks I'm maintaining are provisioned with only one of those rack roles, but most of the time are a mixed setup of infrastructure, storage and server equipment. At the moment I'm circumventing the unique rack roles by using tags. But this gets very messy especially if using tags very extensively like I do for many other operational and organizational purpose. The benefit would be more flexibility in structuring the racks. ### Database changes rack (1) ------ (0..n) rack role ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:44:26 +01:00
adam closed this issue 2025-12-29 21:44:27 +01:00
adam commented 2025-12-29 21:44:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2025):

It sounds like maybe you're conflating rack roles and device roles. IMO it doesn't make sense to assign multiple roles to a rack, because you'll ultimately end up just replicating all of the roles assigned to devices within it. I'd stick with the tags approach (managing individual rack roles wouldn't be much cleaner), or alternatively create composite roles.

@jeremystretch commented on GitHub (Jul 17, 2025): It sounds like maybe you're conflating rack roles and device roles. IMO it doesn't make sense to assign multiple roles to a rack, because you'll ultimately end up just replicating all of the roles assigned to devices within it. I'd stick with the tags approach (managing individual rack roles wouldn't be much cleaner), or alternatively create composite roles.
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#11382
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?