Skip to content

Chef Solo Guide

Jump to bottom
steveandroulakis edited this page Apr 30, 2013 · 52 revisions

This is a brief, informal guide on running chef-solo on a server with the MyTardis recipe. This deploys a recipe on the machine that's executing this and doesn't require a chef server (Hosted Chef or other).

Confirmed working on these images (built from NeCTAR, tested on 17 Jan 2013)

  • 'Ubuntu Lucid i386'
  • 'CentOS 6.3 x86_64' (omit sudo from guide)
  • 'NeCTAR CentOS 6.3 x86_64'

Option 1: Deployment on your local machine with Vagrant

Follow the Vagrant getting started guide up to the point of adding the lucid32 box, then follow the commands below.

git clone https://github.com/steveandroulakis/mytardis-chef.git
cd mytardis-chef/
git checkout master_compatibility
cd vagrant/lucid
vagrant up

The server will be available on localhost:8000.

Use vagrant ssh then cd /opt/mytardis/current and bin/django createsuperuser to create a MyTardis administrator.

Option 2: Install on a server (non-vagrant chef build)

Non-vagrant setup.

Note: If your NeCTAR cloud node is complaining about not being able to resolve its hostname then fix it first before running this guide (add hostname 127.0.0.1 to /etc/hosts). This is a NeCTAR cloud issue.

Ubuntu:

sudo true && curl -L https://www.opscode.com/chef/install.sh | sudo bash
sudo apt-get update
sudo apt-get install git-core
mkdir -p /var/chef-solo
cd /var/chef-solo
git clone https://github.com/steveandroulakis/mytardis-chef.git
cd mytardis-chef/
git checkout master_compatibility
chef-solo -c solo/solo.rb -j solo/node.json -ldebug
Clone this wiki locally