-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add an asset tag field to the rack model #1444
Comments
The problem with adding a RackType object analogous to DeviceType is we've already associated a type, width, and height with each individual rack. Introducing a separate model for this would allow racks of the same RackType to have different physical characteristics defined locally, which obviously wouldn't make sense. It would be possible to allow users to begin adopting the new approach at their leisure, but many would opt not to pursue it and I don't want to support two schemes for defining racks indefinitely. Alternatively, we could add a direct association from the Rack model to the Manufacturer model, and add a Serial number I have no problem adding. Asset tag might be problematic, as it's reasonable to assume that an asset tag will be unique across racks and devices, so we'd have to change it from a local field to a ForeignKey on a new model with its own table, which could get messy with regard to data migrations. |
I'm going to hold off on adding an asset tag field to the rack model for now. I'd like to gather more feedback on that feature before we implement to avoid working ourselves into a corner. |
Issue type
[x] Feature request
[ ] Bug report
[ ] Documentation
Environment
Description
Add fields to the rack model so that one can identify:
Use case
In the same way that it's useful to know what device type (model and manufacturer) a server is, it's also useful to know the same details for the rack:
The text was updated successfully, but these errors were encountered: