Preventing a system power on before BMC Ready

[Michael Richardson]

Andrew Geissler <geissonator at gmail.com> wrote:
    > That got us brainstorming about some possible solutions: - Write some
    > code in bmcweb to send a “bmc state change event” anytime bmcweb comes
    > up to ensure listening clients know “something” has happened

useful, but not foolproof.

    > Queue up the power on request and execute it once we
    > reach BMC Ready (not sure what type of response that would be to
    > Redfish clients or what error path looks like if we never reach Ready?)

this seems like the best plan.

    > Push bmcweb further in the startup to BMC
    > Ready, ensuring clients can't talk to the BMC until it's near Ready
    > state

The problem  with this is that if you can't talk to the BMC, then you can't
find out why it was never Ready.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 511 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20230502/661e4ae6/attachment.sig>