Display rack utilisation #695

New Issue

adam · 2025-12-29T16:24:51+01:00

adam commented

2025-12-29 16:24:51 +01:00

Originally created by @candlerb on GitHub (Feb 7, 2017).

When listing racks, display space utilisation (units used / total height). Preferably nice coloured bars like aggregate utilisation does.

A little care is needed with front/back mounting. I think you could overlay bars. Suppose you have 6U where both front and back are used, another 6U where only front are used, and 10U where only back are used. This is 6U (both) and 10U (maximum of front-only or back-only), giving utilisation of 16U, and could display as:

XXXXXXxxxxxxxxxx........
 |        |
both   front-or-back only

This is less than perfect, since adding a 4U box may not be possible without serious juggling if the available space is 4 x 1U. However, a figure for the largest contiguous gap could also be shown.

Relates to reserving rack space (#36), floorplan visualisation (#114)

Originally created by @candlerb on GitHub (Feb 7, 2017). When listing racks, display space utilisation (units used / total height). Preferably nice coloured bars like aggregate utilisation does. A little care is needed with front/back mounting. I think you could overlay bars. Suppose you have 6U where both front and back are used, another 6U where only front are used, and 10U where only back are used. This is 6U (both) and 10U (maximum of front-only or back-only), giving utilisation of 16U, and could display as: ~~~ XXXXXXxxxxxxxxxx........ | | both front-or-back only ~~~ This is less than perfect, since adding a 4U box may not be possible without serious juggling if the available space is 4 x 1U. However, a figure for the largest contiguous gap could also be shown. Relates to reserving rack space (#36), floorplan visualisation (#114)

adam closed this issue

2025-12-29 16:24:51 +01:00

adam commented

2025-12-29 16:24:52 +01:00

@jeremystretch commented on GitHub (Feb 7, 2017):

There's a lot of overhead in calculating utilized rack space. We already report on percentage of free space available; I'm pretty happy with that.

@jeremystretch commented on GitHub (Feb 7, 2017): There's a lot of overhead in calculating utilized rack space. We already report on percentage of free space available; I'm pretty happy with that.

adam commented

2025-12-29 16:24:52 +01:00

@candlerb commented on GitHub (Feb 7, 2017):

We already report on percentage of free space available

OK, operator error - I didn't find it initially. Thanks.

@candlerb commented on GitHub (Feb 7, 2017): > We already report on percentage of free space available OK, operator error - I didn't find it initially. Thanks.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#695