Cannot authenticate with Keystone using credentials

[Salvatore Orlando]

It's probably not reliable to rely on passing a token to the kuryr service.
If it's a valid token it will eventually expire.
It it's the 'admin token', using it is a practice which is not recommended in production (for obvious reasons).

Adding support for password authentication should be easy peasy.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/221336

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/221336
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=e3383a6dc29abe1777e43d7889f74f27db37a0ae
Submitter: Jenkins
Branch: master

commit e3383a6dc29abe1777e43d7889f74f27db37a0ae
Author: Salvatore Orlando <email address hidden>
Date: Tue Sep 8 07:36:03 2015 -0700

    Enable keystone password authentication

    Enable Kuryr to authenticate with keystone not only using service
    tokens but also credentials.

    The patch also does a minimal refactoring by moving the code for
    retrieving a neutron client into kuryr.utils

    Change-Id: Ib230da6e6484646436525e15ab8e93fe671800ec
    Closes-Bug: #1493382