Add virtualenv configs for stagecraft and admin

 - Creates the virtualenv so workon $projectname will work
 - Installs the requirements.txt
 - Exports required environment variables to run the project
 - Sets a project dir so workon $projectname will cd to correct
   directory
Add extra disks to boxes that need it

This isnt a very nice fix but is easier than the method in
https://www.pivotaltracker.com/story/show/81180896
Disable Mongo HTTP interface

MongoDB by default provides an HTTP interface running by default on TCP
port 28017 which provides the “home” status page. This provides a vast
amount of information and the interface is not recommended for
production environments.
Merge pull request #623 from alphagov/feature/disable-mongo-http-interface

Disable Mongo HTTP interface
Pin our version of mongodb

We recently reprovisioned our mongo machines, and by a happy accident
upgraded to a more recent version.

This change explicitly controls which version we’re using, so that it if
we add more nodes, they will all be running the  same version until we
choose to upgrade.
Merge pull request #625 from alphagov/feature/explicit-mongodb-version

Pin our version of mongodb
Disk growth check

This should check the disk growth over the last hour, and alert if it is
more than 10G and warn if more than 5. Prompted by the issues we have
been having with elasticsearch filling the disk, as it happens too
quickly for a standard disk space alert to happen
Merge pull request #626 from alphagov/attempt-disk-growth-check

Disk growth check
Merge pull request #615 from alphagov/add-virtualenv-configs

Add virtualenv configs for stagecraft and admin
Merge pull request #620 from alphagov/extra-disks-for-vagrant

Add extra disks to boxes that need it
Add logic around vmware specific clause

- Really temporary fix for suckers in the team who aren't lucky enough to have :money_with)wings: vmware :money_with_wings: as their vm provider
- It's difficult to switch on current provider in your vagrantfile, there are some workarounds listed here: https://github.com/mitchellh/vagrant/issues/1867
- Will have a bash at refactoring to match some of those solutions, but this temporarily fixes this issue: http://cl.ly/image/0n0m0E1F3b2y
Merge pull request #629 from alphagov/notallvms

Add logic around vmware specific clause
lint
Use Azul Zulu JDK rather than Oracle

This is an upgrade from 

```
java version "1.7.0_09"
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
```

to

```
openjdk version "1.8.0_20"
OpenJDK Runtime Environment (Zulu 8.3.0.1-linux64) (build 1.8.0_20-b26)
OpenJDK 64-Bit Server VM (Zulu 8.3.0.1-linux64) (build 25.20-b23, mixed mode)
```

As a member of the technical community in GDS,
I would like to understand my options when it comes to choosing
technology
So that I can make the best choice for my context

Typically, that involves experience and data. I’ve volunteered us to try
the Azul OpenJDK port for maturity and stability in production.

Exciting, eh?
Merge pull request #630 from alphagov/feature/zulu

Use Azul Zulu JDK rather than Oracle