Always use the SQL backend for tokens.

The KVS has a number of drawbacks:

* Requires load balancer to persist connections to a single keystone
 server by token
* Memory will grow out of control until keystone server is restarted
*  At some point kvs lookups get very slow because there are millions of
*  keys in the dict.
* Process restart invalidates all tokens.

see e.g. https://bugs.launchpad.net/tripleo/+bug/1188301
Merge DE1227 - Move Pull from source to the bottom of each proposal
Merge pull request #117 from dirkmueller/release/roxy/master

Passes smoketests..
Merge pull request #119 from dpaterson/pull-req-release-roxy-master-064252f44188e4bb6508e0ee05366574d5d00004

Merge DE1227 - Move Pull from source to the bottom of each proposal [1/1]
Fixed text for keystone barclamp for UI (DE1346)

Conflicts:

	crowbar.yml
Merge pull request #120 from rajinir/pull-req-release-roxy-master-d60e3df0ef23e8f562c46b44efd6dfc72be7a48f

 [1/1]
Delete the tokens that we create to test the password
Merge pull request #123 from rajinir/pull-req-release-roxy-master-f02e053b976be8e3036f8c2e0c321cbaa90343fd

Mesa 1.6.1 merge Delete the tokens that we create to test the password [1/1]