Review: Puppet Vs. Chef Vs. Ansible Vs. Salt 141
snydeq writes "InfoWorld's Paul Venezia provides an in-depth review of Puppet, Chef, Ansible, and Salt — four leading configuration management and orchestration tools, each of which takes a different path to server automation. 'Puppet, Chef, Ansible, and Salt were all built with that very goal in mind: to make it much easier to configure and maintain dozens, hundreds, or even thousands of servers. That's not to say that smaller shops won't benefit from these tools, as automation and orchestration generally make life easier in an infrastructure of any size. I looked at each of these four tools in depth, explored their design and function, and determined that, while some scored higher than others, there's a place for each to fit in, depending on the goals of the deployment. Here, I summarize my findings.'"
Oh really? (Score:1, Interesting)
I call BS on that statement, I run puppet at home for my 2.5 servers, it really simplifies my life.
Advanced Puppet (Score:3, Interesting)
I prefer Puppet, but I don't think it's perfect. As a result, I've written some complicated hacks do to complicated things that aren't directly possible in core. I still think Puppet is the closest thing to being right.
Feel free to look through my articles and hacks: https://ttboj.wordpress.com/ [wordpress.com]
Most code available at: https://github.com/purpleidea/ [github.com]
Ansible lol... (Score:5, Interesting)
Am I the only one who saw Ansible in the article and was expecting a discussion about FTL communications?
Re:Puppet Vs. Chef Vs. Ansible Vs. Salt (Score:4, Interesting)
Comment removed (Score:5, Interesting)