Activity log for bug #1523752

Date Who What changed Old value New value Message
2015-12-08 04:02:58 Eva Balycheva bug added bug
2015-12-08 04:03:21 Eva Balycheva zaqar: assignee Eva Balycheva (ubershy)
2015-12-08 04:04:22 Eva Balycheva description As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as this parameter to make zaqar-bench able to work with no keystone auth environment variables set, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth environment variables set, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables.
2015-12-08 04:04:53 Eva Balycheva description As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth environment variables set, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables.
2015-12-08 04:06:27 Eva Balycheva description As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables. Zaqar-bench is not working. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables.
2015-12-08 04:07:26 Eva Balycheva description Zaqar-bench is not working. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentification parameters either from "clouds.yaml" or keystone auth environment variables. Zaqar-bench is not working. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentication parameters either from "clouds.yaml" or keystone auth environment variables.
2015-12-08 04:07:55 Md Nadeem zaqar: status New Confirmed
2015-12-09 02:52:13 OpenStack Infra zaqar: status Confirmed In Progress
2015-12-19 05:52:24 Eva Balycheva description Zaqar-bench is not working. As python-zaqarclient recently changed it's default auth backend from 'noauth' to 'keystone', zaqar-bench should instantiate python-zaqarclient Client objects with explicit auth backend parameter. Of course we can just pass 'noauth' as the parameter value to make zaqar-bench able to work with no keystone auth as it was before, but Zaqar team decided to make zaqar-bench flexible and able also to use 'keystone' auth. This can be done easily with os_client_config lib which gets authentication parameters either from "clouds.yaml" or keystone auth environment variables. 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.
2016-01-18 01:08:00 OpenStack Infra zaqar: status In Progress Fix Released