Douglas,
I have to concur with disconnect, now that we are using Foreman, many
of the things we setup in the past to catch these things are now
redundant. I don't know why you "don't like" Foreman, but I have to
say along with our initial decision to use puppet, and managing our
configs with version control, adopting Foreman stands up there as one
of our big infrastructure management wins. (And we aren't even
using Foreman's provisioning capabilities).
May I ask why you don't like Foreman? (We were for a long time
hesitant to use Foreman, as it wasn't an "official" project, but we
had reached a point where we needed a new ENC, and a technical
evaluation of both Foreman and Dashboard lead us to the realization
that functionality-wise it was a lot closer to what we needed. (And I
suspect your needs may be similar to ours.)
Cheers,
Brian
On Wed, May 25, 2011 at 1:54 PM, Disconnect <dc.disconn...@gmail.com> wrote:
> Foreman can email error reports automatically. (Without having to use the
> GUI..) IIRC you can also make it email actions (changes) - if not, it
> shouldn't be that hard to add.
>
> We use nagios to check puppet's state file for age - if it is too old,
> puppet hasn't run. Between those two, afaict, we're covering basically
> everything. And once a day, foreman also emails a status summary
> ('interesting' hosts - changes, failures, outdated/no report, etc)
>
> Puppet tries to run, finds a problem: Foreman emails the report.
> Puppet runs and makes changes, no errors: Do you want email? It'll show on
> the 'active hosts' page, and in the nightly summary email.
> Puppet doesn't run: Nagios alerts on that host
>
> And FWIW I'm the only sysadmin (also at a startup w/ no dev environment for
> puppet) and its really not impossible to get identical servers. (In fact,
> our first answer to "wtf is wrong with server21-foo" is "meh, whatever,
> trash the vm and recreate it".. Well.. thats first after "lets make sure it
> didn't get hacked" of course..) My workload went -way- down once puppet was
> working properly (complete manifests) and even more when I got foreman's vm
> deployments going.
>
> On Wed, May 25, 2011 at 1:48 PM, Douglas Garstang <doug.garst...@gmail.com>
> wrote:
>>
>> Executed successfully =
>> a) No syntax errors
>> b) No dependency errors
>> c) No other weird stuff
>> Just because there are no dependency errors on one system, doesn't mean
>> that there won't be dependency errors on another system. No two systems are
>> ever identical, so spot checks won't cover all bases.
>> We're a startup with limited resources, with the typical total lack of
>> resources. We don't have the luxury of a dev environment. We have 4 data
>> centres, different rules for each, and one is PCI compliant, which is akin
>> to having a root canal done every time you touch it. Even if we did, that
>> doesn't preclude making sure everything ran ok. It's still needed.
>> Doug.
>>
>> --
>> 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+unsubscr...@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
