Vagrant: Add support for Vagrant install (`vagrant up`)

Cf README, this adds support to install and setup a dev instance through
Vagrant. The Vagrantfile at the root handles the vagrant commands like
`vagrant up`.

Provisioning is done by the shell script `vagrant-provisionning.sh`,
which is a light wrapper around the `create-dev-setup.sh` which does
most of the job using the standard process, but limiting possible
side-effect by ensuring the environment on which the install is
performed is clean.

Based on an Ubuntu precise 12.04 LTS.

.gitignore

@@ -44,3 +44,4 @@ node_modules
 .prereqs_cache
 autodeploy.properties
 .ws_migrations_complete
+.vagrant/

README.md

@@ -2,8 +2,132 @@ This is the main edX platform which consists of LMS and Studio.
 
 See [code.edx.org](http://code.edx.org/) for other parts of the edX code base.
 
-Installation
-============
+Installation - The first time
+=============================
+
+The following instructions will help you to download and setup a virtual machine 
+with a minimal amount of steps, using Vagrant. It is recommended for a first 
+installation, as it will save you from many of the common pitfalls of the
+installation process.
+
+1. Install Git: http://git-scm.com/downloads
+2. Install VirtualBox: https://www.virtualbox.org/wiki/Downloads
+3. Install Vagrant: http://www.vagrantup.com/ (Vagrant 1.2.2 or later)
+4. Open a terminal
+5. Download the project: `git clone git://github.com/edx/edx-platform.git`
+6. Enter the project directory: `cd edx-platform/`
+7. Start: `vagrant up`
+
+The last step might require your administrator password to setup NFS. 
+
+Afterwards, it will download an image, install all the dependencies and configure 
+the VM. It will take a while, go grab a coffee.
+
+Once completed, hopefully you should see a "Success!" message indicating that the 
+installation went fine. (If not, refer to the Troubleshooting section below.)
+
+Accessing the VM
+----------------
+
+Vagrant should automatically log you in the virtual machine once the installation
+is finished. You can also type, from another terminal:
+
+```
+$ vagrant ssh
+```
+
+Note: This won't work from Windows, install install PuTTY from 
+http://www.chiark.greenend.org.uk/%7Esgtatham/putty/download.html instead. Then 
+connect to 127.0.0.1, port 2222, using vagrant/vagrant as a user/password.
+
+Using edX
+---------
+
+Once inside the VM, you can start Studio and LMS with the following commands
+(from the `/edx/edx-platform` folder):
+
+Learning management system (LMS):
+
+```
+$ rake lms[cms.dev,0.0.0.0:8000]
+```
+
+Studio:
+
+```
+$ rake cms[dev,0.0.0.0:8001]
+```
+
+Once started, open the following URLs in your browser:
+
+* Learning management system (LMS): http://192.168.20.40:8000/ 
+* Studio (CMS): http://192.168.20.40:8001/
+
+You can develop by editing the files directly in the `edx-platform/` directory you 
+downloaded before, you don't need to connect to the VM to edit them (the VM uses
+those files to run edX, mirroring the folder in `/edx/edx-platform`).
+
+Stopping & starting
+-------------------
+
+To stop the VM (from your `edx-platform/` directory):
+
+```
+$ vagrant halt
+```
+
+To restart:
+
+```
+$ vagrant up
+```
+
+or, to start without attempting to update the dependencies:
+
+```
+$ vagrant up --no-provision
+```
+
+Troubleshooting
+---------------
+
+### Reinstalling
+
+If something goes wrong, you can easily recreate the installation from scratch by 
+typing:
+
+```
+$ vagrant destroy -f && vagrant up
+```
+
+This will delete the current VM, create a new VM, re-install all the dependencies,
+and reconfigure.
+
+### "Mounting NFS shared folders failed"
+
+If you get the following error message when you run `$ vagrant up`:
+
+```
+It appears your machine doesn't support NFS, or there is not an
+adapter to enable NFS on this machine for Vagrant. Please verify
+that `nfsd` is installed on your machine, and try again. If you're
+on Windows, NFS isn't supported.
+```
+
+You need to install NFS. Under Debian/Ubuntu, for example:
+
+```
+$ sudo apt-get install nfs-common nfs-kernel-server
+```
+
+Installation - Advanced
+=======================
+
+Note: The following installation instructions are for advanced users & developers
+who are familiar with setting up Python, Ruby & node.js virtual environments.
+Even if you know what you are doing, edX has a large code base with multiple 
+dependencies, so you might still want to use the method described above the
+first time, as Vagrant helps avoiding issues due to the different environments.
 
 There is a `scripts/create-dev-env.sh` that will attempt to set up a development
 environment.

Vagrantfile

