On Thursday, December 6, 2012 10:07:43 PM UTC, John Warburton wrote:
> On 6 December 2012 20:29, Luke Bigum <luke....@lmax.com <javascript:>>wrote:
>
>> 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?
>>
>> 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 want
>
> % wget http://localhost:3000/nodes.csv
>
>
Thanks John and Ohad,
I use Puppet Dashboard but I've never tried that control before ;-) That
should do as a very good start.
Cheers,
-Luke
--
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/-/VIHTWkFeoQQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
