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 View - Devices #317

Closed
nicko170 opened this issue Jul 18, 2016 · 3 comments
Closed

Rack View - Devices #317

nicko170 opened this issue Jul 18, 2016 · 3 comments
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@nicko170
Copy link

A 44U device placed in U1 shows up in U44. Would expect per notes in device creation to show up in U1, however would like for it to show in the whole rack instead of just a disabled field for the rest of the RU in that rack.

(this whole front view would be green)

image

@jeremystretch jeremystretch added the type: bug A confirmed report of unexpected behavior in the application label Jul 18, 2016
@jeremystretch
Copy link
Member

This is because we currently only define CSS classes for up to 42U in height. We could add more, but maybe it make sense to simply set the height and padding attributes directly on the elements within the template.

Out of curiosity, what sort of device do you have that's 44U in height?

@Zanthras
Copy link
Contributor

My most common example of devices taking the entire cab, are storage arrays, single monolithic enterprise sized storage arrays.

@nicko170
Copy link
Author

Thanks! This is now working.

Full rack colocation - so they can be searched from here. I've created generic colocation for 1RU - 45RU as a device which works well as I can then link to switches and power too 👍 (unless there is a better way to do this - but this seems to be working well) and also the reason I opened #304 to get an overview of used rackspace when looking to provision new services.

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 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants