openbmc_project/State/README.md

5 The goal of the phosphor-state-manager repository is to control and track the
11 interfaces are designed in a way to support a many to many mappings of each
21    it's required target (Ready) or it's on it's way there (NotReady). Users can
32    power to the chassis. The Chassis being on is a pre-req to the Host being
34    to one or the other is implied by the transition not matching the current
66 In multi-host or multi-chassis system, instance number can be used from 1-N, as
72 In the future, OpenBMC will provide an association API, which allows one to
77 to the system as a whole as if it was a system with one BMC, one chassis and one
80 entities as if they are one (if at all possible).
88 multi-chassis system, starting counting from 1 rather than 0 would avoid this
89 problem, while allowing an API user to _intentionally_ only power off one
91 to function on this multi-chassis system.
120 spec (DSP0249, Section 6.3, State Sets Tables, Table 7 – Boot-Related State
121 Sets, Set ID - 196 Boot Progress).
124 …https://github.com/openbmc/docs/blob/master/architecture/openbmc-systemd.md#error-handling-of-syst…
126   https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_project/State/
128 …https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_project/State/Ope…
130 …https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_project/State/Boo…