Handle Power Supply #37
Labels
No labels
help wanted
need testing
status: accepted
status: discussing
type: bug
type: documentation
type: duplicate
type: enhancement
type:hardware
type: invalid
type: major feature
type: minor feature
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DGNum/netbox-agent#37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
An example of dmidecode output for multiple power supply
There's a case with blades/chassis with 4 power supply, where:
2 out of 4 servers use 2 power supply and the other 2 servers use the 2 others power supply
In case of blade, we'll need to create the power supply on the parent device and
get_or_create
It's a 4u box, with 4 power supplies in it; there are 8 blades, 4 nodes/blades (n1,n2,n3,n4) use two of the power supplies, the other 4 nodes (n5,n6,n7,n8) use the other two power supplies.
from lshw -json (which is way better than dmidecode - it includes the sata and nvme drives)
from another node, on the other 2 power supplies:
What's interesting is the BMC Webinterface has a multinode page, that shows 4 of the nodes..
Now to see if I can get that via Redfish, or scrape the page (ugh)
Unfortunately it seems that dmidecode gives more infos for power supply like:
I think we'll go for dmidecode output, or let the user chose lshw if needed
We can also report the PSU consumption:
For example,
omreport
doesn't report the power consumption per PSU in WBut it gives the Amperage per PSU
If the user has setup the
Power Feed
for the datacenter of the server, we can report the PSU consumption viaPS1 Amperage * Power Feed Voltage
We could add a
get_power_consumption
method per Manufacturer then