Arvados

{{>toc}}

h1. Hacking prerequisites

The Arvados test suite can run in a Docker container, a VM, or your workstation -- provided a few prerequisites are satisfied.

h2. Host options

h3. Starting on your workstation

If your workstation is a debian wheezy or jessie system -- and you don't mind installing a bunch of packages on your workstation, some of them without apt -- the easiest way to get running is to run tests on bare metal. Skip to "Dependencies".

Other linux distributions should work too with some modifications, but it's probably easier to use a VM.

h3. Starting on a VM

Another option is to create a virtual machine using something like Xen or VirtualBox, and run debian jessie on it. The instructions below assume you have just a few basic requirements:

* SSH server

* sudo (@apt-get install sudo@)

* A user account with sudo privileges

h3. Starting in a docker container

This can get you started quickly, but (unlike the above options) you'll need to remember to use something like @docker commit@ to save your state before shutting down your container.

See http://docker.io for more about installing docker. On debian it looks something like this.

<pre>

echo 'deb http://http.debian.net/debian jessie-backports main' | sudo tee -a /etc/apt/sources.list.d/jessie-backports.list

sudo apt-get install docker.io

sudo adduser $USER docker

# {log out & log back in}

groups

# {should include "docker"}

</pre>

Start up a new container with jessie, make a new user and log in as that user:

<pre>

docker run -it debian:jessie bash

apt-get update

apt-get install sudo

adduser me

adduser me sudo

sudo -u me -i

</pre>

h2. Install dev environment

<pre>

sudo apt-get install bison build-essential fuse gettext git gitolite3 graphviz \

    iceweasel libattr1-dev libfuse-dev libcrypt-ssleay-perl libjson-perl libcurl3 libcurl3-gnutls \

    libcurl4-openssl-dev libpcre3-dev libpq-dev libpython2.7-dev \

    libreadline-dev libssl-dev libxslt1.1 linkchecker lsof nginx perl-modules \

    postgresql python python-epydoc pkg-config sudo virtualenv \

    wget xvfb zlib1g-dev

# ruby 2.1:

sudo apt-get install ruby2.1 ruby2.1-dev || \

(

 set -e

 mkdir -p ~/src

 cd ~/src

 wget http://cache.ruby-lang.org/pub/ruby/2.1/ruby-2.1.6.tar.gz

 tar xzf ruby-2.1.6.tar.gz

 cd ruby-2.1.6

 ./configure --disable-install-doc

 make

 sudo make install

 sudo gem install bundler

)

# go >= 1.3

sudo apt-get install golang=2:1.3.3-1 || \

(

 set -e

 wget https://storage.googleapis.com/golang/go1.4.2.linux-amd64.tar.gz

 sudo tar -C /usr/local -xzf go1.4.2.linux-amd64.tar.gz

 cd /usr/local/bin

 sudo ln -s ../go/bin/* .

)

# phantomjs 1.9.8

(

 set -e

 PJS=phantomjs-1.9.8-linux-x86_64

 wget -P /tmp https://bitbucket.org/ariya/phantomjs/downloads/$PJS.tar.bz2

 sudo tar -C /usr/local -xjf /tmp/$PJS.tar.bz2

 sudo ln -s ../$PJS/bin/phantomjs /usr/local/bin/

)

</pre>

h2. Get the arvados source tree and test scripts

<pre>

cd

git clone https://github.com/curoverse/arvados.git

git clone https://github.com/curoverse/arvados-dev.git

</pre>

...or, if you're a committer with your public key on our git server:

<pre>

cd

git clone git@git.curoverse.com:arvados.git

git clone git@git.curoverse.com:arvados-dev.git

</pre>

h2. Start Postgres

_If you're running in a docker container_ you'll need to start Postgres manually:

<pre>

sudo /etc/init.d/postgresql start

</pre>

(If you're on a regular workstation/server/VM, startup scripts have already taken care of that for you.)

h2. Start X11

In order for the apps/workbench tests to function, firefox needs to have an X11 server (or it will fail to start). If you are on a workstation with a "real" X server, that should work. If not, Xvfb is an X server that renders to a virtual framebuffer so that selenium/firefox tests can run in headless mode. Also make sure that the DISPLAY environment variable is set accordingly.

<pre>

Xvfb :0.0

export DISPLAY=":0.0"

</pre>

h2. Setup groups

Make sure the fuse and docker groups exist (create them if necessary) and that the user who will run the tests is a member of them. 

h2. Create a Postgres user

Create an "arvados" user with "create database" privileges. The test suite will create and drop the arvados_test database as needed.

<pre>

newpw=`tr -cd a-zA-Z </dev/urandom |head -c32`

sudo -u postgres psql -c "create user arvados with createdb encrypted password '$newpw'"

cp -i ~/arvados/services/api/config/database.yml{.sample,} # {.example,}

newpw="$newpw" perl -pi~ -e 's/xxxxxxxx/$ENV{newpw}/' ~/arvados/services/api/config/database.yml

</pre>

h2. Run tests

<pre>

time ~/arvados-dev/jenkins/run-tests.sh WORKSPACE=~/arvados

</pre>

During development, you'll probably want something more like this. It leaves its temp dirs in place after running tests, which allows you to save time with @--skip-install@ or @--only-install sdk/ruby@ and so on.

<pre>

time ~/arvados-dev/jenkins/run-tests.sh WORKSPACE=~/arvados \

 VENVDIR=~/.cache/arvados-venv \

 VENV3DIR=~/.cache/arvados-venv3 \

 GOPATH=~/.cache/arvados-gopath \

 GEMHOME=~/.cache/arvados-gemhome

</pre>