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

Raft of Enhancements to Power - capacity management, unique ports, utilization view #403

New Issue
Closed
opened 2025-12-29 16:21:42 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:21:42 +01:00
Owner
Copy Link

Originally created by @iamdadmin on GitHub (Aug 31, 2016).

Add power utilization bar to Power Connections, options to group or filter by Site, Rack-Group, Rack or PDU Device

When viewing Racks, you get a utilization in %, being a ratio of free space minus occupied space. Doing the same for power bars would be useful.

Ideally you'd want to be able to filter or group by Site, Rack-Group, Rack or PDU Device.

Power Capacity Management

This also implies an extra field on PDU type devices which would be "max power". I'd suggest this be freeform to allow people to manage it in either amps or watts. Further, it implies custom fields on device types and devices for peak power draw, steady power draw, and heat dissipation in BTU/hr.

It might even benefit a 'weight' field on device types and devices.

Make Power Connections 'unique' (and console and management)

When viewing a device, and selecting to add a new power (/console/management) connection you search for a CI or select it from a list, and then the API loads the valid ports for the device. The API call here should instead only return all non-connected ports, or if that's not possible, it should return any current assignment in addition to the port ID; instead of just being a list of "" it would be " - " for ports with a connection.

I don't know if this requires a new API call, or just requires the page to be configured to load a different API call, which would already return this data.

Originally created by @iamdadmin on GitHub (Aug 31, 2016). # Add power utilization bar to Power Connections, options to group or filter by Site, Rack-Group, Rack or PDU Device When viewing Racks, you get a utilization in %, being a ratio of free space minus occupied space. Doing the same for power bars would be useful. Ideally you'd want to be able to filter or group by Site, Rack-Group, Rack or PDU Device. # Power Capacity Management This also implies an extra field on PDU type devices which would be "max power". I'd suggest this be freeform to allow people to manage it in either amps or watts. Further, it implies custom fields on device types and devices for peak power draw, steady power draw, and heat dissipation in BTU/hr. It might even benefit a 'weight' field on device types and devices. # Make Power Connections 'unique' (and console and management) When viewing a device, and selecting to add a new power (/console/management) connection you search for a CI or select it from a list, and then the API loads the valid ports for the device. The API call here should instead only return all non-connected ports, or if that's not possible, it should return any current assignment in addition to the port ID; instead of just being a list of "<port name>" it would be "<port name> - <connected device>" for ports with a connection. I don't know if this requires a new API call, or just requires the page to be configured to load a different API call, which would already return this data.
adam closed this issue 2025-12-29 16:21:42 +01:00
adam commented 2025-12-29 16:21:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 1, 2016):

Power management is covered by #54. Please break the other two requests into their own issues.

@jeremystretch commented on GitHub (Sep 1, 2016): Power management is covered by #54. Please break the other two requests into their own issues.
adam commented 2025-12-29 16:21:43 +01:00
Author
Owner
Copy Link

@iamdadmin commented on GitHub (Sep 1, 2016):

Sure thing.

@iamdadmin commented on GitHub (Sep 1, 2016): Sure thing.
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
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#403
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?