openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thang Nguyen <thang@os.amperecomputing.com>
To: Ed Tanous <edtanous@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Where to collect information for Redfish System's Processors, Storage, Memory data
Date: Fri, 19 Mar 2021 09:13:48 +0700	[thread overview]
Message-ID: <a1063850-c42c-ccbc-e3b1-34211f6e766a@os.amperecomputing.com> (raw)
In-Reply-To: <CAH2-KxDv8jgFP8gRQgGkKruUk-scUOr5Mja6NkTgO4ODGGnmvA@mail.gmail.com>


On 18/03/2021 23:07, Ed Tanous wrote:
> On Thu, Mar 18, 2021 at 1:26 AM Thang Nguyen
> <thang@os.amperecomputing.com> wrote:
>>
>> On 18/03/2021 02:45, Ed Tanous wrote:
>>> 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.
>> I checked on the Redfish Schema Supplement document and saw attributes
>> from the Memory, Pcie, ... schema are read-only. It means no POST/PATCH
>> action is supported now.
>>
>> How's about suggesting on supporting POST/PATCH action with the needed
>> information change to read-write? UEFI will then collect data and send
>> Redfish commands via the Redfish Host Interface.
>
> That's effectively what I'm hoping to propose.  ar ethe Memory and
> PCIe schemas the only things you need?

I think the following information should be sent from UEFI: CPU 
(information in SMBIOS type 4)), Memory, PCIE, Storage (SSD/NVMe, HDD, 
...) and firmware information (information in SMBIOS Type 0).

I see in some hardware designs, there are I2C connections from BMC to 
DIMM SPD and PCIE slots. I wonder if we can have alternative way to read 
DIMM SPD and PCIE devices information.

>
>>>> 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 -
>>>>

      reply	other threads:[~2021-03-19  2:14 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
2021-03-18  8:25   ` Thang Nguyen
2021-03-18 16:07     ` Ed Tanous
2021-03-19  2:13       ` Thang Nguyen [this message]

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=a1063850-c42c-ccbc-e3b1-34211f6e766a@os.amperecomputing.com \
    --to=thang@os.amperecomputing.com \
    --cc=edtanous@google.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 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).