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.
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.
Thank you, -AdamM
[0] - https://github.com/maxamillion/loopabull [1] - https://pagure.io/releng-automation [2] - https://pagure.io/releng/pull-request/6804#request_diff [3] - https://github.com/openstack/ara
On Mon, Jun 5, 2017 at 11:33 AM, Adam Miller maxamillion@fedoraproject.org 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.
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.
Thread bump. :)
-AdamM
Thank you, -AdamM
[0] - https://github.com/maxamillion/loopabull [1] - https://pagure.io/releng-automation [2] - https://pagure.io/releng/pull-request/6804#request_diff [3] - https://github.com/openstack/ara
On Mon, Jun 05, 2017 at 11:33:12AM -0500, Adam Miller wrote:
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.
Pardon the ignorant question, but: fedmsg/datagrepper/fednotify not sufficient?
On Mon, Jun 12, 2017 at 11:05 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, Jun 05, 2017 at 11:33:12AM -0500, Adam Miller wrote:
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.
Pardon the ignorant question, but: fedmsg/datagrepper/fednotify not sufficient?
I was hoping for more verbose logs of the ansible run.
-AdamM
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
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?
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?
Or using the logdetail2 callback plugin we have on batcave01/ansible repo and just logging to files locally on loopabull01?
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.
kevin
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@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@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
On 06/14/2017 09:12 AM, Adam Miller wrote:
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@scrye.com 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.
Who knows, perhaps one day we could use ansible tower for this. ;)
kevin
On Thu, Jun 15, 2017 at 10:24 AM, Kevin Fenzi kevin@scrye.com wrote:
On 06/14/2017 09:12 AM, Adam Miller wrote:
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@scrye.com 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.
Who knows, perhaps one day we could use ansible tower for this. ;)
That sure would be nice, if only Ansible were acquired by a company that was committed to open sourcing it. ;)
-AdamM
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
On Thu, Jun 15, 2017 at 2:41 PM, Adam Miller maxamillion@fedoraproject.org wrote:
On Thu, Jun 15, 2017 at 10:24 AM, Kevin Fenzi kevin@scrye.com wrote:
On 06/14/2017 09:12 AM, Adam Miller wrote:
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@scrye.com 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. :)
Who knows, perhaps one day we could use ansible tower for this. ;)
That sure would be nice, if only Ansible were acquired by a company that was committed to open sourcing it. ;)
-AdamM
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
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@fedoraproject.org wrote:
On Thu, Jun 15, 2017 at 10:24 AM, Kevin Fenzi kevin@scrye.com wrote:
On 06/14/2017 09:12 AM, Adam Miller wrote:
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@scrye.com 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.
kevin
On Mon, Jun 26, 2017 at 5:53 PM, Kevin Fenzi kevin@scrye.com 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@fedoraproject.org wrote:
On Thu, Jun 15, 2017 at 10:24 AM, Kevin Fenzi kevin@scrye.com wrote:
On 06/14/2017 09:12 AM, Adam Miller wrote:
On Mon, Jun 12, 2017 at 2:48 PM, Kevin Fenzi kevin@scrye.com 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@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
infrastructure@lists.fedoraproject.org