Read FRU of host through ipmi in Entity manager.

[Thomaiyar, Richard Marian]

Hi Kumar,

Better to expose IPMI FRU of the host read via IPMB through FRU 
Interface (i.e. say xyz.openbmc_project.IPMB.FruDevice daemon, which can 
expose all the FRU's read through the same). In this way, current 
EntityManager probe will still work. (Note: We can add the support in 
FRUDevice if it is IPMB read of raw FRU data, so that conversion code in 
FRUDevice can still be used).

Current plan (under discussion - Needs to finalize) to expose the PLDM 
FRU in separate daemon under interface 
(https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Inventory/Source/PLDM) 


James, Do you see any issue with this approach / comments ?

Regards,
Richard

On 9/14/2020 10:25 PM, Kumar Thangavel wrote:
>
> Classification: *HCL Internal*
>
> Hi All,
>
>          We are working on the Platform which has multi host and the 
> host are FRUs.  The host and BMC communication is based on IPMB. We 
> have each host is connected in separate ipmb bus.
>
>          Existing Entity manager has the FRU read info from EEPROM 
> (I2C)in the form of bin file.
>          We understand that entity manager does not support ipmb based 
> host fru.
>
>          So, we are proposing the design to support ipmb based FRU in 
> entity manager.
>          From Entity manager, we will send the generic "read host fru" 
> command request to ipmbbrige to read the host FRU.
>
>          Then, store the host fru info in the bin file to process and 
> creating dbus objects in the entity manager.
>
>          Please let us know your comments on this.
>
> Thanks,
>
> Kumar.
>
> ::DISCLAIMER::
> ------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be 
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> may contain viruses in transmission. The e mail and its contents (with 
> or without referred errors) shall therefore not attach any liability 
> on the originator or HCL or its affiliates. Views or opinions, if any, 
> presented in this email are solely those of the author and may not 
> necessarily reflect the views or opinions of HCL or its affiliates. 
> Any form of reproduction, dissemination, copying, disclosure, 
> modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL 
> is strictly prohibited. If you have received this email in error 
> please delete it and notify the sender immediately. Before opening any 
> email and/or attachments, please check them for viruses and other defects.
> ------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200914/09c8c832/attachment-0001.htm>