Aha! I worked out a way to do this using AMT:
ubuntu@maas:~$ yes|AMT_PASSWORD=Password1+ amttool 10.0.0.150 powerdown host ., powerdown [y/N] ? execute: powerdown result: pt_status: not permitted ubuntu@maas:~$ yes|AMT_PASSWORD=Password1+ amttool 10.0.0.150 reset cd host ., reset [y/N] ? execute: reset result: pt_status: success ubuntu@maas:~$ yes|AMT_PASSWORD=Password1+ amttool 10.0.0.150 powerdown host ., powerdown [y/N] ? execute: powerdown result: pt_status: success ubuntu@maas:~$ AMT_PASSWORD=Password1+ amttool 10.0.0.150 info ### AMT info on machine '10.0.0.150' ### AMT version: 8.1.30 Hostname: . Powerstate: S5 (soft-off) Remote Control Capabilities: IanaOemNumber 157 OemDefinedCapabilities IDER SOL BiosSetup SpecialCommandsSupported PXE-boot HD-boot cd-boot SystemCapabilitiesSupported powercycle powerdown powerup reset SystemFirmwareCapabilities 7821
I'll throw this into the template as a special override if we get the "pt_status: not_permitted" response if everyone agrees?
Aha! I worked out a way to do this using AMT:
ubuntu@maas:~$ yes|AMT_ PASSWORD= Password1+ amttool 10.0.0.150 powerdown PASSWORD= Password1+ amttool 10.0.0.150 reset cd PASSWORD= Password1+ amttool 10.0.0.150 powerdown Password1+ amttool 10.0.0.150 info apabilities IDER SOL BiosSetup andsSupported PXE-boot HD-boot cd-boot ilitiesSupporte d powercycle powerdown powerup reset areCapabilities 7821
host ., powerdown [y/N] ? execute: powerdown
result: pt_status: not permitted
ubuntu@maas:~$ yes|AMT_
host ., reset [y/N] ? execute: reset
result: pt_status: success
ubuntu@maas:~$ yes|AMT_
host ., powerdown [y/N] ? execute: powerdown
result: pt_status: success
ubuntu@maas:~$ AMT_PASSWORD=
### AMT info on machine '10.0.0.150' ###
AMT version: 8.1.30
Hostname: .
Powerstate: S5 (soft-off)
Remote Control Capabilities:
IanaOemNumber 157
OemDefinedC
SpecialComm
SystemCapab
SystemFirmw
I'll throw this into the template as a special override if we get the "pt_status: not_permitted" response if everyone agrees?