From: Michael Richardson <mcr@sandelman.ca>
To: Andrew Geissler <geissonator@gmail.com>,
OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Preventing a system power on before BMC Ready
Date: Tue, 02 May 2023 17:50:32 -0400 [thread overview]
Message-ID: <21047.1683064232@localhost> (raw)
In-Reply-To: <0992ABFC-7CD8-4E4E-8731-167E59C8A9F7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Andrew Geissler <geissonator@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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-05-02 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 20:48 Preventing a system power on before BMC Ready Andrew Geissler
2023-05-02 21:50 ` Michael Richardson [this message]
2023-05-03 0:48 ` Ed Tanous
2023-05-09 20:00 ` Andrew Geissler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21047.1683064232@localhost \
--to=mcr@sandelman.ca \
--cc=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.