feat(Vagrantfile): use "virtio" network devices by default
chore(controller): update psycopg to 2.5.4

http://pythonhosted.org//psycopg2/news.html#what-s-new-in-psycopg-2-5-4
http://pythonhosted.org//psycopg2/news.html#what-s-new-in-psycopg-2-5-3
ref(cache): just use go. remove bash script
Merge pull request #2141 from mboersma/update-psycopg

chore(controller): update psycopg to 2.5.4
Typo
Merge pull request #2165 from glomium/patch-1

Typo
Merge pull request #2157 from mboersma/use-vagrant-virtio

feat(Vagrantfile): use "virtio" network devices in virtualbox
chore(builder): update Docker engine to 1.3.0
fix(controller): use docker cache
Merge pull request #2166 from mboersma/builder-docker-130

chore(builder): update Docker engine to 1.3.0
Merge pull request #2143 from aledbf/logger_just_use_go

ref(cache): just use go. remove bash script
Merge pull request #2170 from aledbf/fix_controller_docker_cache

fix(controller): use docker cache
ref(controller): disable CSRF token authn/authz
ref(controller): switch to token-based authn

When pulling out CSRF tokens from the authentication requirements, we
are still relying on cookies. This is great from a CSRF attacker's
standpoint as attackers can easily `<iframe>` the site that utilizes the
API, generate a POST request and re-use the existing cookie. Using
token-based authn fixes this because there will be no existing authn
cookie in the request. With this change, we are also not vulnerable to
XSRF attacks either because we do not store a validated login cookie
in the browser (yay!).
test(integration): add client.json tests