Allow cinder operations with only auth_token

This uses the same technique as Horizon for auth_token operations.

Specifically, the cinder endpoint is found directly from keystone
and the auth_token and management_url are set on cinderclient
after it has been created.

Client libs are in theory capable of looking up their own endpoints
given an auth_token, but in practice this is the code-path least
travelled and there are many issues. I think it is best to do what
Horizon does, since all Horizon operations use only a token and always
provide the endpoint to the client lib.

Tested by launching a stack with and without the --token-only flag

Also tested using Horizon, which is auth_token only

Part of blueprint auth-token-only

Change-Id: Iea9159299ad3f354bcc768c9ac1172d6d9f814a8
Pass in endpoint url for swift auth_token auth

This aligns swift auth_token only authentication with the
way Horizon does it, and avoids python-swiftclient bug #1160172

Tested by launching a stack with and without the --token-only flag

Also tested using Horizon, which is auth_token only

Part of blueprint auth-token-only

Change-Id: I0622f76e93df4f7353fc0cc61dc962b6c8f0be11
Allow nova operations with only auth_token

This uses the same technique as Horizon for auth_token operations.

Specifically, the nova endpoint is found directly from keystone
and the auth_token and management_url are set on novaclient
after it has been created.

Note that the explicit call to authenticate() is not required
and actually breaks the auth_token case.

Tested by launching a stack with and without the --token-only flag

Also tested using Horizon, which is auth_token only

Part of blueprint auth-token-only

Change-Id: Ic11a838b96a4b5130cb2ac9d685e8a97c9d0a0ad
Pass in endpoint url for quantum auth_token auth

This aligns quantum auth_token only authentication with the
way Horizon does it.

Tested by launching a stack with and without the --token-only flag

Also tested using Horizon, which is auth_token only

Part of blueprint auth-token-only

Change-Id: Ic6d471de527951415ef4858cbbff27cf60561924
No longer pass no_cache=True to novaclient create

The default is now os_cache=False, so default behaviour will not
use a keyring that prompts for a password.

This was committed on 2012-12-12 and released in
python-novaclient 2.11.0 on 2013-02-11

Part of blueprint auth-token-only

Change-Id: Id2846b2e344f8e3321240795aebf9a59ddad711a
Add Getting Started Guides the developer doc's

These have been copied from the wiki.

DocImpact
Signed-off-by: Angus Salkeld <asalkeld@redhat.com>

Change-Id: I4c93bc5a1811e674cef3c7868e7cf9a457c12dea
Merge "Allow cinder operations with only auth_token"
Merge "Pass in endpoint url for swift auth_token auth"
Merge "Allow nova operations with only auth_token"
Merge "Pass in endpoint url for quantum auth_token auth"
Merge "No longer pass no_cache=True to novaclient create"
Merge "Add Getting Started Guides the developer doc's"