Proposal for Error Log triggered BMC Dump creation.

[Jayanth Othayoth]

Background:
Currently BMC dump is created based on one of the following
        * User Initiated
        * Application core
        * Error Log of type "Internal failures"
        * Host Checkstop (to be done)
..............................................................................
Extending Dump Infrastructure:
The existing Dump framework can be extended as follows to support new Dump
type
and/or new dump content:
1) Existing Dump type with existing plugin(s)
     * Annotate the plugin with the dump type.
2) Existing Dump type with new plugin(s)
     * Provide the plugin under plugins.d
     * Annotate the plugin with the dump type.
3) A new Dump type with existing plugins
     * Configure the new dump type in sample.conf
     * Annotate the plugin with the dump type.
4) A new Dump type with new plugin(s)
     * Configure the new dump type in sample.conf
     * Provide the plugin under plugins.d
     * Annotate the plugin with the dump type.
..............................................................................
Motivation & Proposal:
The current dump management framework allows to collect debug data upon a
User
request. Also additional debug data can be collected for internal failures
over
and above what is present in the Error Log. This proposal extends the
framework
to associate dump creation with specific Error logs.

The design guideline is to create a dump based on the Error code.  The
framework consists of a json based policy configuration which associates the
Error Log type with the corresponding Dump type. This framework provides the
flexibility to configure the dump collection behavior for an existing Error
Log
type and/or for new Error Log types introduced in future. For every Error
Log
type that must trigger a Dump, there must be configuration info int he json
policy file. The policy configuration is compiled binary config info which
will
be used by Dump Manager.
..............................................................................
~

~
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20180521/2fcf7cb6/attachment-0001.html>