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

Select Status


devstack (4) Versions 1.0.1

Installs/Configures devstack

cookbook 'devstack', '= 1.0.1', :supermarket
cookbook 'devstack', '= 1.0.1'
knife supermarket install devstack
knife supermarket download devstack
Quality 0%

devstack cookbook

A cookbook to install devstack



Operating Systems

  • Centos 7
  • Ubuntu 14.04



Key Type Description Default
['devstack']['host-ip'] String The host/ip to bind the stack to
['devstack']['database-password'] String The password for the DevStack database ostackdemo
['devstack']['rabbit-password'] String The password for tde rabbit service ostackdemo
['devstack']['service-token'] String The token for the DevStack service user token
['devstack']['service-password'] String The password for the DevStack service user ostackdemo
['devstack']['admin-password'] String The password for the DevStack admin user ostackdemo
['devstack']['dest'] String The directory to install DevStack /opt/stack
['devstack']['pip-timeout'] Integer The default time out for pip 1000



Just include devstack in your node's run_list:

    "run_list": [

Local Testing

There is also test-kitchen support for this cookbook. You can run:

$ chef exec kitchen verify

And it'll build it via vagrant on your local machine. There are serverspec tests also attached to verify devstack
is built correctly. You'll notice that it stops outputting at Recipe: devstack::stack, it's running the behind the scenes,
it averages 30ish mins on my MacBook Pro.

You can login to the devstack instance via:

$ chef exec kitchen login <version you converged>
vagrant@<machine_you_converged> $ cd /opt/stack/devstack/
vagrant@<machine_you_converged>:/opt/stack/devstack/ $ source openrc
vagrant@<machine_you_converged>:/opt/stack/devstack/ $ nova list
vagrant@<machine_you_converged>:/opt/stack/devstack/ $ nova nova boot test --image cirros-0.3.2-x86_64-uec --flavor 1

If you haven't changed any variables and usernames/passwords, you can go to http://localhost:8080 and use demo/devstack and see
the dashboard.


NOTE: Not in order of priority.

  • travis testing
  • Rakefile and rake commands
  • chefspec for the different resources
  • more serverspec tests
  • neutron support
  • multi-node lab support


  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

Apache 2

Author: Cameron Lopez
Author: JJ Asghar (

Dependent cookbooks

git >= 0.0.0
sudo >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

CHANGELOG for devstack

This file is used to list changes made in each version of devstack.


  • Initial release of devstack

Check the Markdown Syntax Guide for help with Markdown.

The Github Flavored Markdown page describes the differences between markdown on github and standard markdown.

Foodcritic Metric

1.0.1 failed this metric

FC002: Avoid string interpolation where not required: /tmp/cook/fbac7c471dbc46f59f45aaa6/devstack/recipes/install.rb:27
FC031: Cookbook without metadata file: /tmp/cook/fbac7c471dbc46f59f45aaa6/devstack/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/fbac7c471dbc46f59f45aaa6/devstack/metadata.rb:1