Support decimal rack units for rack reservations #6942

Closed
opened 2025-12-29 19:47:02 +01:00 by adam · 2 comments
Owner

Originally created by @Toothwitch on GitHub (Sep 7, 2022).

NetBox version

v3.3.2

Feature type

Change to existing functionality

Proposed functionality

With v3.3 we got the possibility to add devices with .5 rack unit precision.

I would like to see the same logic/datamodel used for rack reservations because currently they do not support decimals at all.

Code which would have to be changed:
https://github.com/netbox-community/netbox/blob/v3.3.2/netbox/dcim/models/racks.py#L463

See also:
https://github.com/netbox-community/netbox/issues/10272

Use case

As with

https://github.com/netbox-community/netbox/issues/51
i would like to reserve the space used for these devices beforehand or block unusable space.

Database changes

The current PositiveSmallInteger would have to be changed to a Decimal

External dependencies

No response

Originally created by @Toothwitch on GitHub (Sep 7, 2022). ### NetBox version v3.3.2 ### Feature type Change to existing functionality ### Proposed functionality With v3.3 we got the possibility to add devices with .5 rack unit precision. I would like to see the same logic/datamodel used for rack reservations because currently they do not support decimals at all. Code which would have to be changed: https://github.com/netbox-community/netbox/blob/v3.3.2/netbox/dcim/models/racks.py#L463 See also: https://github.com/netbox-community/netbox/issues/10272 ### Use case As with https://github.com/netbox-community/netbox/issues/51 i would like to reserve the space used for these devices beforehand or block unusable space. ### Database changes The current PositiveSmallInteger would have to be changed to a Decimal ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:47:02 +01:00
adam closed this issue 2025-12-29 19:47:03 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 7, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 7, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Dec 8, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Dec 8, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6942