Permalink
Browse files

Add: Vagrant support for testing.

  • Loading branch information...
1 parent 56993cd commit 5d012deabbb1f71d4a68e560507c1b246273b003 @nisaacson nisaacson committed Dec 5, 2013
Showing with 204 additions and 0 deletions.
  1. +1 −0 .gitignore
  2. +1 −0 .travis.yml
  3. +118 −0 Vagrantfile
  4. +1 −0 clean_vm.sh
  5. +83 −0 test/provision_vagrant.sh
View
@@ -1,2 +1,3 @@
node_modules
npm-debug.log
+.vagrant
View
@@ -7,6 +7,7 @@ before_install:
- 'sudo bash -c "echo deb http://apt.basho.com $(lsb_release -sc) main > /etc/apt/sources.list.d/basho.list"'
- "sudo apt-get update"
- "yes n | sudo apt-get install riak --force-yes"
+ - "cd /etc/riak && sudo sed -i.bak -e 0,/\"enabled, false\"/{s/\"enabled, false\"/\"enabled, true\"/} app.config"
- "sudo service riak start"
before_script: sudo /usr/sbin/search-cmd install test
View
@@ -0,0 +1,118 @@
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
+VAGRANTFILE_API_VERSION = "2"
+
+Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
+ # All Vagrant configuration is done here. The most common configuration
+ # options are documented and commented below. For a complete reference,
+ # please see the online documentation at vagrantup.com.
+
+ # Every Vagrant virtual environment requires a box to build off of.
+ config.vm.box = "precise64_virtualbox"
+
+ # The url from where the 'config.vm.box' box will be fetched if it
+ # doesn't already exist on the user's system.
+ config.vm.box_url = "http://files.vagrantup.com/precise64.box"
+ config.vm.provision "shell", path: "test/provision_vagrant.sh"
+ # Create a forwarded port mapping which allows access to a specific port
+ # within the machine from a port on the host machine. In the example below,
+ # accessing "localhost:8080" will access port 80 on the guest machine.
+ # config.vm.network :forwarded_port, guest: 80, host: 8080
+
+ # Create a private network, which allows host-only access to the machine
+ # using a specific IP.
+ # config.vm.network :private_network, ip: "192.168.33.10"
+
+ # Create a public network, which generally matched to bridged network.
+ # Bridged networks make the machine appear as another physical device on
+ # your network.
+ # config.vm.network :public_network
+
+ # If true, then any SSH connections made will enable agent forwarding.
+ # Default value: false
+ # config.ssh.forward_agent = true
+
+ # Share an additional folder to the guest VM. The first argument is
+ # the path on the host to the actual folder. The second argument is
+ # the path on the guest to mount the folder. And the optional third
+ # argument is a set of non-required options.
+ # config.vm.synced_folder "../data", "/vagrant_data"
+
+ # Provider-specific configuration so you can fine-tune various
+ # backing providers for Vagrant. These expose provider-specific options.
+ # Example for VirtualBox:
+ #
+ # config.vm.provider :virtualbox do |vb|
+ # # Don't boot with headless mode
+ # vb.gui = true
+ #
+ # # Use VBoxManage to customize the VM. For example to change memory:
+ # vb.customize ["modifyvm", :id, "--memory", "1024"]
+ # end
+ #
+ # View the documentation for the provider you're using for more
+ # information on available options.
+
+ # Enable provisioning with Puppet stand alone. Puppet manifests
+ # are contained in a directory path relative to this Vagrantfile.
+ # You will need to create the manifests directory and a manifest in
+ # the file precise64_virtualbox.pp in the manifests_path directory.
+ #
+ # An example Puppet manifest to provision the message of the day:
+ #
+ # # group { "puppet":
+ # # ensure => "present",
+ # # }
+ # #
+ # # File { owner => 0, group => 0, mode => 0644 }
+ # #
+ # # file { '/etc/motd':
+ # # content => "Welcome to your Vagrant-built virtual machine!
+ # # Managed by Puppet.\n"
+ # # }
+ #
+ # config.vm.provision :puppet do |puppet|
+ # puppet.manifests_path = "manifests"
+ # puppet.manifest_file = "site.pp"
+ # end
+
+ # Enable provisioning with chef solo, specifying a cookbooks path, roles
+ # path, and data_bags path (all relative to this Vagrantfile), and adding
+ # some recipes and/or roles.
+ #
+ # config.vm.provision :chef_solo do |chef|
+ # chef.cookbooks_path = "../my-recipes/cookbooks"
+ # chef.roles_path = "../my-recipes/roles"
+ # chef.data_bags_path = "../my-recipes/data_bags"
+ # chef.add_recipe "mysql"
+ # chef.add_role "web"
+ #
+ # # You may also specify custom JSON attributes:
+ # chef.json = { :mysql_password => "foo" }
+ # end
+
+ # Enable provisioning with chef server, specifying the chef server URL,
+ # and the path to the validation key (relative to this Vagrantfile).
+ #
+ # The Opscode Platform uses HTTPS. Substitute your organization for
+ # ORGNAME in the URL and validation key.
+ #
+ # If you have your own Chef Server, use the appropriate URL, which may be
+ # HTTP instead of HTTPS depending on your configuration. Also change the
+ # validation key to validation.pem.
+ #
+ # config.vm.provision :chef_client do |chef|
+ # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
+ # chef.validation_key_path = "ORGNAME-validator.pem"
+ # end
+ #
+ # If you're using the Opscode platform, your validator client is
+ # ORGNAME-validator, replacing ORGNAME with your organization name.
+ #
+ # If you have your own Chef Server, the default validation client name is
+ # chef-validator, unless you changed the configuration.
+ #
+ # chef.validation_client_name = "ORGNAME-validator"
+end
View
@@ -0,0 +1 @@
+vagrant destroy -f; vagrant up --no-provision; vagrant reload; vagrant provision
View
@@ -0,0 +1,83 @@
+#!/usr/bin/env bash
+
+function install_from_apt {
+ TOOL=$1
+ echo "-----> Install $TOOL if needed"
+ command -v $TOOL > /dev/null
+ if [[ $? -eq 0 ]]; then
+ echo " $TOOL already installed"
+ return
+ fi
+ echo " $TOOL not installed, begin installation from apt"
+ sudo apt-get install -qqy curl
+ command -v $TOOL > /dev/null
+ if [[ $? -eq 0 ]]; then
+ echo " $TOOL installed correctly"
+ return
+ fi
+ echo "$TOOL failed to install correctly"
+ exit 1
+}
+
+function install_node {
+ echo "-----> Install nodejs if needed"
+ command -v node > /dev/null
+ if [[ $? -eq 0 ]]; then
+ echo " nodejs already installed"
+ return
+ fi
+ echo " nodejs not installed, begin installation from ppa now"
+ sudo apt-get update
+ sudo apt-get install -y -qq python-software-properties python g++ make
+ sudo add-apt-repository -y ppa:chris-lea/node.js
+ sudo apt-get update -y
+ sudo apt-get install -qqy nodejs
+ command -v node > /dev/null
+ if [[ $? -eq 0 ]]; then
+ echo " nodejs installed correctly"
+ return
+ fi
+ echo "nodejs failed to install correctly"
+ exit 1
+}
+
+function install_riak {
+ echo "-----> Install riak if needed"
+ command -v riak > /dev/null
+ if [[ $? -eq 0 ]]; then
+ echo " riak already installed"
+ return
+ fi
+ echo " riak not installed, begin installation from ppa now"
+ curl http://apt.basho.com/gpg/basho.apt.key | sudo apt-key add -
+ sudo bash -c "echo deb http://apt.basho.com $(lsb_release -sc) main > /etc/apt/sources.list.d/basho.list"
+ sudo apt-get update
+ sudo apt-get install riak
+ command -v riak > /dev/null
+ if [[ $? -ne 0 ]]; then
+ echo " riak failed to install correctly"
+ exit 1
+ fi
+
+ # switch to leveldb as the riak backend
+ echo "change riak backend to leveldb to support secondary indices"
+ cd /etc/riak && sudo sed -i.bak -e s/riak_kv_bitcask_backend/riak_kv_eleveldb_backend/g app.config
+ cd /etc/riak && sudo sed -i.bak -e 0,/"enabled, false"/{s/"enabled, false"/"enabled, true"/} app.config
+ sudo riak start
+ if [[ $? -ne 0 ]]; then
+ echo " riak failed to start correctly"
+ exit 1
+ fi
+ echo " riak start completed"
+ sleep "5s"
+ riak ping
+ if [[ $? -ne 0 ]]; then
+ echo " riak failed to install correctly"
+ exit 1
+ fi
+ echo "riak install correctly"
+}
+
+install_from_apt "curl"
+install_node
+install_riak

0 comments on commit 5d012de

Please sign in to comment.