summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoel Stanley <joel@jms.id.au>2016-06-20 18:57:41 +0930
committerJeremy Kerr <jk@ozlabs.org>2016-07-07 12:01:47 +0800
commit4cd993e2ebeeba49468f485fda6b3e9b6f1cec7b (patch)
treea5e4492fa56ac6320bc84a3a8109304fa63371c8
parentbcc4ffd0dccb984c25c1cfe0ed17ea296bbfef84 (diff)
downloadopenbmc-docs-4cd993e2ebeeba49468f485fda6b3e9b6f1cec7b.tar.gz
openbmc-docs-4cd993e2ebeeba49468f485fda6b3e9b6f1cec7b.zip
host-management: Add section on power control
Signed-off-by: Joel Stanley <joel@jms.id.au>
-rw-r--r--host-management.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/host-management.md b/host-management.md
index d223850..e313468 100644
--- a/host-management.md
+++ b/host-management.md
@@ -140,3 +140,27 @@ Each boot parameter is represented by an individual property, and their hex
value is displayed in a string format. For example, a boot flags parameter value
of `0x8014000000` would be stored as a `8014000000` string in the
`settings/host0/boot_flags` property.
+
+Host power control
+------------------
+
+The host can be controlled through the `chassis` object. It implements a number
+of actions including powerOn and powerOff. These correspond to the IPMI
+`chassis power on` and `chassis power off` commands.
+
+Assuming you have logged in, the following will issue a POST with an empty data
+payload that powers the host on:
+
+```
+curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \
+ -d '{"data": []}' https://bmc/org/openbmc/control/chassis0/action/powerOn
+```
+
+Other actions available are:
+
+ * `setIdentify` / `clearIdentify`
+ * `powerOff`
+ * `softPowerOff`
+ * `reboot`
+ * `softReboot`
+ * `getPowerState`
OpenPOWER on IntegriCloud