Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cfengine vs Puppet vs Chef: A Guide for Stressed Developers

7,944 views

Published on

If you're a developer in a small company, you probably don't have a dedicated sysadmin, but you still want to use best practices.

You've probably heard of configuration management as a better way to control your servers. You've heard of the big three: Puppet, Chef, and Cfengine.

But how do you choose between them? Especially when you've only got a week to spare for a project that should take 4?

This talk will walk you through the major differences between the big three solutions, and where each one would be the best fit.

Published in: Technology, Business
  • Login to see the comments

Cfengine vs Puppet vs Chef: A Guide for Stressed Developers

  1. 1. Cfengine vs Puppet vs Chef Ron Toland SCALE 2013
  2. 2. Background
  3. 3. Scenario
  4. 4. Common Features ● Flexible ● Configuration as Code ● Declarative DSL* * well, ok, not chef. but let's pretend.
  5. 5. Evaluation Criteria ● Footprint ● Scalability ● Documentation ● Learning Curve
  6. 6. Cfengine Footprint: Low
  7. 7. Cfengine Scalability: High
  8. 8. Cfengine Documentation: Terrible
  9. 9. Cfengine Learning Curve: Painful
  10. 10. Puppet Footprint: Ruby
  11. 11. Puppet Scalability: Tricky
  12. 12. Puppet Documentation: Excellent
  13. 13. Puppet Learning Curve: Gentle
  14. 14. Chef Footprint: Ruby + Friends
  15. 15. Chef Scalability: YES
  16. 16. Chef Documentation: Ok
  17. 17. Chef Learning Curve: Moderate
  18. 18. Recommendations
  19. 19. Small to Mid Scale: Puppet
  20. 20. Mid to Large Scale: Chef
  21. 21. Job Security: Cfengine
  22. 22. Further Reading ● Cfengine: http://cfengine.com/ ● Puppet: https://puppetlabs.com/ ● Pro Puppet, Turnbull & McCune ● Chef: http://www.opscode.com/chef/

×