add multi-host support in the phosphor-post-code-manager

[Manikandan]

On Tue, Jul 21, 2020 at 05:10:04PM +0000, Ren, Zhikui wrote:
> I would think that one process to handle all post-code is a cleaner design.

   Thanks Ren for comments.

   As Patrick mentioned on different hardware toplogy and hot-plug-able 
   concept matches with our platform.
 
   As per my undersatnd on recent multi-host feature such as  
   obmc-console, host-logger and x86-power-control implemented based on the multi-process.

   I will update design doc in Gerrit to discuss to further on single or multi-host approach. 
 
> 
> -----Original Message-----
> From: openbmc <openbmc-bounces+zhikui.ren=intel.com at lists.ozlabs.org> On Behalf Of Manikandan
> Sent: Monday, July 20, 2020 9:00 AM
> To: openbmc at lists.ozlabs.org
> Cc: Wang, Kuiying <kuiying.wang at intel.com>; velumanit at hcl.com; manikandan.e at hcl.com
> Subject: add multi-host support in the phosphor-post-code-manager
> 
> Hi All,
> 
>  We woukld like to get opion on below multi-host support approaches.
> 
> Background :
> ------------
>   The Phosphor-post-code-manager supports only host to store/retrieve the host postcode history.
> 
> Approaches:
> -----------
> Approach 1: << run the multiple process >>
> 
> Create and run the multiple phosphor-post-code-manager process to handle each host postcode history.
> 
>    xyz.openbmc_project.State.Host0.Boot.PostCode
>    xyz.openbmc_project.State.Host1.Boot.PostCode
>    xyz.openbmc_project.State.Host2.Boot.PostCode
>    xyz.openbmc_project.State.Host3.Boot.PostCode
> 
> Approach 2: << pass number of host to single process >>
> 
> Pass number of host to single process phosphor-post-code-manager to register dbus object and handle each host postcode.
> 
>    xyz.openbmc_project.State.Host0.Boot.PostCode
>    xyz.openbmc_project.State.Host1.Boot.PostCode
>    xyz.openbmc_project.State.Host2.Boot.PostCode
>    xyz.openbmc_project.State.Host3.Boot.PostCode
> 
> 
> Thanks
> Mani.E