Hi Is there a way to parse the yaml reports on locally on the puppet clients. What I''d like to offer our sysadmins is a command that will give them some info when the last puppetrun was and whether anything has changed. This could be included in .profile/.bashrc. We have an environment where admins look after a their "own" machines. And it is new that something like puppet ist allowed to interfer with "their" systems so we are slowly getting used to the new situation. I do hope that we will eventually move to a centralized reporting UI. We''re just not that far yet. Thanks for any help Chris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
hello, ----- "Chris" <sinloft@gmail.com> wrote:> Hi > > Is there a way to parse the yaml reports on locally on the puppet > clients. What I''d like to offer our sysadmins is a command that will > give them some info when the last puppetrun was and whether anything > has changed. This could be included in .profile/.bashrc. We have an > environment where admins look after a their "own" machines. And it is > new that something like puppet ist allowed to interfer with "their" > systems so we are slowly getting used to the new situation. I do hope > that we will eventually move to a centralized reporting UI. We''re > just > not that far yet.I made a feature request so the report gets saved locally http://projects.reductivelabs.com/issues/4339 not sure how you''d get this information today -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
You could always have a script that queries the puppetmaster or whatever your report server is. I''d just use https. Have some cgi script that grabs the latest yaml file for the requesting host and then returns it. The requesting script on the client can then parse it and do whatever with it. You could get crazy and cache the report locally but you''d need some way of dirtying it after each puppet run. I don''t think there''s any security implications in that. You shouldn''t have any sensitive data in your reports unless you log the output of Execs that contain passwords. On Aug 22, 2010, at 8:52 AM, Chris <sinloft@gmail.com> wrote:> Hi > > Is there a way to parse the yaml reports on locally on the puppet > clients. What I''d like to offer our sysadmins is a command that will > give them some info when the last puppetrun was and whether anything > has changed. This could be included in .profile/.bashrc. We have an > environment where admins look after a their "own" machines. And it is > new that something like puppet ist allowed to interfer with "their" > systems so we are slowly getting used to the new situation. I do hope > that we will eventually move to a centralized reporting UI. We''re just > not that far yet. > > > Thanks for any help > > > Chris > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Puppet logs to syslog so why not setup an alias that just runs "grep puppet /var/log/messages". The log file may differ between distributions (daemon.log for Debian), but this generally suffices for me. On 23 August 2010 00:20, Carl.caum <carl.caum@gmail.com> wrote:> You could always have a script that queries the puppetmaster or whatever your report server is. I''d just use https. Have some cgi script that grabs the latest yaml file for the requesting host and then returns it. The requesting script on the client can then parse it and do whatever with it. You could get crazy and cache the report locally but you''d need some way of dirtying it after each puppet run. > I don''t think there''s any security implications in that. You shouldn''t have any sensitive data in your reports unless you log the output of Execs that contain passwords. > > On Aug 22, 2010, at 8:52 AM, Chris <sinloft@gmail.com> wrote: > >> Hi >> >> Is there a way to parse the yaml reports on locally on the puppet >> clients. What I''d like to offer our sysadmins is a command that will >> give them some info when the last puppetrun was and whether anything >> has changed. This could be included in .profile/.bashrc. We have an >> environment where admins look after a their "own" machines. And it is >> new that something like puppet ist allowed to interfer with "their" >> systems so we are slowly getting used to the new situation. I do hope >> that we will eventually move to a centralized reporting UI. We''re just >> not that far yet. >> >> >> Thanks for any help >> >> >> Chris >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Christopher Johnston
2010-Aug-22 23:23 UTC
Re: [Puppet Users] Parsing yaml report locallly
Great idea Sent from my iPhone On Aug 22, 2010, at 9:58 AM, "R.I.Pienaar" <rip@devco.net> wrote:> hello, > > ----- "Chris" <sinloft@gmail.com> wrote: > >> Hi >> >> Is there a way to parse the yaml reports on locally on the puppet >> clients. What I''d like to offer our sysadmins is a command that will >> give them some info when the last puppetrun was and whether anything >> has changed. This could be included in .profile/.bashrc. We have an >> environment where admins look after a their "own" machines. And it is >> new that something like puppet ist allowed to interfer with "their" >> systems so we are slowly getting used to the new situation. I do hope >> that we will eventually move to a centralized reporting UI. We''re >> just >> not that far yet. > > I made a feature request so the report gets saved locally http://projects.reductivelabs.com/issues/4339 not sure how you''d get this information today > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Thanks, I saw that the request was accepted. So there will be solution in the future -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
True, this seems to be the easiest way to do it. Thanks On 23 Aug., 00:59, Tim Sharpe <t...@sharpe.id.au> wrote:> Puppet logs to syslog so why not setup an alias that just runs "grep > puppet /var/log/messages". The log file may differ between > distributions (daemon.log for Debian), but this generally suffices for > me. > > On 23 August 2010 00:20, Carl.caum <carl.c...@gmail.com> wrote: > > > > > You could always have a script that queries the puppetmaster or whatever your report server is. I''d just use https. Have some cgi script that grabs the latest yaml file for the requesting host and then returns it. The requesting script on the client can then parse it and do whatever with it. You could get crazy and cache the report locally but you''d need some way of dirtying it after each puppet run. > > I don''t think there''s any security implications in that. You shouldn''t have any sensitive data in your reports unless you log the output of Execs that contain passwords. > > > On Aug 22, 2010, at 8:52 AM, Chris <sinl...@gmail.com> wrote: > > >> Hi > > >> Is there a way to parse the yaml reports on locally on the puppet > >> clients. What I''d like to offer our sysadmins is a command that will > >> give them some info when the last puppetrun was and whether anything > >> has changed. This could be included in .profile/.bashrc. We have an > >> environment where admins look after a their "own" machines. And it is > >> new that something like puppet ist allowed to interfer with "their" > >> systems so we are slowly getting used to the new situation. I do hope > >> that we will eventually move to a centralized reporting UI. We''re just > >> not that far yet. > > >> Thanks for any help > > >> Chris > > >> -- > >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. > >> To post to this group, send email to puppet-users@googlegroups.com. > >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > >> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Thank you for your suggestion, we would have to get the permission for an extra open port on our firewalls. That will take some time, so I will probably go with Tims proposal On 22 Aug., 16:20, "Carl.caum" <carl.c...@gmail.com> wrote:> You could always have a script that queries the puppetmaster or whatever your report server is. I''d just use https. Have some cgi script that grabs the latest yaml file for the requesting host and then returns it. The requesting script on the client can then parse it and do whatever with it. You could get crazy and cache the report locally but you''d need some way of dirtying it after each puppet run. > I don''t think there''s any security implications in that. You shouldn''t have any sensitive data in your reports unless you log the output of Execs that contain passwords. > > On Aug 22, 2010, at 8:52 AM, Chris <sinl...@gmail.com> wrote: > > > > > Hi > > > Is there a way to parse the yaml reports on locally on the puppet > > clients. What I''d like to offer our sysadmins is a command that will > > give them some info when the last puppetrun was and whether anything > > has changed. This could be included in .profile/.bashrc. We have an > > environment where admins look after a their "own" machines. And it is > > new that something like puppet ist allowed to interfer with "their" > > systems so we are slowly getting used to the new situation. I do hope > > that we will eventually move to a centralized reporting UI. We''re just > > not that far yet. > > > Thanks for any help > > > Chris > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.