From: Ed Tanous <edtanous@google.com>
To: Thang Nguyen <thang@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Where to collect information for Redfish System's Processors, Storage, Memory data
Date: Wed, 17 Mar 2021 12:45:11 -0700 [thread overview]
Message-ID: <CAH2-KxCUYzjckT7xEAtcdV4Q_2h4B7GdAcXw_TTqBA6O76Q7Ng@mail.gmail.com> (raw)
In-Reply-To: <925a9eba-db8f-fba0-7d17-db32860c44ba@os.amperecomputing.com>
On Tue, Mar 16, 2021 at 3:22 AM Thang Nguyen
<thang@os.amperecomputing.com> wrote:
>
> Hi,
>
> I am looking for how to support Redfish System schema which information
> from Host:
>
> - Processors: redfish/v1/Systems/system/Processors
>
> - Storage: redfish/v1/Systems/system/Storage
>
> - Memory: redfish/v1/Systems/system/Memory
>
> I looked into the bmcweb repository at redfish-core/lib/memory.hpp and
> redfish-core/lib/pcie.hpp but just see doGet() function to read data
> from dbus to report via Redfish. There is no doPost() function to post
> codes to Redfish.
Today, there's no way to do this sort of Redfish POST/PATCH for normal
BIOS use cases. I'm working on a design doc for how to add this (via
redfish host interface) to bmcweb. If you have any ideas here for how
this should work, or requirements for what you're trying to do,
please, share.
>
> My questions are:
>
> 1. How can Host BIOS collect information and send to BMC so that BMC can
> report via Redfish? via in-band Redfish?
>
> 2. If the information is not from BIOS, how can BMC collect information?
> What recipes/repositories are used to collect information?
>
>
> Thanks,
>
> Thang Q. Nguyen -
>
next prev parent reply other threads:[~2021-03-17 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 10:22 Where to collect information for Redfish System's Processors, Storage, Memory data Thang Nguyen
2021-03-17 19:26 ` Ren, Zhikui
2021-03-18 7:40 ` Thang Nguyen
2021-03-18 20:08 ` Ren, Zhikui
2021-03-18 20:10 ` Ren, Zhikui
2021-03-17 19:45 ` Ed Tanous [this message]
2021-03-18 8:25 ` Thang Nguyen
2021-03-18 16:07 ` Ed Tanous
2021-03-19 2:13 ` Thang Nguyen
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=CAH2-KxCUYzjckT7xEAtcdV4Q_2h4B7GdAcXw_TTqBA6O76Q7Ng@mail.gmail.com \
--to=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=thang@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).