openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: George Liu <liuxiwei1013@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Request new repo for Audit function
Date: Mon, 16 Aug 2021 09:25:24 -0500	[thread overview]
Message-ID: <YRp1VMAJ6TcDzTz5@heinlein> (raw)
In-Reply-To: <CANFuQ7AOMpqhpa_Upn5toNeSDzZK_TADbc4ikqjbZBjmrMoBSA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Fri, Aug 13, 2021 at 08:51:32AM +0800, George Liu wrote:
> Hi Brad:
> 
> We have a requirement to implement an Audit function, I found that
> there is a design doc[1], but there is no code to implement it.
> 
> Could you create a new repo for Audit function?
> eg: phosphor-audit
> 
> [1]: https://github.com/openbmc/docs/blob/master/designs/phosphor-audit.md
> 
> thx - George Liu

George,

Are you planning to implement the design as-is?  It has been quite a while since
this design was proposed and it feels to me like there may be some overlap with
the Redfish logging proposal[1].

With how old this design doc is, I think we should have an update / re-review
of it.  If you are willing to take on this development effort, could you replace
yourself as the "Primary Assignee" and make any necessary updates?

1. https://github.com/openbmc/docs/blob/master/architecture/redfish-logging-in-bmcweb.md


-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-08-16 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  0:51 George Liu
2021-08-16 14:25 ` Patrick Williams [this message]
2021-08-17  0:51   ` George Liu
2021-08-13  3:21 Milton Miller II
2021-08-13  6:09 ` George Liu
2021-08-13  8:41   ` Ivan Mikhaylov
2021-08-13  9:14     ` George Liu

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=YRp1VMAJ6TcDzTz5@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=liuxiwei1013@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --subject='Re: Request new repo for Audit function' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).