On Aug 26, 2010, at 11:36 AM, Mike Peck wrote:
I've spent some time beginning to learn how puppet works, and one seemingly rather daunting task I'm facing, is how to setup the initial state of things. What I'm specifically thinking about, is that I have machines running that I want to get their current state pulled into puppet. How do I do that? I have various flavors/versions of BSD systems and various flavors/versions of *nix machines, and right now it's seeming like I have to tackle each one of each type, one by one, figuring out all the myriad steps needed to build each one. One thing I may be mis-understanding, however, is the base OS. Should I be expecting to have puppet start from a freshly installed OS, and if so what level of configuration should be assumed? I am expecting puppet to be able to handle OS updates, but I haven't yet run across examples of that. Does anybody know of any docs that describe what a significantly sized existing organization might go through in order to adopt puppet? Of course I would expect this to ignore all the policy issues of adoption, I'm looking for ideas on how to get started.
I've been engaged in more or less the same task. One suggestion I have is that you don't need to do it all up front. You can get Puppet installed and running on all of your nodes with trivial configuration for each. You (or some delegates) can then update the configuration bit by bit, and refactor into modules as appropriate.
---------------------- Charles Yeomans Senior Software Engineer Dakim, Inc. char...@dakim.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
