On Mon, Jun 26, 2017 at 5:53 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > Didnt copy the list because thunderbird is stupid now. :( > > On 06/22/2017 04:06 PM, Adam Miller wrote: >> On Thu, Jun 15, 2017 at 2:41 PM, Adam Miller >> <maxamillion@xxxxxxxxxxxxxxxxx> wrote: >>> On Thu, Jun 15, 2017 at 10:24 AM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: >>>> On 06/14/2017 09:12 AM, Adam Miller wrote: >>>>> On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: >>>> ...snip.. >>>> >>>>>> How about logging to syslog and viewing that on log01? >>>>> >>>>> That's find with me, is that publicly viewable without credentials? >>>> >>>> nope. You need to have ssh access to log01 to read those. >>>> >>>>>> 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. >>>> >>>> Cool, well, I suggest for now just log locally/syslog and we can look at >>>> a better interface down the road. >>>> >>> >>> +1 - Will do, are there any security/infra policies about allowing >>> logs to be accessible to the public? I'd like to just let apache serve >>> them up for easy presentation. >> >> Thread bump. :) > > There isn't currently, but I would be very wary of just publishing > ansible logs directly to the public... > > I'd say don't worry about it for the first cut of things, and look at > adding something in later after more thought. Awesome, thanks! -AdamM > > kevin > > > > > > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