+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+Vagrant.configure("2") do |config|
+  config.vm.box = "precise32"
+  config.vm.box_url = "http://files.vagrantup.com/precise32.box"
+
+  config.vm.network :forwarded_port, guest: 8000, host: 9000
+  config.vm.network :forwarded_port, guest: 8001, host: 9001
+
+  # Create a private network, which allows host-only access to the machine
+  # using a specific IP.
+  config.vm.network :private_network, ip: "192.168.20.40"
+
+  nfs_setting = RUBY_PLATFORM =~ /darwin/ || RUBY_PLATFORM =~ /linux/
+  config.vm.synced_folder ".", "/edx/edx-platform", id: "vagrant-root", :nfs => nfs_setting
+
+  # Make it so that network access from the vagrant guest is able to
+  # use SSH private keys that are present on the host without copying
+  # them into the VM.
+  config.ssh.forward_agent = true
+
+  config.vm.provider :virtualbox do |vb|
+    # Use VBoxManage to customize the VM. For example to change memory:
+    vb.customize ["modifyvm", :id, "--memory", "1024"]
+
+    # This setting makes it so that network access from inside the vagrant guest
+    # is able to resolve DNS using the hosts VPN connection.
+    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
+  end
+
+  config.vm.provision :shell, :path => "scripts/vagrant-provisioning.sh"
+end

scripts/vagrant-provisioning.sh

+#!/bin/bash -e
+#
+# Copyright (C) 2013 edX <info@edx.org>
+#
+# Authors: Xavier Antoviaque <xavier@antoviaque.org>
+#
+# This software's license gives you freedom; you can copy, convey,
+# propagate, redistribute and/or modify this program under the terms of
+# the GNU Affero General Public License (AGPL) as published by the Free
+# Software Foundation (FSF), either version 3 of the License, or (at your
+# option) any later version of the AGPL published by the FSF.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero
+# General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with this program in a file in the toplevel directory called
+# "AGPLv3".  If not, see <http://www.gnu.org/licenses/>.
+
+
+###############################################################################
+
+# vagrant-provisioning.sh:
+#
+# Script to setup base environment on Vagrant, based on `precise32` image
+# Runs ./scripts/create-dev-env.sh for the actual setup
+#
+# This script is ran by `$ vagrant up`, see the README for more explanations
+
+
+# APT - Packages ##############################################################
+
+apt-get update
+apt-get install -y python-software-properties vim
+
+
+# Curl - No progress bar ######################################################
+
+[[ -f ~vagrant/.curlrc ]] || echo "silent show-error" > ~vagrant/.curlrc
+chown vagrant.vagrant ~vagrant/.curlrc
+
+
+# SSH - Known hosts ###########################################################
+
+# Github
+([[ -f ~vagrant/.ssh/known_hosts ]] && grep "zBX7bKA= ssh" ~vagrant/.ssh/known_hosts) || {
+    echo "|1|4DtBcMsTM4zgl/jTS7h3ZkmS/Vc=|XkRnn2xEhr8ixOxeskJAzBX7bKA= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==" >> ~vagrant/.ssh/known_hosts
+}
+([[ -f ~vagrant/.ssh/known_hosts ]] && grep "jO3J5bvw= ssh" ~vagrant/.ssh/known_hosts) || {
+    echo "|1|9rANf/qOAPgKH/TXpGuZCAgGxMs=|x9VYWEDI8kiotbhhNXqjO3J5bvw= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==" >> ~vagrant/.ssh/known_hosts
+}
+chown vagrant.vagrant ~vagrant/.ssh/known_hosts
+
+
+# edX - Development environment ###############################################
+
+chown vagrant.vagrant /edx
+
+# For convenience with `vagrant ssh`, the `edx-plateform` virtualenv is always 
+# loaded after the first run, so we need to deactivate that behavior to run
+# `create-dev-env.sh`.
+[[ -f ~vagrant/.bash_profile ]] && {
+    mv ~vagrant/.bash_profile ~vagrant/.bash_profile.bak
+}
+sudo -u vagrant -i bash -c "cd /edx/edx-platform && ./scripts/create-dev-env.sh -ynq"
+
+
+# Virtualenv - Always load ####################################################
+
+([[ -f ~vagrant/.bash_profile ]] && grep "edx-platform/bin/activate" ~vagrant/.bash_profile) || {
+    echo -e "\n. /home/vagrant/.virtualenvs/edx-platform/bin/activate\n" >> ~vagrant/.bash_profile
+}
+
+
+# Directory ###################################################################
+
+grep "cd /edx/edx-platform" ~vagrant/.bash_profile || {
+    echo -e "\ncd /edx/edx-platform\n" >> ~vagrant/.bash_profile
+}
+
+
+# End #########################################################################
+
+cat << EOF
+==============================================================================
+Success!
+==============================================================================
+
+Now, from the virtual machine (connect with "vagrant ssh" if vagrant didn't
+log you in already), you can start Studio & LMS with the following commands:
+
+- Learning management system (LMS):
+    $ rake lms[cms.dev,0.0.0.0:8000]
+
+    =>  http://192.168.20.40:8000/
+
+- Studio: 
+    $ rake cms[dev,0.0.0.0:8001]
+
+    => http://192.168.20.40:8001/
+
+
+See the README for details.
+
+
+EOF
+
+