starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Calculate power utilization based on the installed devices and modules #8093

New Issue
Closed
opened 2025-12-29 20:32:18 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:32:18 +01:00
Owner
Copy Link

Originally created by @chwichmann on GitHub (May 20, 2023).

NetBox version

v3.5.1

Feature type

Data model extension

Proposed functionality

Set the estimated power consumption in watts on the device type and module type. On the power port allocated draw write {device} and the way the power port fetches the data for the allocated draw is now by iterate through all installed modules and the hosting device and sum the “estimated power consumption”. The maximum draw still is the physical limit for that power port where the allocated power draw is the real one based on the assembly of the device.

Redundant PSU’s
This will also work for redundant power supplies by assuming that the allocated draw needs to be available for both installed PSU’s. at any time.

Devices with three + PSU’s
Some devices have three ore more PSU’s and aren’t designed to handle the whole electrical draw (n+1 design). In this case you may fill in the allocated draw manually (like now) on the power port.

Backward compatibility
By only activating this new feature with the {device} string it should not break any actual code or behavior.

Use case

For chassis-based devices it’s common that the overall power consumption depends on the installed modules. Therefore, it would be nice to see the real power consumption based on the installed modules.

• You may deal with power ratings of shelfs and PSU’s because there is an older hardware revision that is not rated for the power of possible assemblies – like newer 400G+ Line cards.

• In life cycle projects you may have new devices with higher power demands than the old one. Depending on the really needs of the assembly in a particular site you may see if the actual power feed and the outlet need an upgrade

• Based on this calculation you may forecast the costs for electricity more accurate

• The UPS and batterie uptime on a remote site are dependent on the power consumption. Based on the proposed feature the uptime calculations would be more accurate

• PSU’s with module-based rectifiers can be assembled based on the real need of the device

Database changes

DCIM.DeviceType Model add IntegerField “power_consumption”
DCIM.ModuleType Model add IntegerField “power_consumption”

External dependencies

N.A.

Originally created by @chwichmann on GitHub (May 20, 2023). ### NetBox version v3.5.1 ### Feature type Data model extension ### Proposed functionality Set the estimated power consumption in watts on the device type and module type. On the power port allocated draw write {device} and the way the power port fetches the data for the allocated draw is now by iterate through all installed modules and the hosting device and sum the “estimated power consumption”. The maximum draw still is the physical limit for that power port where the allocated power draw is the real one based on the assembly of the device. **Redundant PSU’s** This will also work for redundant power supplies by assuming that the allocated draw needs to be available for both installed PSU’s. at any time. **Devices with three + PSU’s** Some devices have three ore more PSU’s and aren’t designed to handle the whole electrical draw (n+1 design). In this case you may fill in the allocated draw manually (like now) on the power port. **Backward compatibility** By only activating this new feature with the {device} string it should not break any actual code or behavior. ### Use case For chassis-based devices it’s common that the overall power consumption depends on the installed modules. Therefore, it would be nice to see the real power consumption based on the installed modules. • You may deal with power ratings of shelfs and PSU’s because there is an older hardware revision that is not rated for the power of possible assemblies – like newer 400G+ Line cards. • In life cycle projects you may have new devices with higher power demands than the old one. Depending on the really needs of the assembly in a particular site you may see if the actual power feed and the outlet need an upgrade • Based on this calculation you may forecast the costs for electricity more accurate • The UPS and batterie uptime on a remote site are dependent on the power consumption. Based on the proposed feature the uptime calculations would be more accurate • PSU’s with module-based rectifiers can be assembled based on the real need of the device ### Database changes DCIM.DeviceType Model add IntegerField “power_consumption” DCIM.ModuleType Model add IntegerField “power_consumption” ### External dependencies N.A.
adam added the type: featurepending closure labels 2025-12-29 20:32:18 +01:00
adam closed this issue 2025-12-29 20:32:19 +01:00
adam commented 2025-12-29 20:32:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 19, 2023):

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 (Aug 19, 2023): 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).
adam commented 2025-12-29 20:32:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 18, 2023):

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 (Sep 18, 2023): 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8093
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?