On 2010-05-25 at 11:10 -0400, 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?
* I use source control, extensively * I don't currently work on systems where puppet or its like are used, although my desktop & laptop are admin'd with puppet by another group, so I'm only talking general principles here * What worries me is the potential to have a broken dependency somewhere with a diff which *looks* innocuous but turns out to have rather significant impact -- so pre-commit or post-commit hooks are going to be beneficial: even if not for the cross-reference sanity checks I mentioned then for generating impact summaries _______________________________________________ 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/
