[RFE] PSU metadata to support power functions to disable / enable power going to system

[kambiz-aghaiepour]

It would be useful to have PSU/PDU metadata to map the connections of system resources to smart PDUs. This would be similar to network interface tracking that lends itself to switch port management. A few useful commands to go along with it:

# Show the current PSU -> PDU mappings
quads --host host01.example.com --ls-psus

# Turn off power to a specific PSU
quads --host host01.example.com --mod-psu --psu-id 1 --psu-state off

# Turn off power to all PSUs
quasd --host host01.example.com --power-state off

The PSU -> PDU metadata should contain several bits of information:
PDU_ID
PDU_PORT

And the PDUs would be defined to have:
PDU_IP
PDU_USER
PDU_PASS
PDU_TYPE

Depending on the type of PDU and support (e.g. APC), the power toggle subcommands would function as desired.

[sadsfae]

@kambiz-aghaiepour unless the landscape has changed with these devices and they still require SSH or telnet and more importantly we need to audit, document and then forever track their physical host connections I am uncertain this is something that's worth the trouble.

We already tried this by with the strips library in QUADS 1.x days many years ago, it was too much to keep with then and the varying quality of SSH (or in some cases telnet was better) transport implementation led to all kinds of issues and instability.

Is there some way to access an API instead of each PDU independently now?

I am still worried about keeping up with such a mapping continually as at least in our datacenter physical power cables are always moved and unplugged and worse than it not working is operating on the wrong system because of this.