Progress Codes in BMC

[Brad Bishop]

On Sat, Jan 30, 2021 at 08:31:26AM -0600, Patrick Williams wrote:
>On Wed, Jan 27, 2021 at 08:05:26PM -0500, Brad Bishop wrote:
>>
>> There are multiple sources of the codes - on Power the power sequencing
>> is done on the BMC and that is considered part of the server boot so we
>> have both those applications indicating their progress along with the
>> more traditional progress flowing down from system firmware.
>
>The `xyz.openbmc_project.State.Boot.Raw` is the interface to use here.
>You just write the `Value` property.  

Ok.  Do I have it right - on any application that wants to post a 
"progress code" you would just implement this interface on a single 
(arbitrary?) path and continually write to the Value property?

>> Our progress codes are much larger than 64 bits.  More like 64 bytes.
>> Does that still seem acceptable?
>
>Maybe we could change Value from a uint64 to a vector<uint64>?

Works for me.  Does anyone have a problem with this?  Hoping the 
existing users of this interface will speak up - I've CCed them...

>> I'd also like to sort out the external facing interfaces for these codes
>> though.  My straw-man proposal would be that these are just another log
>> service with yet another additionaldatauri attachment in the log
>> entries.  Is this a terrible idea?
>
>I think you're asking about Redfish now?  I have no opinion on that.

Yes I'm asking about Redfish.  If any of the bmcweb maintainers could 
speak up on whether or not a LogService is the right path to take here 
_before_ we get too far down the design path that would be fantastic.

thx - brad