Add support for the Joyent provider.

Add support for the Joyent provider.

Tests: `make check`.

QA:
QA is not straightforward for this branch, due to the
fact this needs to be tested on a not yet released
juju-core. Sorry about that.
1) Check out the 1.18 juju-core branch (lp:juju-core/1.18), 
   and compile it.
2) Edit the quickstart/settings.py file included in this branch:
   set `JUJU_CMD` to point to the juju 1.18 path.
3) Sign up for a Joyent account from http://www.joyent.com/.
4) Run `.venv/bin/python juju-quickstart -i` and create a new
   joyent environment: DO NOT bootstrap it from quickstart, just
   create it and exit (^X).
5) Use juju 1.18 to bootstrap the joyent account, e.g.
   `juju bootstrap -e joyent --upload-tools`. This is required
   because quickstart does not support uploading tools.
6) After a minute, and while the environment is bootstrapping,
   open another terminal and re-run quickstart, select the
   joyent account you created and hit "use" 
   (or just invoke quickstart with `-e joyent`).
7) Ensure everything proceeds as expected, and wait
   until the quickstart opens the GUI.
Done, destroy the environment, thank you!

https://code.launchpad.net/~frankban/juju-quickstart/joyent/+merge/214022

(do not edit description out of merge proposal)

[frankban, 2014-04-03 13:20:57]

Please take a look.

[bac, 2014-04-03 15:20:54]

Code LGTM.  On to QA.

https://codereview.appspot.com/83880044/diff/1/quickstart/tests/models/test_f...
File quickstart/tests/models/test_fields.py (right):

https://codereview.appspot.com/83880044/diff/1/quickstart/tests/models/test_f...
quickstart/tests/models/test_fields.py:468: field.validate(unicode(__file__))
Nice use of __file__.  Nicer then creating a temp file and destroying it.

[bac, 2014-04-03 17:23:49]

When doing QA and bootstrapping the joyent environment I get 

http://paste.ubuntu.com/7199671/

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py
File quickstart/models/envs.py (right):

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py#newc...
quickstart/models/envs.py:621: 'manta-user', required=True,
I'm running quickstart for the first time to set up joyent.  I don't know what
the manta username and ssh keys are.  Are they the same as my SDC ones?  I only
have one Joyent username and ssh key.

Kind of confusing.

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py#newc...
quickstart/models/envs.py:634: 'private-key-path', label='provate key path',
required=False,
typo: provate

[bac, 2014-04-03 20:06:11]

For the private key file path, the default is listed as ~/.ssh/id_rsa

If you try to enter '~/.ssh/id_rsa_joyent', quickstart does not properly expand
the path and gives an error.  Using '/home/bac/.ssh/id_rsa_joyent' was accepted.

[bac, 2014-04-03 20:22:37]

QA-OK after lots of struggles, mainly the issue with passphrase-protected ssh
key, which is not quickstart's problem.

Though if juju doesn't screen for it perhaps we should?

[frankban, 2014-04-04 08:07:54]

On 2014/04/03 20:06:11, bac wrote:
> For the private key file path, the default is listed as ~/.ssh/id_rsa
> 
> If you try to enter '~/.ssh/id_rsa_joyent', quickstart does not properly
expand
> the path and gives an error.  Using '/home/bac/.ssh/id_rsa_joyent' was
accepted.

Good catch. Fixed the FilePathField validation to use expanduser.

[frankban, 2014-04-04 08:10:05]

On 2014/04/03 20:22:37, bac wrote:
> QA-OK after lots of struggles, mainly the issue with passphrase-protected ssh
> key, which is not quickstart's problem.
> 
> Though if juju doesn't screen for it perhaps we should?

Thanks a lot Brad, and sorry again for the difficult QA.
As you mentioned, this is something that must be handled by juju-core, so, given
this will land later, I'd be inclined to wait for the core fix.

[frankban, 2014-04-04 08:11:26]

Please take a look.

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py
File quickstart/models/envs.py (right):

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py#newc...
quickstart/models/envs.py:621: 'manta-user', required=True,
On 2014/04/03 17:23:50, bac wrote:
> I'm running quickstart for the first time to set up joyent.  I don't know what
> the manta username and ssh keys are.  Are they the same as my SDC ones?  I
only
> have one Joyent username and ssh key.
> 
> Kind of confusing.

Good point Brad, updated the fields description.

https://codereview.appspot.com/83880044/diff/1/quickstart/models/envs.py#newc...
quickstart/models/envs.py:634: 'private-key-path', label='provate key path',
required=False,
On 2014/04/03 17:23:50, bac wrote:
> typo: provate

Done.

[bac, 2014-04-04 12:19:49]

Changes all LGTM.  Thanks.

[frankban, 2014-04-10 09:39:03]

*** Submitted:

Add support for the Joyent provider.

Tests: `make check`.

QA:
QA is not straightforward for this branch, due to the
fact this needs to be tested on a not yet released
juju-core. Sorry about that.
1) Check out the 1.18 juju-core branch (lp:juju-core/1.18), 
   and compile it.
2) Edit the quickstart/settings.py file included in this branch:
   set `JUJU_CMD` to point to the juju 1.18 path.
3) Sign up for a Joyent account from http://www.joyent.com/.
4) Run `.venv/bin/python juju-quickstart -i` and create a new
   joyent environment: DO NOT bootstrap it from quickstart, just
   create it and exit (^X).
5) Use juju 1.18 to bootstrap the joyent account, e.g.
   `juju bootstrap -e joyent --upload-tools`. This is required
   because quickstart does not support uploading tools.
6) After a minute, and while the environment is bootstrapping,
   open another terminal and re-run quickstart, select the
   joyent account you created and hit "use" 
   (or just invoke quickstart with `-e joyent`).
7) Ensure everything proceeds as expected, and wait
   until the quickstart opens the GUI.
Done, destroy the environment, thank you!

R=bac
CC=
https://codereview.appspot.com/83880044