Before, the quota API used to fail to perform calls with specified
keystone API v2, because the keystone client used in code was set
to v3 and all quota operations used to assume that the user would
use only keystone API v3.
Now, we use the generic client, which discovers the version of the
keystone API, so depending on that, the quota API can perform
appropriate operations.
Change-Id: I32595a37a9fe74ede77c92f76e0865f4c9371f65
Closes-Bug: 1517043
(cherry picked from commit ffd32c7e1947189eee701c417d9f72982f720a11)
Reviewed: https:/ /review. openstack. org/262162 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=bd3b972e72b b17b0a0f08f972a 7bcdb39c6dd35f
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit bd3b972e72bb17b 0a0f08f972a7bcd b39c6dd35f
Author: Szymon Borkowski <email address hidden>
Date: Thu Dec 17 13:18:31 2015 +0100
Quota API is now compatible with keystone API v2
Before, the quota API used to fail to perform calls with specified
keystone API v2, because the keystone client used in code was set
to v3 and all quota operations used to assume that the user would
use only keystone API v3.
Now, we use the generic client, which discovers the version of the
keystone API, so depending on that, the quota API can perform
appropriate operations.
Change-Id: I32595a37a9fe74 ede77c92f76e086 5f4c9371f65 eee701c417d9f72 982f720a11)
Closes-Bug: 1517043
(cherry picked from commit ffd32c7e1947189