Redfish Dump Service Proposal

Gunnar Mills gmills at
Fri Jan 10 07:07:19 AEDT 2020

A couple comments.

On 1/7/2020 2:08 PM, Bills, Jason M wrote:
> On 1/7/2020 2:11 AM, Ratan Gupta wrote:
>>>> On Sat, Dec 14, 2019 at 10:57 AM dhruvaraj S <dhruvaraj at> 
>>>> wrote:
>>>>> On Sat, Dec 14, 2019 at 1:32 AM Bills, Jason M
>>>>> <jason.m.bills at> wrote:
>>>>>> I like this as well.  I'm trying to support a CPU crashdump that 
>>>>>> would
>>>>>> fit perfectly with this proposal.
>>>>>> A question and some comments below:
>>>>>> Will Dump only have the two types: BMC and Host?  Could this be more
>>>>>> flexible to allow for multiple different types of dumps from various
>>>>>> components?
>>>>> + I think dump types should be flexible to cover different types of
>>>>> host or bmc dumps from different components with varying formats.
>> Sure we can enhance the type of dump, it is enum in the proposal 
>> which can be enhanced.
>> What could be other dump type which I can add in the types?

Slide 15:  Since DumpType is an enum, should reason be as well? "Type" 
is a pretty typical enum in Redfish. E.g. BaseModuleType from

Reason seems similar to the LogEntryCode from

Slide 15:
"Size": 108944B
Redfish size properties typically have the unit in the name. E.g. From CacheSizeMiB or 

odata.context is getting dropped. See or 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openbmc mailing list