identity tests don't take into account tenant isolation

[Jesse Keating]

http://git.openstack.org/cgit/openstack/tempest/tree/tempest/api/identity/base.py#n32 this tries to use a test user from the config file, which isn't defined because I'm using tenant isolation for my testing. So this test blows up, and spits out a traceback like https://gist.github.com/j2sol/d1a32fb16d3503c34439

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/165548
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=db9721dfecd99421f89ca9e263a97271e5f79ca0
Submitter: Jenkins
Branch: master

commit db9721dfecd99421f89ca9e263a97271e5f79ca0
Author: Matthew Treinish <email address hidden>
Date: Wed Mar 18 14:21:28 2015 -0400

    Respect configured credential provider everywhere

    This commit changes all the uses of the old AdminManager and Manager()
    constructs to use cls.isolated_creds to provide user credentials from
    whatever the configured credential provider is being used instead of
    assuming it's the non-locking accounts provider without an accounts.yaml
    file. As part of this we need to add a heat option for the stack owner
    role so that we can request the creds by that role. The heat tests were
    previously making an implicit assumption about the configured user having
    that role assigned. Which while true in devstack today, it isn't
    necessarily the case everywhere.

    Depends-On: Id98a83f0a716de0fdb5f36d03407364830e8fa5f
    Closes-Bug: #1433723
    Change-Id: Ie071cb2cb6add591a60c9d76a12c95b7fb5ee539