This guide describes how to build a Ruby On Rails application stack using Chef cookbooks available from the Cookbooks Community Site and Hosted Chef. It assumes you followed the Getting Started Guide and have Chef installed.
This guide uses Ubuntu 10.04 on Amazon AWS EC2 with Chef 0.10.0.
Note: At this time, the steps described above have only been tested on the identified platform(s). Opscode has not researched and does not support alternative steps that may lead to successful completion on other platforms. Platform(s) supported by this guide may change over time, so please do check back for updates. If you'd like to undertake this guide on an alternate platform, you may desire to turn to open source community resources for support assistance.
You can watch a short screencast of this guide here.
At the end of this guide, you'll have four total Ubuntu 10.04 systems running in Amazon EC2.
- 1 haproxy load balancer.
- 2 Ruby on Rails application servers.
- 1 MySQL database server.
The Ruby on Rails application used in this guide is Radiant CMS.
We're going to reuse a number of cookbooks from the Cookbooks Community Site to build the environment. For example, the source code lives in git, so that cookbook will ensure Git is available. The load balancer is haproxy because it is very simple to deploy and configure, and we use a recipe that automatically discovers the Rails application systems. The heavy lifting is handled by recipes in the application and database cookbooks. Finally, as we're deploying Radiant, we'll get some help from the radiant cookbook.
If you don't already have an account with Amazon AWS, go to Amazon Web Sevices and click "Sign up". You'll need the access and secret access key credentials from the sign-up later.
First, let's configure the local workstation.
Obtain the repository used for this guide. It contains all the components required. Use git:
git clone git://github.com/opscode/rails-quick-start.git
Ubuntu/Debian users: Install XML2 and XLST development headers on your system:
sudo apt-get install libxml2-dev libxslt-dev
All Users: You'll need some additional gems for Knife to launch instances in Amazon EC2:
sudo gem install knife-ec2
As part of the Getting Started Guide, you cloned a chef-repo and copied the Knife configuration file (knife.rb), validation certificate (ORGNAME-validator.pem) and user certificate (USERNAME.pem) to ~/chef-repo/.chef/. Copy these files to the new rails-quick-start repository. You can also re-download the Knife configuration file for your Organization from the Management Console.
mkdir ~/rails-quick-start/.chef
cp ~/chef-repo/.chef/knife.rb ~/rails-quick-start/.chef
cp ~/chef-repo/.chef/USERNAME.pem ~/rails-quick-start/.chef
cp ~/chef-repo/.chef/ORGNAME-validator.pem ~/rails-quick-start/.chef
Add the Amazon AWS credentials to the Knife configuration file.
vi ~/rails-quick-start/.chef/knife.rb
Add the following two lines to the end:
knife[:aws_access_key_id] = "replace with the Amazon Access Key ID"
knife[:aws_secret_access_key] = "replace with the Amazon Secret Access Key ID"
Once the rails-quick-start and knife configuration is in place, we'll work from this directory.
cd rails-quick-start
In addition to the credentials, two additional things need to be configured in the AWS account.
Configure the default security group to allow incoming connections for the following ports.
- 22 - ssh
- 80 - haproxy load balancer
- 22002 - haproxy administrative interface
- 8080 - unicorn Rails application
Add these to the default security group for the account using the AWS Console.
- Sign into the Amazon AWS Console.
- Click on the "Amazon EC2" tab at the top.
- Click on "Security Groups" in the left sidebar of the AWS Console.
- Select the "Default" group in the main pane.
- Enter the values shown for each of the ports required. Use "Custom" in the drop-down for 22002 and 8080.
Create an SSH Key Pair and save the private key in ~/.ssh.
-
In the AWS Console, click on "Key Pairs" in the left sidebar.
-
Click on "Create Keypair" at the top of the main pane.
-
Give the keypair a name like "rails-quick-start".
-
The keypair will be downloaded automatically by the browser and saved to the default Downloads location.
-
Move the rails-quick-start.pem file from the default Downloads location to ~/.ssh and change permissions so that only you can read the file. For example,
mv ~/Downloads/rails-quick-start.pem ~/.ssh
chmod 600 ~/.ssh/rails-quick-start.pem
The rails-quick-start has all the cookbooks we need for this guide. They were downloaded along with their dependencies from the cookbooks site using Knife. These are in the cookbooks/ directory.
apt
git
application
database
radiant
haproxy
Upload all the cookbooks to Hosted Chef.
knife cookbook upload -a
All the required roles have been created in the rails-quick-start repository. They are in the roles/ directory.
base.rb
radiant_database_master.rb
radiant.rb
radiant_run_migrations.rb
radiant_load_balancer.rb
Upload all the roles to Hosted Chef.
rake roles
The rails-quick-start repository contains a data bag item that has all the information required to deploy and configure the Radiant application from source using the recipes in the application and database cookbooks.
The data bag name is apps and the item name is radiant. Upload this to Hosted Chef.
knife data bag create apps
knife data bag from file apps radiant.json
It is time for you to decide whether you want a single instance running Radiant, or a few instances as a small infrastructure.
In either case, we're going to use m1.small instances with the 32 bit Ubuntu 10.04 image provided by Canonical. The identifier is ami-88f504e1 for the AMI in us-east-1 with instance storage that we will use in this guide. We'll show you the knife ec2 server create sub-command to launch instances.
This command will:
- Launch a server on EC2.
- Connect it to Hosted Chef.
- Configure the system with Chef.
See the appropriate section below for instruction on launching a single instance, or launching the multi-system infrastructure.
Launch the entire stack on a single instance.
knife ec2 server create -G default -I ami-7000f019 -f m1.small \
-S rails-quick-start -i ~/.ssh/rails-quick-start.pem -x ubuntu -d ubuntu10.04-gems-qs \
-r 'role[base],role[radiant_database_master],role[radiant],role[radiant_run_migrations],recipe[radiant::db_bootstrap],role[radiant_load_balancer]'
Once complete, the instance will be running MySQL and Radiant under Unicorn. With only one system, a load balancer is unnecessary.
We will launch one database server, two application servers and one load balancer. One of the application server instances will include the role for running migrations as discussed before.
First, launch the database instance.
knife ec2 server create -G default -I ami-7000f019 -f m1.small \
-S rails-quick-start -i ~/.ssh/rails-quick-start.pem -x ubuntu -d ubuntu10.04-gems-qs \
-r 'role[base],role[radiant_database_master]'
Once the database master is up, launch one node that will run database migration and set up the database with default data.
knife ec2 server create -G default -I ami-7000f019 -f m1.small \
-S rails-quick-start -i ~/.ssh/rails-quick-start.pem -x ubuntu -d ubuntu10.04-gems-qs \
-r 'role[base],role[radiant],role[radiant_run_migrations],recipe[radiant::db_bootstrap]'
Launch the second application instance w/o the radiant_run_migrations role or radiant::db_bootstrap recipe.
knife ec2 server create -G default -I ami-7000f019 -f m1.small \
-S rails-quick-start -i ~/.ssh/rails-quick-start.pem -x ubuntu -d ubuntu10.04-gems-qs \
-r 'role[base],role[radiant]'
Once the second application instance is up, launch the load balancer.
knife ec2 server create -G default -I ami-7000f019 -f m1.small \
-S rails-quick-start -i ~/.ssh/rails-quick-start.pem -x ubuntu -d ubuntu10.04-gems-qs \
-r 'role[base],role[radiant_load_balancer]'
Once complete, we'll have four instances running in EC2 with MySQL, Radiant and haproxy up and available to serve traffic.
Knife will output the fully qualified domain name of the instance when the commands complete. Navigate to the public fully qualified domain name on port 80:
http://ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com/
The login is admin and the password is radiant.
You can access the haproxy admin interface at:
http://ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com:22002/
The data bag item for Radiant contains default passwords that should certainly be changed to something stronger.
The passwords in the Radiant Data Bag Item are set to the values show below:
"mysql_root_password": {
"_default": "mysql_root"
},
"mysql_debian_password": {
"_default": "mysql_debian"
},
"mysql_repl_password": {
"_default": "mysql_repl"
},
To change the password to something stronger, modify mysql_root, mysql_debian, mysql_repl values. Something like the following secure passwords:
vi data_bags/apps/radiant.json
"mysql_root_password": {
"_default": "super_s3cur3_r00t_pw"
},
"mysql_debian_password": {
"_default": "super_s3cur3_d3b1@n_pw"
},
"mysql_repl_password": {
"_default": "super_s3cur3_r3pl_pw"
},
Once the entries are modified, simply load the data bag item from the json file:
knife data bag from file apps radiant.json
For people not using Amazon EC2, other Cloud computing providers can be used. Supported by knife and fog as of this revision:
- Rackspace Cloud
See the launch cloud instances page on the Chef wiki for more information about using Knife to launch these instance types.
For people not using cloud at all, but have their own infrastructure and hardware, use the bootstrap knife command. Note that the run-list specification is slightly different. For the first example of the single instance:
knife bootstrap IPADDRESS \
-r 'role[base],role[radiant_database_master],role[radiant],role[radiant_run_migrations],recipe[radiant::db_bootstrap],role[radiant_load_balancer]'
See the contextual help for knife bootstrap on the additional options to set for SSH.
knife bootstrap --help
We used m1.small instances. This is a low performance instance size in EC2 and just fine for testing. Visit the Amazon AWS documentation to learn more about instance sizes.