update for new host states and transitions
New host state and transitions have been approved via design docs and
phosphor-dbus-interfaces. Add these to the README.
ref:
https://github.com/openbmc/docs/blob/master/designs/state-management-and-external-interfaces.md
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/State/Host.interface.yaml
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1efad5bfdac7f4a3a1c5473e8d3cecbc77ed1095
diff --git a/README.md b/README.md
index e9ff81d..4ae1966 100644
--- a/README.md
+++ b/README.md
@@ -51,9 +51,11 @@
- RequestedPowerTransition: On, Off
- [host][4]: The host represents the software running on the system. In most
cases this is an operating system of some sort. The host can be `Off`,
- `Running`, or `Quiesced`(error condition)
- - CurrentHostState: Off, Running, Quiesced
- - RequestedHostTransition: Off, On, Reboot
+ `Running`, `Quiesced`(error condition), or in `DiagnosticMode`(collecting
+ diagnostic data for a failure)
+ - CurrentHostState: Off, Running, Quiesced, DiagnosticMode
+ - RequestedHostTransition: Off, On, Reboot, GracefulWarmReboot,
+ ForceWarmReboot
As noted above, phosphor-state-manager provides a command line tool,
[obmcutil][5], which takes a `state` parameter. This will use D-Bus commands to