Puppet's a fine direction. Without knowing your situation and your preferences, I think it would be hard for anyone to say much more than that.
I have Puppet experience from $JOB-1, but decided to implement Salt at $JOB. I like that it's fast, integrates configuration management with orchestration, allows for very simple state files, and is based on Python-not-Ruby (which matches my personal preferences). I liked that Puppet was relatively mature and has a huge amount of community support. I never seriously investigated Chef since I thought it emphasized the sides of Puppet style configuration management I like less. Ansible seems great for orchestration, but lighter on configuration management. Broadly, Starchy On 11/12/2014 02:18 PM, Edward Ned Harvey (lopser) wrote: > I've decided it's time to step forth out of the stone ages and get into CM. > > > > As I understand it, the major contenders are puppet, chef, ansible, and > salt. (And optionally vagrant on top of it all). > > > > Not having the experience of using and understanding each and every one > of them, I decided to start digging into puppet - just because people > talking about it seem the most positively aligned with what I want to > do. However, when I start browsing their site, reading documentation, > it's immediately overwhelming and mind-numbing. > > > > Funnily, I googled for "getting started with puppet" and came up with > this: http://puppetlabs.com/presentations/getting-started-puppet > It's funny because they don't have this sort of thing front and center, > their website is organized as to be completely overwhelming and mind > numbing as mentioned above. But anyway.... > > > > I assume a lot of people here have experience with these things. If you > think I'm not starting out in the "right" direction, or would like to > offer any other advice, please let me know. > > > > I am primarily interested in making a small number of machines > standardized, recreatable, manageable. If I run a production server on > amazon and I want to migrate it somewhere else, I'd like to know I > easily can. And when the current OS becomes EOL, I'd like to know I > have a sane path for recreating the same services on the new OS that's > available at the time, and stuff like that. > > > > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
