On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
On 06/05/2017 10:33 AM, Adam Miller wrote:
> Hello all,
> I am in need of a publicly accessible location to have logs hosted
> (or mirrored) from loopabull[0] in order to provide public-facing
> feedback on what's actually going on with the automated tasks.
Who is the audience here? Sysadmins that want to confirm the playbook
ran the way they wanted?
Yes, or anyone in the community who wants to see what the auto-fu is
up to and what's actually happening.
> For background/context, there are docs what loopabull is[0] and how
> Fedora RelEng is currently aiming to use it[1][2].
>
> If it's acceptable, I would like to use OpenStack's Project ARA[3] for
> this but that is "yet another service" and if there's something
> readily available from the Fedora Infrastructure then I'd certainly
> like to go that route. I'm also completely open to alternative
> solutions, whatever the Fedora Infrastructure Team thinks it best.
How about logging to syslog and viewing that on log01?
That's find with me, is that publicly viewable without credentials?
Or using the logdetail2 callback plugin we have on batcave01/ansible
repo and just logging to files locally on loopabull01?
That would also work.
Is there a requirement for a pretty web interface? We can do that, it's
just going to take some cycles to make sure we don't expose anything we
shouldn't and do it right.
There is not, it would just be nice to have.
Thanks,
-AdamM
>
> kevin
>
>
>
>
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
>