RETIRED, Examples and references to use Chef for OpenStack projects
Go to file
Hugh Saunders ae1c001286 Remove Berksfile.lock
Berksfile.lock is not updated so points to old versions of each of the
stackforge cookbooks. Removing this file ensures that a user gets the
most recent stackforge cookbooks when installing with berkshelf.

Add Berksfile.lock to .gitignore so that another version isn't
committed.

Update Readme with note about Berksfile.lock

Change-Id: I8ea3223e98ac4dbab94e45f2323c6dcea2b54504
2014-01-20 15:50:36 +00:00
environments Add environment and roles for heat support 2014-01-17 17:42:36 +08:00
roles Add environment and roles for heat support 2014-01-17 17:42:36 +08:00
.gitignore Remove Berksfile.lock 2014-01-20 15:50:36 +00:00
.gitreview Add gitreview file 2013-05-27 11:47:33 -04:00
Berksfile Add openstack-orchestration to chef-repo Berksfile. 2014-01-16 20:07:39 +00:00
CHANGELOG.md preparing for grizzly 2013-05-24 13:31:19 -05:00
Gemfile remove Vagabond (for now) and update gem dependencies to fix the gating 2013-10-11 16:17:41 -05:00
Gemfile.lock remove Vagabond (for now) and update gem dependencies to fix the gating 2013-10-11 16:17:41 -05:00
LICENSE Apache License v2.0 2012-10-12 15:45:47 -05:00
README.md Remove Berksfile.lock 2014-01-20 15:50:36 +00:00
TESTING.md Remove Ubuntu 13.04 from test matrix. 2013-11-28 09:13:32 -06:00
Vagabondfile Adds Vagabond integration testing and setup 2013-08-07 15:50:29 -04:00
Vagrantfile Remove Ubuntu 13.04 from test matrix. 2013-11-28 09:13:32 -06:00
infrastructure.yml create os-image-upload role and change the order of 2013-12-04 15:10:44 +08:00

README.md

Description

This repository contains examples of the roles, environments and other supporting files for deploying an OpenStack Havana reference architecture using Chef. This currently includes all OpenStack core projects: Compute, Dashboard, Identity, Image, Network, Object Storage, Block Storage, Telemetry and Orchestration.

Development of the latest Stable release will continue on the master branch and releases tagged with 8.0.X. Once development starts against OpenStack master or icehouse, this branch will move to stable/havana and the appropriate branches will continue development.

The documentation has been moved to the https://github.com/mattray/chef-docs repository for merging to https://github.com/opscode/chef-docs and eventual release to https://docs.opscode.com. Instructions for building the docs are included in the repository. There is additional documentation on the OpenStack wiki.

Usage

This repository uses Berkshelf (https://berkshelf.com) to manage downloading all of the proper cookbook versions, whether from Git or from the Opscode Community site (https://community.opscode.com). The preference is to eventually upstream all cookbook dependencies to the Opscode Community site. The Berksfile lists the current dependencies. Note that berks will resolve version requirements and dependencies on first run and store these in Berksfile.lock. If new cookbooks become available you can run berks update to update the references in Berksfile.lock. Berksfile.lock will be included in stable branches to provide a known good set of dependencies. Berksfile.lock will not be included in development branches to encourage development against the latest cookbooks.

There is a Spiceweasel (http://bit.ly/spcwsl) infrastructure.yml manifest documenting all the roles and environments required to deploy OpenStack.

To see the commands necessary to push all of the files to the Chef server, run the following command:

spiceweasel infrastructure.yml

To actually deploy the repository to your Chef server, run the following command:

spiceweasel -e infrastructure.yml

Cookbooks

The cookbooks have been designed and written in such a way that they can be used to deploy individual service components on any of the nodes in the infrastructure; in short they can be used for single node 'all-in-one' installs (for testing), right up to multi/many node production installs. In order to achieve this flexibility, they are configured by attributes which may be used to override search. Chef 10 or later is currently required, but the intention is to move to Chef 11 with the havana release to take advantage of features such as partial search. Ruby 1.9.x is considered the minimum supported version of Ruby as well. Most users of this repository test with the full-stack Chef 11 client and a Chef server (Chef Solo is not explicity supported).

Each of the OpenStack services has its own cookbook and will eventually be available on the Chef Community site.

OpenStack Block Storage

http://github.com/stackforge/cookbook-openstack-block-storage/

There is further documentation in the OpenStack Block Storage cookbook README.

OpenStack Compute

http://github.com/stackforge/cookbook-openstack-compute/

There is further documentation in the OpenStack Compute cookbook README.

OpenStack Dashboard

http://github.com/stackforge/cookbook-openstack-dashboard/

There is further documentation in the OpenStack Dashboard cookbook README.

OpenStack Identity

http://github.com/stackforge/cookbook-openstack-identity/

There is further documentation in the OpenStack Identity cookbook README.

OpenStack Image

http://github.com/stackforge/cookbook-openstack-image/

There is further documentation in the OpenStack Image cookbook README.

OpenStack Network

Http://github.com/stackforge/cookbook-openstack-network/

There is further documentation in the OpenStack Network cookbook README.

OpenStack Object Storage

http://github.com/stackforge/cookbook-openstack-object-storage/

There is further documentation in the OpenStack Object Storage cookbook README.

Testing

Please refer to the TESTING.md for instructions for testing the repository and cookbooks with Vagrant or Vagabond.

License and Author

Author Matt Ray (matt@opscode.com)
Author Jay Pipes (jaypipes@gmail.com)
Copyright Copyright (c) 2011-2013 Opscode, Inc.

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.