From: Vijay Khemka <vijaykhemka@fb.com>
To: Sui Chen <suichen@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Request to create repository google-ipmi-bmc-health
Date: Thu, 1 Oct 2020 19:05:28 +0000 [thread overview]
Message-ID: <D355FA68-E163-4DA8-861E-7E9DB68F5EEB@fb.com> (raw)
In-Reply-To: <CAJOps0sd-YFr5P+_N0i78pd9akBJS6DP99wugKvUDOGpXw2pcA@mail.gmail.com>
Hi Sui,
On 9/30/20, 8:30 AM, "openbmc on behalf of Sui Chen" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of suichen@google.com> wrote:
Hello OpenBMC community,
We are working on an IPMI blob-based implementation of BMC health
monitoring. We currently have an internal working prototype version
and would like to upload it to this newly proposed repository,
openbmc/google-ipmi-bmc-health .
In my opinion, we can enhance existing health-monitor and add your features.
We are aware of existing BMC health monitoring designs such as:
1. https://github.com/openbmc/phosphor-health-monitor and its
documentation https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_c_openbmc_docs_-2B_31957&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=Z-_Rsue1ZHBD_TgPw7EDIc8dh8E8o8dlUe8aKr7I5VA&s=HTKEM8tcIgwzwL4OQVP1Kcve6ZfnhSTohdwPmIrjwe4&e=
2. https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_c_openbmc_docs_-2B_34766&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=Z-_Rsue1ZHBD_TgPw7EDIc8dh8E8o8dlUe8aKr7I5VA&s=EcxSrU1PC6Akfy1FR0wo-5TC_QvMld9SDT7pJAh5QcM&e=
Main differences between this implementation and existing ones are:
- google-ipmi-bmc-health is implemented with the IPMI blob handler
framework and exists as an IPMI blob handler, while
phosphor-health-monitor runs as a daemon and exposes BMC health
metrics on DBus in the same manner sensors are exposed.
Is this going to be a library or daemon, Same health-monitor daemon can
Be enhanced to add these functionalities.
- This implementation does not check health metric values against
thresholds or perform actions when thresholds are crossed.
If you don't define threshold in configuration file, health-monitor will
also not monitor metrics defined.
- This implementation currently reports uptime, memory usage, free
disk space, CPU time consumed by processes, and file descriptor stats.
Same can be added as extra metrics. That was the goal of this repo as to
start with basic metrics and add more as required.
- This implementation does not read a configuration file yet. It
always reads the hard-coded set of health metrics listed above.
We can enable or disable certain metrics through this configuration file.
- This implementation does not post-process sensor readings such as
compute the average CPU usage over a certain time window.
Window size 1 can give latest data rather than averaged data.
As such, this implementation differs enough from existing ones such
that we believe we have enough reasons to have a separate repository
for it.
I will strongly prefer to add all of the features in the existing repo.
Thanks!
next prev parent reply other threads:[~2020-10-01 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 15:27 Request to create repository google-ipmi-bmc-health Sui Chen
2020-10-01 19:05 ` Vijay Khemka [this message]
2020-10-02 1:52 ` Sui Chen
2020-10-02 20:54 ` Vijay Khemka
2020-10-06 22:57 ` Sui Chen
2020-10-07 1:43 ` Patrick Williams
2020-11-05 23:54 ` Sui Chen
2020-11-11 6:34 ` Vijay Khemka
2020-11-11 6:38 ` William Kennington
2020-11-11 12:14 ` Patrick Williams
2020-11-17 0:00 ` Sui Chen
2020-11-17 1:41 ` Patrick Williams
2020-11-18 8:48 ` Vijay Khemka
2020-11-18 23:06 ` Sui Chen
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=D355FA68-E163-4DA8-861E-7E9DB68F5EEB@fb.com \
--to=vijaykhemka@fb.com \
--cc=openbmc@lists.ozlabs.org \
--cc=suichen@google.com \
/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.