--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Fcx6zByYGPQJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
You could use foreman for that? filtering the hosts via search should allow you to find the exact resources you are looking for?Ohad
On Wednesday, December 5, 2012 12:50:43 PM UTC, ohad wrote:
You could use foreman for that? filtering the hosts via search should allow you to find the exact resources you are looking for?OhadHi Ohad,I haven't looked at The Foreman in a while but in my mind it's more like Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool that can aid change / release management where we run Puppet --noop across the estate, gather all the reports, then summarise what changes will be applied (resolv.conf changes on all hosts, fstab changes on 20 hosts, service X refreshes on Y hosts).
I don't really want to be searching for explicit resources changing across hosts, it's the resources I don't know about that worry me ;-) Is the foreman worth a look in this case?-LukeHi all,Can anyone recommend any tools for Puppet report aggregation? I'm interested in something that can take a given set of Puppet reports and summarise to me what resources have changed across all hosts.If nothing exists I will look to write one myself. In that case, is Puppet report format 3 valid for Puppet 3.0?
http://projects.puppetlabs.com/projects/puppet/wiki/Report_Format_3
Thanks,-Luke--To post to this group, send email to puppet...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Fcx6zByYGPQJ.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/zk_ospPVmYkJ.
I haven't looked at The Foreman in a while but in my mind it's more like Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool that can aid change / release management where we run Puppet --noop across the estate, gather all the reports, then summarise what changes will be applied (resolv.conf changes on all hosts, fstab changes on 20 hosts, service X refreshes on Y hosts).I don't really want to be searching for explicit resources changing across hosts, it's the resources I don't know about that worry me ;-) Is the foreman worth a look in this case?
On 6 December 2012 20:29, Luke Bigum <Luke....@lmax.com> wrote:Luke, we use the puppet dashboard which aggregates all the reports and then lets us suck down a CSV ("Export nodes as CSV" on front page) which contains a status of all resources on all machine reporting. We run puppet in noop all the time, so need similar reports you are requesting. It is just a matter of slicing & dicing the csv to get what you wantI haven't looked at The Foreman in a while but in my mind it's more like Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool that can aid change / release management where we run Puppet --noop across the estate, gather all the reports, then summarise what changes will be applied (resolv.conf changes on all hosts, fstab changes on 20 hosts, service X refreshes on Y hosts).I don't really want to be searching for explicit resources changing across hosts, it's the resources I don't know about that worry me ;-) Is the foreman worth a look in this case?
% wget http://localhost:3000/nodes.csv