On 05/25/2010 11:10 AM, Nick Silkey wrote: > On Tue, May 25, 2010 at 11:01 AM, Phil Pennock > <lopsa-discuss+p...@spodhuis.org> wrote: > >> So, if service Foo gets droped from your puppet configs somehow, through >> misconfiguration, your monitoring will stop and the service can go down >> without you knowing about it? >> > Hopefully something, in meatspace or otherwise, is watching diffs of > commits to VCS that manages the puppet configs? You do keep cfg mgmt > configs under VCS ... right? Working on code without the safety net > of source control feels like tightrope walking over an acid-filled > pool of sharks with lasers. > [http://twitter.com/BrianEnigma/status/14640615599] So I guess like > many things we sysadmins do, this boils down to > risk-of-no-airspace-segregation versus convenience-of-reuse? > _______________________________________________ > Discuss mailing list > Discuss@lopsa.org > http://lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > I also use source control extensively, but my pre-commit does syntax checking for a bunch of languages, nothing that is intelligent enough to determine that you stopped configuring a service via puppet. I mean we get notifications of diffs in the post-commit, so if you are paying attention to the e-mails you should notice.
-- Joe McDonagh Operations Engineer AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
