Juju quickstart should support vagrant

[Jorge Castro]

We'd like to see:

    juju quickstart developer

Then

a) Install vagrant
b) Set up a barebones Vagrantfile
c) Downloads the Ubuntu Juju vagrantbox
c) Set up shared directories between host OS and the box.
d) Set up a charm structure in this charm directory.

This way people can just get started with a charm developer environment on all three OSes with minimal effort. We talked about this a little bit at the cloud sprint and this bug is meant to be a metabug tracking the workflow.

[Francesco Banconi (frankban)]

Some notes:
a) Install vagrant

OSX:
brew install caskroom/cask/brew-cask
brew cask install vagrant

UBUNTU:
$ apt-get install vagrant

Detect whether the user already has vbox or vmware installed: if so, use those
with a disclaimer for vmware (not tested, experimental mode).
If none is installed, tell the user to go install vbox (link to vagrant docs).

b) Set up a barebones Vagrantfile

In this example, quickstart is just the arbitrary name assigned to the machine.
$ vagrant add quickstart http://cloud-images.ubuntu.com/vagrant/trusty/current/[name with juju in it]
!!! We need a vagrant image for vmware.
The command above creates a machine template in ~/.vagrant.d/boxes/quickstart
$ vagrant init quickstart
It creates a new configuration for the machine in the current directory.
$ vagrant up
The above must be run from the directory containing the config file, it starts
the box and wait until it's ready. Since we used the "juju" vagrant file, when
the machine is bootstrapped also a juju environment is bootstrapped. Also the
Juju GUI is deployed automatically on the LXC environment.

c) Downloads the Ubuntu Juju vagrantbox
???

c) Set up shared directories between host OS and the box.
This is already done by the ubuntu juju vagrant images.

d) Set up a charm structure in this charm directory.
This is out of scope for quickstart.

Done.