delta/openstack/python-cinderclient.git, branch 1.8.0

Don't enable lazy translation when loading client

2016-05-30T15:14:15+00:00

The change I9c8db9487b554b637a41620c858a7e7abf802879 introduced a
regression in nova and trove. Importing cinderclient.client now calls
_i18n.enable_lazy() which calls oslo_i18n.enable_lazy(). It's wrong to
modify a global variable (oslo_i18n._lazy.USE_LAZY) when a module is
imported.

This change removes the call to _i18n.enable_lazy() from client.py.

Closes-Bug: #1587071
Related-Bug: 1586976
Change-Id: I1512b86815e7248fa226c6969124ddc654145562

Merge "Remove deprecated tempest_lib and use tempest.lib"

2016-05-25T21:49:40+00:00

Merge "Support for cinder backup force delete"

2016-05-23T19:30:08+00:00

Support for cinder backup force delete

2016-05-21T12:30:18+00:00

Cinder backup force delete is supported from cinder server
side but cinderclient support is not present.

This patchset adds support for cinder backup force delete
from cinderclient side.

Closes-Bug:#1567243

Partially-Implements: blueprint snapshot-backup-force-delete

Change-Id: I4ec38376d57ef6f74fefdd3bd2fea7a10bc51672

Fix upload_to_image method

2016-05-20T19:55:55+00:00

Commit Ie639179c5bbbaca4de62b42b368830afcfd8f7ac introduced 'visibility'
and 'protected' params. These params should be used only with
v3.1 microversion. Also these changes break current v2 users.

This patch fixes these issues.

Closes-Bug: #1584056
Change-Id: I0574631791c475bbefdb6e7d1647a20d0759df64

Remove deprecated tempest_lib and use tempest.lib

2016-05-20T13:13:07+00:00

Since 10.0.0 release tempest-ib is deprecated now.
Cinderclient should use tempest.lib in test code
and add tempest>=11.0.0 in requirements following
global-requirements.

Closes-Bug: #1583583
Change-Id: I9d766f46eb6fff29ae9c0267a60ff2ef4bf2343e

Merge "Updated from global requirements"

2016-05-18T23:18:32+00:00

Updated from global requirements

2016-05-18T20:27:13+00:00

Change-Id: I299ff1546179c71664b43e8e821b9e45b9a2fe73

Don't reset volume status when resetting migration status

2016-05-18T19:43:54+00:00

In case of failed volume migration, status of the volume is
still in-use and the migration status is set to error.

Current reset-migration-status command resets not only
migration status but also volume status. However the volume
status should not reset because the volume is still attached.

Closes-Bug #1552058
Change-Id: I9a8a5ed6a00bdcffecbf98862fe60aee373f5e9b

Merge "Support --os-key option"

2016-05-18T14:46:23+00:00