Storing host data on the BMC
patrick at stwcx.xyz
Mon May 11 22:07:19 AEST 2020
Intel has already made significant progress on this problem domain and
we seem to be fairly converged on the design direction [1,2]. Have you
read through their design proposal? Are there any oversights in their
design that would affect your needs?
Their design has been on-going for months now. I don't think it is
appropriate to start from scratch on the design discussions unless there
is something fundamentally broken about their direction.
I thought there was even some implementation started in bmcweb for this
On Mon, May 11, 2020 at 11:44:35AM +0530, Sunitha Harish wrote:
> Gentle reminder for the feedback.
> Thanks & regards,
> On 06-05-2020 12:53, Sunitha Harish wrote:
> > Hi Deepak,
> > Please suggest which other approach you think is better here for
> > Origin attribute?
> > When the interface is set as DHCPEnabled=true ; similar to the Origin
> > attribute , the IP address, SubnetMask and Gateway will be set by the
> > host. So we would need to consider this usecase also as a candidate
> > for the new approach.
> > Thanks & regards,
> > Sunitha
> > On 05-05-2020 12:29, Deepak Kodihalli wrote:
> >> On 05/05/20 12:12 pm, Sunitha Harish wrote:
> >>> Hi Deepak,
> >>> As mentioned , the Origin is the property which will be set by the
> >>> host once the IP address is applied to its interface. Its a
> >>> read-only property for the out-of-band user. But its a closely
> >>> coupled - related attribute on the host setting/BIOS object.
> >> Hi Sunitha,
> >> What I'm trying to say is - we shouldn't make this coupling. The BIOS
> >> settings table is a group of attributes that can alter the default
> >> behavior of the host firmware. The Origin property you describe
> >> doesn't fit that description.
> >> The host "sets" several things for the BMC, for eg the host firmware
> >> can tell us functional/presence states of FRUs which the host has
> >> access to. Everything that the host "sets" this way isn't a BIOS
> >> attribute. Once you decouple this, I believe we can think about
> >> options other than the two you have suggested - since both of them
> >> involve making the Origin property seem like a BIOS attribute, which
> >> it clearly is not.
> >> Thanks,
> >> Deepak
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the openbmc