Unify path that nodes take to get into `hwdown`
Right now, depending on how nodes find their way into hwdown
, they can be in different states.
For one, years ago I had added a sitevar reload/hwdownaction
that could define what we do with node when reload failed and we moved the nodes into hwdown
, one of do nothing, reboot the node into the admin MFS, or power it off. But, as the name implies, this is only done if it is the reload daemon that puts the node in hwdown
. If it gets there via the checknodes daemon, or via an explicit sched_reserve
or nalloc
, then nothing special is done.
For another, whether NFS filesystems should be available and mounted likewise depends on how the node gets into hwdown
, or more accurately, whether exports_setup
gets run on that path.
So, we should put some code in the Node.pm
module or maybe just write an explicit script that will put a node into hwdown
, taking care of all the magic necessary to ensure it is cleanly removed from wherever it is and put into a consistent state.