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.

Sign up for GitHub

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

Jump to bottom

Show child status in device bay list #2125

Closed
kasimon opened this issue May 29, 2018 · 0 comments
Closed

Show child status in device bay list #2125

kasimon opened this issue May 29, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@kasimon
Copy link

kasimon commented May 29, 2018

Issue type

[X] Feature request

Environment

  • Python version: 2.7.13
  • NetBox version: 2.3.3

Description

Please add the status ("Active"/"Offline"/...) of the child devices in the device view (dcim/devices/<device-id/) "Device Bays" table, for example before the child device name.

**Device Bays**
| Name         | Installed Devices                                       |  
| Device Bay 1 | [Active]  | child1.host.name | HPE ProLiant BL460c Gen8 |
| Device Bay 2 | [Offline] | child2.host.name | HPE ProLiant BL460c Gen8 |

This would be helpful when for example looking at a blade center to see which blade servers are in which state.
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Jun 6, 2018
@zachmoody zachmoody mentioned this issue Jul 11, 2018
Merged
jeremystretch added a commit that referenced this issue Jul 16, 2018
@jeremystretch
Merge pull request #2230 from digitalocean/2125-device-bay-status
ecaba5b 
Fixes #2125 - Show child status in device bay list
@jeremystretch jeremystretch mentioned this issue Jul 16, 2018
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kasimon @zachmoody @jeremystretch