Chef (software)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Not to be confused with Chef (programming language).
Chef
Chef logo.svg
Developer(s) Chef
Initial release January 2009; 7 years ago (2009-01)[1]
Stable release
  • 2016-09-22 12.14.89 (client),[2]
  • 2016-09-26 12.9.1 (server)[3]
Development status Active
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, Infrastructure as Code
License Apache License 2.0
Website www.chef.io

Chef is both the name of a company and the name of 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 and maintaining a company's servers, and can integrate with cloud-based platforms such as Internap, Amazon EC2, Google Cloud Platform, OpenStack, SoftLayer, Microsoft Azure and Rackspace 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.

Features[edit]

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"[4] 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.[5]

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.

Traditionally, Chef was used to manage Linux but later versions support Microsoft Windows as well.[6]

It is one of the four major configuration management systems on Linux, along with CFEngine, Bcfg2, and Puppet.[7][8] Chef is more than a configuration management tool, along with Puppet, Ansible and Otter it's one of the industry's most notable Infrastructure as Code (IAC) tools.[9]

History[edit]

Chef was created by Adam Jacob as a tool for his consulting company, whose business model was to build end-to-end server/deployment tools. Jacob showed Chef to Jesse Robbins, who saw its potential after running operations at Amazon. They founded a new company with Barry Steinglass, Nathen Haneysmith, and Joshua Timberman to turn Chef into a product.[10]

The project was originally named "marionette", but the word was too long and cumbersome to type; the "recipe" format that the modules were prepared in led to the project being renamed "Chef".[10]

In February 2013, Opscode released version 11 of Chef. Changes in this release included a complete rewrite of the core API server in Erlang.[11]

Platform support[edit]

Chef is supported on multiple platforms according to a supported platforms matrix for client and server products.[12] Major platform support for clients includes AIX, RHEL/CentOS, FreeBSD, OS X, Solaris, Microsoft Windows and Ubuntu. Additional client platforms include Arch Linux, Debian and Fedora. Chef Server is supported on RHEL/CentOS, Oracle Linux, and Ubuntu.

Users[edit]

Chef is used by Airbnb, Mozilla, Expedia, Facebook,[13] HP Public Cloud,[14] Prezi,[15] Xero, Ancestry.com,[16] Rackspace,[17] Get Satisfaction, IGN, Marshall University, Socrata, University of Minnesota, Wharton School of the University of Pennsylvania, Bonobos, Splunk, Citi, DueDil, Disney, and Cheezburger, among others.[18]

See also[edit]

References[edit]

  1. ^ https://www.chef.io/blog/2009/01/15/announcing-chef/
  2. ^ Matt Wrock (2016-09-22). "Chef Client 12.14.89 Released". chef.io. Retrieved 2016-10-10. 
  3. ^ Jon Morrow (2016-09-26). "Chef Server 12.9.1 Release Announcement". chef.io. Retrieved 2016-10-10. 
  4. ^ Kumar, Ishant (July 3, 2014). "Understanding Chef and Writing Cookbooks". TO THE NEW. Retrieved September 2, 2016. 
  5. ^ Chef - Code Can | Chef, retrieved 2015-07-04 
  6. ^ Cade Metz (2011-10-26), "The Chef, the Puppet, and the Sexy IT Admin", Wired, retrieved 2015-07-04 
  7. ^ Alan Sharp-Paul (2013-03-04), Puppet vs. Chef - The Battle Wages On, retrieved 2015-07-04 .
  8. ^ Lueninghoener, Cory (2011-03-28), "Getting Started with Configuration Management" (PDF), ;login:, Usenix, 36 (2), retrieved 2015-07-04 
  9. ^ Keiser, John (14 November 2016). "Chef Provisioning: Infrastructure As Code". 
  10. ^ a b History of Chef: What's in a Name? on YouTube
  11. ^ Bryan McLellan (2013-02-04). "Chef 11 Released!". Opscode. Retrieved 2015-07-04. 
  12. ^ https://docs.chef.io/supported_platforms.html
  13. ^ "Facebook uses a seasoned Chef to keep servers simmering". pcadvisor.co.uk. Retrieved 6 January 2014. 
  14. ^ "ChefConf Readout: Chef to Enable the Full Continuous Deployment Pipeline". HPCloud.com. Retrieved 25 June 2012. 
  15. ^ How Chef Enables the DevOps Culture at Prezi - Zsolt Dollenstein on YouTube
  16. ^ Creating a Culture for Continuous Delivery - John Esser on YouTube
  17. ^ www.rackspace.com/devops/
  18. ^ chef.io/customers/

External links[edit]