A Chef cookbook for managing Ruby installations.

A daemon that connects systems to the RightScale cloud management platform.

Magic

Baton

Extenstions for berkshelf

Builderator automates many of the common steps required to build VMs and images with Chef. It provides a common configuration layer for Chef, Berkshelf, Vagrant, and Packer, and tasks to orchestrate the usage of each. https://github.com/rapid7/builderator

Allows Capistrano to use Chef data for deployment

Define, enforce, and handle violations of validation rules for Chef node attributes. This gem provides the validation engine, and can be used outside of a convergence run; a cookbook (attribute-validator) is available to perform validation during a chef run, at compile or converge time.

This library adds the `container_init` Chef resource. Using this resource allows you to hijack service resources and use the runit installation included with chef-container.

A streamlined development and deployment workflow for Chef platform.

Low level manipulation tool for Chef Infra Server

Low level manipulation tool for Chef Server 12 and later

= DESCRIPTION: Provides a Chef handler which can report run status, including any changes that were made, to a Graylog2 server. In the case of failed runs a backtrace will be included in the details reported. = REQUIREMENTS: * A Graylog2 server running somewhere. = USAGE: This example makes of the chef_handler cookbook, place some thing like this in cookbooks/chef_handler/recipes/gelf.rb and add it to your run list. It also assumes your Graylog2 server has set the attribute rsyslog_server to true. log_server = search(:node, "rsyslog_server:true").first if log_server include_recipe "chef_handler::default" gem_package "chef-gelf" do action :nothing end.run_action(:install) # Make sure the newly installed Gem is loaded. Gem.clear_paths require 'chef/gelf' chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'] }) supports :exception => true, :report => true end.run_action(:enable) end Arguments take the form of an options hash, with the following options: * :server - The server to send messages to. * :port (12201) - The port to send on. * :facility (chef-client) - The facility to report under. * :host (node.fqdn) - The host to report messages as coming from. * :blacklist ({}) - A hash of cookbooks, resources and actions to ignore in the change list. = BLACKLISTING: Some resources report themselves as having updated on every run even if nothing changed, or are just things you don't care about. To reduce the amount of noise in your logs these can be ignored by providing a blacklist. In this example we don't want to be told about the GELF handler being activated: chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'], :blacklist => { "chef_handler" => { "chef_handler" => [ "nothing", "enable" ] } } }) supports :exception => true, :report => true end.run_action(:enable) = LICENSE and AUTHOR: Author:: Jon Wood (<jon@blankpad.net>) Copyright:: 2011, Blank Pad Development 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.

Push reporting stats to Librato metrics

Chef report handler for sending run detail information to Opsmatic

A collection of helper methods to use in Opscode Chef recipes

Keep your chef server in sync with jenkins

LXC bindings for Chef

Provisioner for creating LXC containers in Chef Metal.

Provisioner for managing servers using ssh in Chef Metal.