Redfish Dump Service Proposal

[Gunnar Mills]

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 gmail.com> 
>>>> wrote:
>>>>>
>>>>> On Sat, Dec 14, 2019 at 1:32 AM Bills, Jason M
>>>>> <jason.m.bills at linux.intel.com> 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 
https://redfish.dmtf.org/schemas/Memory.v1_8_0.json

Reason seems similar to the LogEntryCode from 
https://redfish.dmtf.org/schemas/LogEntry.v1_5_0.json

Slide 15:
"Size": 108944B
Redfish size properties typically have the unit in the name. E.g. From 
https://redfish.dmtf.org/schemas/Memory.v1_8_0.json CacheSizeMiB or 
CapacityMiB.

odata.context is getting dropped. See 
https://github.com/DMTF/Redfish/issues/2722 or 
https://github.com/DMTF/Redfish/commit/ae49f4fb1278fd435f89317c3fa53cac597e3893#diff-e82b4876efbeaa600d3b104a426f7ac5 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200109/9be4a5f7/attachment.htm>