I’ve worked with CFEngine and Puppet the most. CFEngine was inherited. Everything since that time has been Puppet. Chef has mindshare and Ansible appears to have a following.
See: http://serverfault.com/a/396000/13325 for a more detailed description of how I got started with Puppet. With any solution, I recommend starting small. Start by managing files like /etc/resolv.conf or ensuring certain packages are installed or running. And really try to build from there. After my first two Puppet deployments, I paid out-of-pocket to attend formal Puppet training. It was a 3-day course, but I was able to get a feel for how things should be done and was introduced to the Puppet Enterprise product. That streamlined the ugly portions of the open-source edition and helped me focus on the modules I needed to develop. The course was well worth it. There’s a prebuilt VM for evaluation, and the Puppet Enterprise software can accommodate 10 nodes for free… -- Edmund White e...@ewwhite.net From: "Edward Ned Harvey (lopser)" <lop...@nedharvey.com<mailto:lop...@nedharvey.com>> Date: Wednesday, November 12, 2014 at 4:18 PM To: LOPSA Technical Discussions <t...@lopsa.org<mailto:t...@lopsa.org>> Subject: [lopsa-tech] Puppet, Chef, Etc 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/
