Recent Changes - Search:


Code:


Social:


My journals will take the place of a blog. If you go to the Journal page there is an RSS feed to subscribe with.

(:blogcal group=Journal:)


Sites I take responsibility for

West Volusia, Florida

Documents

Technical

General

Me

Living

Places I frequent

Hobbies

Humor

Items for sale:


Clipboard

edit SideBar

Chef

Include our styles below Infobox - invoke as >>infobox<< ... >><<

Codebox: - invoke as >>codebox<< ... >><<

warnbox: - invoke as >>codebox<< ... >><<

editingbox: - invoke as >>codebox<< ... >><<

noticebox: - invoke as >>codebox<< ... >><<

Page bread crumbs: Main - MyPublicTechnicalNotes - SoftwareAndOperatingSystems - Software - Deployment - Chef

Pages by tags: (:listtags:)
Subscribe to this wiki: RSS Feed RSS or subscribe to this page for changes: RSS Feed RSS
496 articles have been published so far. Recent changes
(:addThis btn="custom":)

2016-03-22: This site is being moved to my main site at https://kevininscoe.com/wiki as part of a consolidation to one domain.


http://en.wikipedia.org/wiki/Chef_%28software%29

"Chef is a configuration management tool written in Ruby. It uses a pure-Ruby, domain-specific language (DSL) for writing system configuration "recipes" or "cookbooks". Chef was written by Opscode and is released as open source under the Apache License 2.0."

Chef can run using a client/server model, or on a consolidated configuration named "chef-solo".

http://www.rubyinside.com/chef-tasty-server-configuraiton-2162.html

"Chef isn't exactly new, but I've been looking into it recently after briefly talking to Lindsay Holmwood at Rails Underground.

Basically, Chef is a Ruby-based configuration management engine. You set up recipes for how you want your system configured, and then Chef will cook it up for you. So, you can write lovely Ruby code to manage your servers, rather than running commands directly on your server.

With Chef, one of your systems is the server and all others are clients that communicate with the Chef "server" via REST over HTTPS. The server is a Merb application that stores cookbooks for your nodes using CouchDB.

The work is done by the clients, running the recipes for one or many nodes thus configuring that particular machine. The Chef server is only there to provide information to the clients. Once configured, you can access your Chef server and its cookbooks via a Web interface. You can create your own cookbooks from scratch but it's worth checking to see if one already exists in the Chef repository or one of its forks.

Once you've got your recipes sorted out, Chef allows you to programatically set up and commission production-ready server instances in next to no time.

Ezra's Cooking with Chef 101 blog post is a great place to get started, and there's a wealth of information in the Opscode Chef wiki. The Superfeedr blog post, Scale With Chef, is also worth a read."

http://www.opscode.com/chef/

http://wiki.opscode.com/display/chef/Recipes

http://www.themomorohoax.com/2010/07/31/ruby-chef-tutorial

http://wiki.opscode.com/display/chef/FAQ

http://wiki.opscode.com/display/chef/Fast+Start+Guide

http://stackoverflow.com/questions/2011011/are-there-any-good-chef-chef-server-and-chef-client-tutorials-out-there

http://wiki.opscode.com/display/chef/Chef+Presentations

http://warwickp.com/2009/12/configuration-management-with-chef-on-debian-part-1/

http://ruby-lambda.blogspot.com/2010/04/adventures-with-chef-server-and-gentoo.html

Programming:

See my Ruby page.


Kevin's Public Wiki maintained and created by Kevin P. Inscoe is licensed under a
Creative Commons Attribution 3.0 United States License.

Back to my web site - http://kevininscoe.com

Edit - History - Print - Recent Changes - Search
Page last modified on June 25, 2012, at 01:01 PM EST