Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


eucalyptus (10) Versions 0.1.3

Installs/Configures eucalyptus

cookbook 'eucalyptus', '= 0.1.3'
cookbook 'eucalyptus', '= 0.1.3', :supermarket
knife supermarket install eucalyptus
knife supermarket download eucalyptus
Quality -%

eucalyptus Cookbook

This cookbook installs and configures Eucalyptus on CentOS 6 physical and virtual machines. Source and package installations are supported.


Chef server config

Ensure that the following config is set in /etc/chef-server/chef-server.rb: erchef['s3_url_ttl'] = 3600


This cookbook only supports RHEL/CentOS 6 at the time being.


A Berksfile is included to allow users to easily download the required cookbook dependencies. - Install Berkshelf: gem install berkshelf - Install Deps from inside this cookbook: berks install


  • bridger - configures bridges on Node Controllers
  • ntp - sets up NTP for all Eucalyptus servers
  • partial_search - required for ssh_known_hosts
  • ssh_known_hosts - add components to known hosts list
  • yum - used for managing repositories
  • selinux - disables selinux on Eucalyptus servers


Attribute list can be found in attributes/default.rb

Some common attributes are:

eucalyptus installation config

<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>["eucalyptus"]["install-type"]</tt></td> <td>String</td> <td>Choose to install from package or source</td> <td><tt>package</tt></td> </tr> <tr> <td><tt>["eucalyptus"]["source-repo"]</tt></td> <td>String</td> <td>Git repository to clone when building from source</td> <td><tt></tt></td> </tr> <tr> <td><tt>["eucalyptus"]["source-branch"]</tt></td> <td>String</td> <td>Branch to use when building from source</td> <td><tt>testing</tt></td> </tr> </table>

eucalyptus network config

<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>["eucalyptus"]["network"]["mode"]</tt></td> <td>String</td> <td>Networking mode to use</td> <td><tt>MANAGED-NOVLAN</tt></td> </tr> <tr> <td><tt>["eucalyptus"]["network"]["private-interface"]</tt></td> <td>String</td> <td>Private interface of component</td> <td><tt>eth0</tt></td> </tr> <tr> <td><tt>["eucalyptus"]["network"]["public-interface"]</tt></td> <td>String</td> <td>Public interface of component</td> <td><tt>eth0</tt></td> </tr> <tr> <td><tt>["eucalyptus"]["network"]["bridge-interface"]</tt></td> <td>String</td> <td>Bridge interface of component. Will be created and set by playbook</td> <td><tt>br0</tt></td> </tr> </table>


eucalyptus from packages

For a single frontend configuration use a role similar to:

  "name": "cloud-controller",
  "description": "",
  "json_class": "Chef::Role",
  "default_attributes": {
    "eucalyptus": {
      "install-load-balancer": false
  "override_attributes": {
  "chef_type": "role",
  "run_list": [
  "env_run_lists": {

For a source build use something like: json { "name": "cloud-controller-source", "description": "", "json_class": "Chef::Role", "default_attributes": { "eucalyptus": { "install-type": "source", "release-rpm": "", "install-load-balancer": false } }, "override_attributes": { }, "chef_type": "role", "run_list": [ "recipe[eucalyptus]", "recipe[eucalyptus::eutester]", "recipe[eucalyptus::cloud-controller]" ], "env_run_lists": { } }


TODO: (optional) If this is a public cookbook, detail the process for contributing. If this is a private cookbook, remove this section.

e.g. 1. Fork the repository on Github 2. Create a named feature branch (like add_component_x) 3. Write your change 4. Write tests for your change (if applicable) 5. Run the tests, ensuring they all pass 6. Submit a Pull Request using Github

License and Authors

Authors: TODO: List authors

Dependent cookbooks

partial_search >= 0.0.0
ssh_known_hosts >= 0.0.0
selinux >= 0.0.0
ntp >= 0.0.0
yum >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found