Is anybody else confused about Chef ? | Everything is a Freaking DNS problem Chef absolutely confuses me.. Luke is confused too .. I’m clearly disappointed that someone who has been a high-profile user of Puppet but has never contributed much in the way of code (Ohloh claims 2 commits) would decide to start a whole new project rather than attempt to contribute to Puppet
I spent a fair bit of time this week messing with Chef, which I had somehow missed in my previous rounds of scooping up system administration tools. Puppet vs Chef | BHUGA WOOGA!
rhel5 - Puppet vs Chef, pro and contra from users and use cases
Chef is based on a key insight: You can model your evolving IT infrastructure and applications as code. Chef makes no assumptions about your environment and the approach you use to configure and manage it. Instead, Chef gives you a way to describe and automate your infrastructure and processes. Your infrastructure becomes testable, versioned and repeatable. It becomes part of your Agile process. Chef relies on reusable definitions known as cookbooks and recipes that are written using the the Ruby programming language.
If you have one Linux system to administer, you need a good working knowledge of scripting, command line utilities, and a trusty text editor. If you have two or more, it may be time to add Puppet to that list. Introduction to Puppet: Streamlined System Configuration
Puppet, Chef, cfengine, and Bcfg2 are all players in the configuration management space. Puppet versus Chef: 10 reasons why Puppet wins | Bitfield Consulting