Relax the rack naming constraint with rackgroups #493

Closed
opened 2025-12-29 16:22:37 +01:00 by adam · 1 comment
Owner

Originally created by @Zanthras on GitHub (Oct 26, 2016).

I think it would make sense to alter the rack naming constraint to include the rack groups instead of just the site.

Take for instance a Site thats a single building, but within it it has multiple floors with multiple IDF's per floor. Each IDF is its own rack group, but within each IDF the racks can easily be named quite identically, the idf (rack group) is the unique identifier.

With the current constraints the rack names basically have to include the rack group identifier, kinda making it redundant.

Originally created by @Zanthras on GitHub (Oct 26, 2016). I think it would make sense to alter the rack naming constraint to include the rack groups instead of just the site. Take for instance a Site thats a single building, but within it it has multiple floors with multiple IDF's per floor. Each IDF is its own rack group, but within each IDF the racks can easily be named quite identically, the idf (rack group) is the unique identifier. With the current constraints the rack names basically have to include the rack group identifier, kinda making it redundant.
adam added the status: duplicate label 2025-12-29 16:22:37 +01:00
adam closed this issue 2025-12-29 16:22:37 +01:00
Author
Owner

@jeremystretch commented on GitHub (Oct 26, 2016):

Duplicate of #238

@jeremystretch commented on GitHub (Oct 26, 2016): Duplicate of #238
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#493