Redfish Dump Service Proposal

[Jayanth Othayoth]

Dump is an additional debug data associated  to an error event.
>From the phosphor-debug-collector  perspective,  BMC Dump collects
additional debug information, which canot be contained in the error log.
Please find my comments inline.

On Fri, Dec 13, 2019 at 6:27 AM Richard Hanley <rhanley at google.com> wrote:

> Hi Ratan,
>
> I think this service is a really good idea.  A couple of thoughts:
>
> 1) I don't think the semantics around the Download action are consistent.
> Generally actions are reserved for stateful changes, and only have post
> methods.  I think this could be simplified by putting an @odata.id in the
> Dump resource that points to the raw dump file.  Then clients can do a
> normal HTTP get on that URL.
>
> 2) I'm wondering what is the best way to communicate what MIME type the
> raw dump supports.  In theory that could be a part of the RawDump
> resource.  However, a case could be made that it should be put into the
> Dump resource.
>
> 3) Perhaps the dump service should be embedded into other resources,
> instead of being a top level service.  I'm imagining something like how the
> LogService is setup.  That way there are a lot fewer dumpTypes for any
> particular instance of the service.
>    a) This could be taken to the extreme, and the DumpService could be
> integrated with the existing LogServices.  This would mean adding in a new
> log type, and having a new action.
>


> +Agree with this suggestion to embedding dump under log service as new
> EventType.  Also need an association  for each system generated dump with
> an error event.
>

> 4) It might be a good idea to have some event support in the cases where a
> dump is created because of a machine crash.
>
> Regards,
> Richard
>
> On Wed, Dec 11, 2019 at 11:08 PM Devender Rao <devenrao at in.ibm.com> wrote:
>
>> Over all the schema looks good. Few observations for clarity, also how
>> about we have multiple collection say HostDumpCollection, BMCDumpCollection
>>  and also a new service DumpLocations similar to "CertificateLocations"
>>
>> Page 17: Dump Creation flow
>> 1. The time line diagram should show that "Request to create dump" return
>> immediatley. The redfish client will be notififed asynchronously when the
>> dump is collected through DumpCollected event. Request for dump with
>> resource id should be in the same time line when it gets notified of Dump
>> collection completed.
>>
>> Page 19: For clarity
>> "List Dumps" should be shown as part of DumpColletion rather than under
>> "Operations on dump"
>> "Get Dump details" should be shown under dump service
>> "Delete Dumps" should be shown under DumpService
>>
>>
>> ----- Original message -----
>> From: Ratan Gupta <ratagupt at linux.vnet.ibm.com>
>> Sent by: "openbmc" <openbmc-bounces+devenrao=in.ibm.com at lists.ozlabs.org>
>> To: "openbmc at lists.ozlabs.org" <openbmc at lists.ozlabs.org>
>> Cc:
>> Subject: [EXTERNAL] Redfish Dump Service Proposal
>> Date: Thu, Dec 12, 2019 5:09 AM
>>
>> Hi All,
>>
>> Please find the redfish dump service proposal for the DMTF attached.
>>
>> Kindly review and provide your inputs.
>>
>> Ratan
>>
>>
>>
>>
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20191213/8aea77de/attachment.htm>