All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Fair <benjaminfair@google.com>
To: Jayashree D <jayashree-d@hcl.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"Velumani T-ERS, HCLTech" <velumanit@hcl.com>
Subject: Re: Rsyslog using Redfish
Date: Tue, 22 Jun 2021 11:19:03 -0700	[thread overview]
Message-ID: <CADKL2t7rCZ2QYBQfvybYtaoZdKDFoPnJzwr8td_4Qg_=gtv4MA@mail.gmail.com> (raw)
In-Reply-To: <SG2PR04MB3093DD642B1D80C03EFBAF91E1099@SG2PR04MB3093.apcprd04.prod.outlook.com>

On Tue, 22 Jun 2021 at 10:18, Jayashree D <jayashree-d@hcl.com> wrote:
>
> Classification: Public
>
>
>
> Hi Ben,
>
>
>
> I submitted the below patch in gerrit regarding rsyslog for my platform.
>
> meta-facebook: Add rsyslog for yosemitev2. (Ife76252d) · Gerrit Code Review (openbmc-project.xyz)
>
>
>
> Also, there are few patches in gerrit for rsyslog which you have submitted.
>
> https://gerrit.openbmc-project.xyz/q/topic:%22rsyslog-refactor%22+(status:open%20OR%20status:merged)
>
> Whether these patches will be enough to store the event logs in redfish ?
>
> or any other changes needs to be done for my platform.
>
>
>
> Thanks,
>
> Jayashree
>

Hi Jayashree,

I'm working on restructuring the rsyslog configs so that the Redfish
rsyslog actions can be installed from bmcweb and the IPMI ones from
phosphor-sel-logger. Once this is done, you'll be able to enable a
PACKAGECONFIG option instead of having to copy and paste the
rsyslog.conf file into your layer.

If you'd like to help with this refactoring, you can review the
changes in the rsyslog-refactor topic starting with this prerequisite:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-logging/+/44109

Thanks,
Benjamin

  reply	other threads:[~2021-06-22 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 17:18 Rsyslog using Redfish Jayashree D
2021-06-22 18:19 ` Benjamin Fair [this message]
2021-06-24  7:24   ` Jayashree D

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADKL2t7rCZ2QYBQfvybYtaoZdKDFoPnJzwr8td_4Qg_=gtv4MA@mail.gmail.com' \
    --to=benjaminfair@google.com \
    --cc=jayashree-d@hcl.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=velumanit@hcl.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.