consume clouds.yaml from devstack in functional tests

[Monty Taylor]

Some client functional tests write out a config file for auth credentials to work around tox env var handling. However, devstack already writes out clouds.yaml which has auth information and is consumed by python-openstackclient during devstack.

Instead of reading openrc and then writing out a file, just use the one that's there.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/236713
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=84538d8870b2204cb9ea0a24217e5b3cb6f38b4f
Submitter: Jenkins
Branch: master

commit 84538d8870b2204cb9ea0a24217e5b3cb6f38b4f
Author: Monty Taylor <email address hidden>
Date: Sun Oct 18 12:16:25 2015 -0400

    Use clouds.yaml from devstack for functional tests

    devstack produces a file called clouds.yaml already with credentials in
    it. Rather than producing our own config file to run functional tests,
    just consume the clouds.yaml file that's already there.

    Closes-Bug: #1507386
    Change-Id: I82c071b2cd903b9578d1f2ec515882c815812692

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/236730
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=51b2e71add3d63dccff98b22a803339e9dfae267
Submitter: Jenkins
Branch: master

commit 51b2e71add3d63dccff98b22a803339e9dfae267
Author: Monty Taylor <email address hidden>
Date: Sun Oct 18 14:47:56 2015 -0400

    Use clouds.yaml from devstack for functional tests

    devstack produces a file called clouds.yaml already with credentials in
    it. Rather than producing our own config file to run functional tests,
    just consume the clouds.yaml file that's already there.

    Closes-Bug: #1507386
    Change-Id: Ie15b5da2e61f5b35e3bdeb75f0ba21c58ddfca76

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/python-neutronclient 4.0.0 release.