|Stable release||11.16.4 / October 8, 2014|
|Written in||Ruby (client) and Ruby / Erlang (server)|
|Operating system||GNU/Linux, AT&T Unix, MS Windows, FreeBSD, Mac OS X, IBM AIX illumos|
|Type||Configuration management, System administration, Network management, Cloud management, Continuous delivery, DevOps|
Chef is a configuration management tool written in Ruby and Erlang. It uses a pure-Ruby, domain-specific language (DSL) for writing system configuration "recipes". Chef is used to streamline the task of configuring & maintaining a company's servers, and can integrate with cloud-based platforms such as Rackspace, Amazon EC2, Google Cloud Platform, OpenStack, SoftLayer and Microsoft Azure to automatically provision and configure new machines. Chef contains solutions for both small and large scale systems, with features and pricing for the respective ranges.
The user writes "recipes" that describe how Chef manages server applications and utilities (such as Apache HTTP Server, MySQL, or Hadoop) and how they are to be configured. These recipes (which can be grouped together as a “cookbook” for easier management) describe a series of resources that should be in a particular state: packages that should be installed, services that should be running, or files that should be written. These various resources can be configured to specific versions of software to run and can ensure that software is installed in the correct order based on dependencies. Chef makes sure each resource is properly configured and corrects any resources that are not in the desired state.
Chef can run in client/server mode, or in a standalone configuration named "chef-solo". In client/server mode, the Chef client sends various attributes about the node to the Chef server. The server uses Solr to index these attributes and provides an API for clients to query this information. Chef recipes can query these attributes and use the resulting data to help configure the node.
Chef began as an internal tool for a consultant company whose business model was to build end-to-end server/deployment tools. However, as the project began to develop, its creators realized its broader use case and created a more adaptable model of the product.
The project was originally named “marionette” (due to the heavy use of the Puppet software), but the length of the word was too long and cumbersome to type and the “recipe” format that the modules were prepared in led to the naming of “Chef.”
Although the Chef source code is licensed under the Apache license, compiled packages for Redhat and Ubuntu are available as "Enterprise Chef" under the following subscriptions:
|Price per month||Free||US-$6/node/month||Contact for Pricing|
|Nodes||25 Nodes||See above||Contact for Pricing|
|Support||Support for 30 days||Full support||Full support|
Chef is used by Airbnb, Mozilla, Facebook, HP Public Cloud, Prezi, Ancestry.com, Rackspace, Get Satisfaction, IGN, Marshall University, Socrata, University of Minnesota, Wharton School of the University of Pennsylvania, Bonobos, Splunk, and Cheezburger, among others.
- "Release: Chef Client Release: 11.16.4". GetChef.com. 8 October 2014.
- "Chef", Opscode
- Chef & Puppet, Wired, Oct 2011
- "Puppet vs Chef battle wages", Script rock.
- Lueninghoener, C (April 2011), Getting Started with Configuration Management (PDF), ;login: (Usenix) 36 (2), retrieved 2012-11-23
- History of Chef: What's in a Name? on YouTube
- "Chef 11 Released!". Opscode. 4 February 2013.
- "Facebook uses a seasoned Chef to keep servers simmering". pcadvisor.co.uk. Retrieved 6 January 2014.
- "ChefConf Readout: Chef to Enable the Full Continuous Deployment Pipeline". HPCloud.com. Retrieved 25 June 2012.
- How Chef Enables the DevOps Culture at Prezi - Zsolt Dollenstein on YouTube
- Creating a Culture for Continuous Delivery - John Esser on YouTube
|This free software–related article is a stub. You can help Wikipedia by expanding it.|