Jump to content

Progress Chef

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by AlastairIrvine (talk | contribs) at 14:50, 25 November 2015 (Category:Configuration management with a subcategory, Category:Configuration management). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

see
Developer(s)Chef
Initial releaseJanuary 2009; 15 years ago (2009-01)[1]
Stable release
  • 2015-10-08 12.5.1 (client),[2]
  • 2015-09-02 12.2.0 (server)[3]
/ October 8, 2015; 8 years ago (2015-10-08)
Repository
Written inRuby (client) and Ruby / Erlang (server)
Operating systemGNU/Linux, AT&T Unix, MS Windows, FreeBSD, Mac OS X, IBM AIX illumos
TypeConfiguration management, System administration, Network management, Cloud management, Continuous delivery, DevOps
LicenseApache License
Websitewww.chef.io

Chef is a company & 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 Rackspace, Internap, 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.

Features

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

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

It is one of the four major configuration management systems on Linux, along with CFEngine, Bcfg2, and Puppet.[6][7]

History

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. Adam 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.[8]

The project was originally named "marionette", but 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".[8]

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

Platform support

Chef is supported on multiple platforms according to a supported platforms matrix for client and server products.[10] Major platform support for client includes AIX, RHEL/CentOS, FreeBSD, OS X, Solaris (operating system), Microsoft Windows, Ubuntu. Other client platforms include ArchLinux, Debian, Fedora, and others. Chef Server is supported on RHEL/CentOS/Oracle Linux, and Ubuntu.

Users

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

See also

References

  1. ^ https://www.chef.io/blog/2009/01/15/announcing-chef/
  2. ^ Julian Dunn (2015-10-08). "Chef Client 12.5 Released". chef.io. Retrieved 2015-10-16.
  3. ^ Marc Paradise (2015-09-02). "Chef Server 12.2.0 Release Announcement". chef.io. Retrieved 2015-10-16.
  4. ^ Chef - Code Can | Chef, retrieved 2015-07-04
  5. ^ Cade Metz (2011-10-26), "The Chef, the Puppet, and the Sexy IT Admin", Wired, retrieved 2015-07-04
  6. ^ Alan Sharp-Paul (2013-03-04), Puppet vs. Chef - The Battle Wages On, retrieved 2015-07-04.
  7. ^ Lueninghoener, Cory (2011-03-28), "Getting Started with Configuration Management" (PDF), ;login:, 36 (2), Usenix, retrieved 2015-07-04
  8. ^ a b History of Chef: What's in a Name? on YouTube
  9. ^ Bryan McLellan (2013-02-04). "Chef 11 Released!". Opscode. Retrieved 2015-07-04.
  10. ^ https://docs.chef.io/supported_platforms.html
  11. ^ "Facebook uses a seasoned Chef to keep servers simmering". pcadvisor.co.uk. Retrieved 6 January 2014.
  12. ^ "ChefConf Readout: Chef to Enable the Full Continuous Deployment Pipeline". HPCloud.com. Retrieved 25 June 2012.
  13. ^ How Chef Enables the DevOps Culture at Prezi - Zsolt Dollenstein on YouTube
  14. ^ Creating a Culture for Continuous Delivery - John Esser on YouTube
  15. ^ www.rackspace.com/devops/
  16. ^ chef.io/customers/
Retrieved from "https://en.wikipedia.org/w/index.php?title=Progress_Chef&oldid=692415090"