Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rack roles #241

Closed
bellwood opened this issue Jul 8, 2016 · 5 comments
Closed

Rack roles #241

bellwood opened this issue Jul 8, 2016 · 5 comments
Milestone

Comments

@bellwood
Copy link
Contributor

bellwood commented Jul 8, 2016

Would it be possible to allow rack name aliases?

We often refer to racks internally by their purpose (hosting, VPS, cloud, backup, demarc, etc) or by the colo customers name/company who is occupying the rack.

@bellwood bellwood changed the title Rack aliases Rack name aliases Jul 8, 2016
@ryanmerolle
Copy link
Contributor

You could also base the primary key and slug on netbox assigned IDs. That way naming can overlap if needed. It allows flexibility. I'm not a huge fan, but it's an option.

@bellwood
Copy link
Contributor Author

bellwood commented Jul 8, 2016

Would be nice, I have multiple colo customers with multiple racks

@jeremystretch
Copy link
Member

Would this be addressed by a combination of #132 (tagging) and #16 (multitenancy)?

@bellwood
Copy link
Contributor Author

bellwood commented Jul 8, 2016

Potentially universal search would - not sure on multi-tenancy

Would depend on implementation I suppose

@jeremystretch jeremystretch changed the title Rack name aliases Rack roles Jul 13, 2016
@jeremystretch
Copy link
Member

jeremystretch commented Jul 13, 2016

After some discussion, we'd like to implement roles for racks, similar to the roles we have for devices, prefixes, and VLANs. These will be user-defineable and optional.

Roles could be combined with multitenancy to cover the customer/colocation aspect.

@jeremystretch jeremystretch added this to the v1.5 milestone Jul 20, 2016
if-fi pushed a commit to if-fi/netbox that referenced this issue Oct 1, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants