Where to collect information for Redfish System's Processors, Storage, Memory data

[Ed Tanous]

On Thu, Mar 18, 2021 at 1:26 AM Thang Nguyen
<thang at 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 at 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?

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