zaqar-bench should use credentials gathered from os_client_config

[Eva Balycheva]

Currently zaqar-bench can't benchmark Zaqar while Zaqar is using keystone authentication backend. It would be good to make it possible.

This can be done easily with os_client_config lib which gets authentication parameters either from "clouds.yaml" or keystone auth environment variables.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/255051
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=1b8334b35a0d01b828ba975ab7d778f403cc7932
Submitter: Jenkins
Branch: master

commit 1b8334b35a0d01b828ba975ab7d778f403cc7932
Author: Eva Balycheva <email address hidden>
Date: Sat Nov 28 07:42:09 2015 +0300

    Make zaqar-bench use credentials from os_client_config

    Currently zaqar-bench can't benchmark Zaqar while Zaqar is using
    keystone authentication backend.

    This patch makes it possible by using os_client_config library. The
    library gets authentication parameters from "clouds.yaml". If keystone
    authentication environment variables present, they override values from
    "clouds.yaml". The aquired parameters then passed to constructors of
    each python-zaqarclient's Client object used in zaqar-bench.

    The patch also makes benchmark queue names reusable across all
    zaqar-bench parts and by this fixes the old DRY princible bug.

    To use zaqar-bench with keystone authentication the user must
    explicitly set OS_AUTH_STRATEGY=keystone as environment variable
    before running the tool. Otherwise the default 'noauth' auth strategy
    will be used. This allows the user to run zaqar-bench as usual.

    This patch also adds option "--api-version" with it's short version
    "api" to zaqar-bench which defaults to Zaqar API v2.

    Change-Id: I0a7aaeaeac6da1b2c9f08fbfdddd467de5747a28
    Closes-Bug: 1523752

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/zaqar 2.0.0.0b2 development milestone.