malex984
commented
6 years ago Should we extend Hilbert.yml to be able to mark such a fallback method to start/stop stations?
It may be a an extended type of a station's poweron_settings: WOL_AMT.... but i do not like the idea of keeping AMT-related data in Hilbert.yml (user, password, port)...
Proposal: we can add wsman (or some similar CLI tool) with some wrapper scripts into hilbert/mng so that Dashboard server would be able to use it as the last resort to power on/off AMT-capable PCs...
Hilbert CLI / backend should support some out-of-band-management commands for stations where this is supported. We discussed Intel vPro / AMT as means of hard-restarting a computer if it doesn't respond.
Clearly hardware needs to support this so the actual command / script for that needs to be provided eventually (will do later), but the functionality for triggering should already be part of Hilbert. For our specific case, "tower PCs" would support it, while "micro PCs" would not. Hilbert configuration variable could define the name of a script that can be executed on the server to do this (or do nothing if the variable is not defined).
Would this functionality be included in the "poweroff" command (e.g. "--force") or as a separate "last resort" command (like "oob-poweroff")? Advantage of separate command is that it makes it more obvious that it's really doing something different from normal shutdown.