Storing host data on the BMC
dkodihal at linux.vnet.ibm.com
Thu May 21 15:16:06 AEST 2020
On 21/05/20 10:42 am, Sunitha Harish wrote:
> Any inputs?
> Thanks & regards,
I believe you had got a direction based on the discussion below.
>>>> As far as Sunitha's question goes, my point is that not all host
>>>> firmware generated data is a BIOS attribute. For eg if the host
>>>> tells me
>>>> about the presence of certain FRUs, or their functional states, I
>>>> wouldn't want to store those in the BIOS attributes backend, I'd rather
>>>> associates those with the existing D-Bus interfaces for the FRU
>>>> inventory. I think the same applies to the Origin property that has
>>>> described - associate with the networking D-Bus backend.
>>> I think we're in agreement here. Data which is interesting to represent
>>> on the BMC, for which we already have a defined-interface, use it. For
>>> data which isn't interesting the to BMC, use the generic BIOS attribute
^^ You use existing (or come up with new) D-Bus interfaces to represent
your data. Those D-Bus interfaces can be implemented by settingsd or
networkd or something else.
More information about the openbmc