Full disclosure: I work for Chef now So… I am a big fan of doing the getting started examples, the one for Chef can be found at http://learn.getchef.com/ <http://learn.getchef.com/>. The real thing is getting to a point where you are comfortable destroying and rebuilding your instances and getting out of the habit of manually making changes.
I started with Puppet and now use Chef. I like both and can be productive in both. The best thing, if it is an option, is to find a mentor that you can poke when you have questions as you are getting started. Each has its warts and it is good to have someone to help you when you are hitting them. One of the things I have really focused on is using the CM software as docs for my system. Not only should they be executable in the sense that it converges on a known state, but I should be able to read through a recipe or class and get a feel for what is being done to the machine. If you have any specific questions, you are welcome to hit me up directly, either via email, irc, or any other place I am available on the inter webs. — cwebber > On Nov 12, 2014, at 2:18 PM, Edward Ned Harvey (lopser) > <lop...@nedharvey.com> 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 > <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 <mailto:Tech@lists.lopsa.org> > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > <https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech> > This list provided by the League of Professional System Administrators > http://lopsa.org/ <http://lopsa.org/>
_______________________________________________ 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/
