opscode / chef

A systems integration framework, built to bring the benefits of configuration management to your entire infrastructure.

This URL has Read+Write access

adamhjk (author)
Wed Nov 04 21:07:16 -0800 2009
commit  2c47c70bf690fb39d5db1336b6735d24211a030a
tree    e9224c87b047a2daf0e72ca61ae5d2ef0750f577
parent  f80b5b578a6000b1da64e2c558f9bc4e5dc33872
chef /
name age message
file .gitignore Thu Aug 20 13:31:58 -0700 2009 Initial pass at a Chef 0.8.0 alpha Conflicts: ... [adamhjk]
file .gitmodules Fri Apr 10 23:46:17 -0700 2009 Submodule the web-app-theme [fujin]
file CHANGELOG Mon Oct 26 13:40:41 -0700 2009 Release Chef 0.7.14 [fujin]
file LICENSE Wed Oct 08 14:50:02 -0700 2008 Chef should have the license and notice at the top [adamhjk]
file NOTICE Fri Mar 13 11:16:56 -0700 2009 Adding joewilliams to the NOTICE file [adamhjk]
file README.rdoc Tue Jun 30 15:09:05 -0700 2009 CHEF-418: Readme clarification for features [fujin]
file Rakefile Thu Oct 29 08:30:28 -0700 2009 Merge branch 'CHEF-656' of git://github.com/dan... [adamhjk]
directory chef-server-api/ Tue Nov 03 16:11:44 -0800 2009 Fixes CHEF-681 [adamhjk]
directory chef-server-webui/ Fri Oct 16 17:00:23 -0700 2009 Merge branch 'master' of git@github.com:opscode... [adamhjk]
directory chef-server/ Mon Oct 19 22:54:06 -0700 2009 Fixes for 0.7.12->0.8 merge, tests pass [adamhjk]
directory chef-solr/ Mon Nov 02 15:26:08 -0800 2009 Using non-macified solr tarballs [adamhjk]
directory chef/ Loading commit data...
file cucumber.yml Thu Oct 29 08:17:48 -0700 2009 Merge branch 'master' into 0.8-alpha All tests... [adamhjk]
directory features/ Thu Oct 29 08:44:51 -0700 2009 Merge branch 'master' into danielsdeleo/CHEF-626 [adamhjk]
directory scripts/ Sat Sep 26 11:33:00 -0700 2009 Adding mac-dev-start script, that spawns termin... [adamhjk]
README.rdoc

Chef

DESCRIPTION:

Chef is a configuration management tool designed to bring automation to your entire infrastructure.

The Chef Wiki is the definitive source of user documentation.

This README focuses on developers who want to modify Chef source code. For users who just want to run the latest and greatest Chef development version in their environment, see:

DEVELOPMENT:

Before working on the code, if you plan to contribute your changes, you need to read the Opscode Contributing document.

You will also need to set up the repository with the appropriate branches. We document the process on the Chef Wiki.

Once your repository is set up, you can start working on the code. We do use BDD/TDD with RSpec and Cucumber, so you’ll need to get a development environment running.

ENVIRONMENT:

In order to have a development environment where changes to the Chef code can be tested, we’ll need to install a few things after setting up the Git repository.

Requirements:

Install these via your platform’s preferred method; for example apt, yum, ports, emerge, etc.

  • Git
  • CouchDB
  • libxml2 development package (for webrat)
  • libxslt develoment package (for webrat)

Install the following RubyGems.

  • ohai
  • rake
  • rspec
  • cucumber
  • webrat
  • merb-core
  • roman-merb_cucumber

Ohai is also by Opscode and available on GitHub, github.com/opscode/ohai/tree/master.

roman-merb_cucumber is available from GitHub:

  gem install --source http://gems.github.com/ roman-merb_cucumber

Starting the Environment:

Once everything is installed, run the dev:features rake task. Since the features do integration testing, root access is required.

  sudo rake dev:features

The dev:features task:

  • Installs chef, chef-server, chef-server-slice gems. It will fail if required gems above are missing.
  • Starts chef-server on ports 4000 and 4001.
  • Starts chef-indexer.
  • Starts CouchDB on port 5984.
  • Starts the stompserver on port 61613.

You’ll know its running when you see:

   ~ Activating slice 'ChefServerSlice' ...
  merb : worker (port 4000) ~ Starting Mongrel at port 4000
  merb : worker (port 4000) ~ Successfully bound to port 4000
  merb : worker (port 4001) ~ Starting Mongrel at port 4001
  merb : worker (port 4001) ~ Successfully bound to port 4001

You’ll want to leave this terminal running the dev environment.

Web Interface:

With the dev environment running, you can now access the web interface via localhost:4000/. Supply an OpenID to log in.

Spec testing:

We use RSpec for unit/spec tests.

  rake spec

This doesn’t actually use the development environment, because it does the testing on all the Chef internals. For integration/usage testing, we use Cucumber features.

Integration testing:

We test integration with Cucumber. The available feature tests are rake tasks:

  rake features                            # Run Features with Cucumber
  rake features:api                        # Run Features with Cucumber
  rake features:api:nodes                  # Run Features with Cucumber
  rake features:api:nodes:create           # Run Features with Cucumber
  rake features:api:nodes:delete           # Run Features with Cucumber
  rake features:api:nodes:list             # Run Features with Cucumber
  rake features:api:nodes:show             # Run Features with Cucumber
  rake features:api:nodes:update           # Run Features with Cucumber
  rake features:api:roles                  # Run Features with Cucumber
  rake features:api:roles:create           # Run Features with Cucumber
  rake features:api:roles:delete           # Run Features with Cucumber
  rake features:api:roles:list             # Run Features with Cucumber
  rake features:api:roles:show             # Run Features with Cucumber
  rake features:api:roles:update           # Run Features with Cucumber
  rake features:client                     # Run Features with Cucumber
  rake features:language                   # Run Features with Cucumber
  rake features:language:recipe_include    # Run Features with Cucumber
  rake features:provider:package:macports  # Run Features with Cucumber
  rake features:provider:remote_file       # Run Features with Cucumber
  rake features:search                     # Run Features with Cucumber

LINKS:

Source:

Tickets/Issues:

Documentation:

LICENSE:

Chef - A configuration management system

Author:Adam Jacob (<adam@opscode.com>)
Copyright:Copyright © 2008, 2009 Opscode, Inc.
License:Apache License, Version 2.0

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.