Closed billhpe closed 1 year ago
If LLNL was interested in pursuing a power off approach, then this would be worth investigating. It is work that I did prior to LLNL indicating that they'd rather pursue a kubernetes based notification rather than powering anything off.
If LLNL was interested in pursuing a power off approach, then this would be worth investigating. It is work that I did prior to LLNL indicating that they'd rather pursue a kubernetes based notification rather than powering anything off.
Maybe I don't understand the requirements, but I was thinking fence_hpe_hss_ssh
would be used for compute nodes, which continue to be fenced with the power-off approach. And the rabbit would still report the HSS status in the get_power_status() call. So all would benefit from a Redfish-based agent.
The proposed changes are not suitable for NNF hardware.
See #14, #22 and successive changes
If HSS presents a standardized Redfish interface, would that be preferred to some SSH console hacking? I see a Redfish fencing agent in the ClusterLabs repo - have you tried that?