delta/openstack/python-openstackclient.git/openstackclient/volume, branch stein-em

Merge "Add --attached / --detached parameter to volume set"

2019-03-06T00:58:17+00:00

Add --attached / --detached parameter to volume set

2019-02-28T15:48:34+00:00

As to reflect cinder reset-state --attach-status functionality,
this patch adds --attached / --detached parameter to OSC's volume set
command.

Change-Id: Ic8ee928c9ab0e579512cfb7608f63bfcc2993c7b
Closes-Bug: #1745699

Fix: Restore output 'VolumeBackupsRestore' object is not iterable

2019-02-27T22:28:09+00:00

VolumeBackupsRetore object has '_info' attribute
which contains the output data of the restore
command which should be returned instead of the
'VolumeBackupsRestore' object.

Change-Id: I64b75649c1ac9c24e05a197f7280975564b4d386
Story: 2004740
Task: 28811

Add volume backup import/export commands

2018-11-10T08:11:04+00:00

This adds commands to import and export volume backup records so they
can be imported and restored on other Cinder instances or to the
original instance if the service or database has been lost and had to be
rebuilt.

I know this is a commonly used process by some users, so it would be
good to have this functionality in osc so they do not have to switch
clients.

More details about the export and import process can be found here:

https://docs.openstack.org/cinder/latest/admin/blockstorage-volume-backups-export-import.html

Change-Id: Ic95f87b36a416a2b50cb2193fd5759ab59336975
Signed-off-by: Sean McGinnis

Merge "Remove invalid 'unlock-volume' migration arg"

2018-11-08T19:11:06+00:00

Remove invalid 'unlock-volume' migration arg

2018-10-26T17:02:58+00:00

There is an optional flag that can be passed in to a
volume migration to tell Cinder to 'lock' a volume so
no other process can abort the migration. This is
reflected correctly with the --lock-volume argument
flag to `openstack volume migrate`, but there is
another --unlock-volume flag that is shown in the help
text for this command that does not do anything and is
not used anywhere.

Since there is no action to "unlock" a volume, this
just causes confusion - including for Cinder developers
that know this API. To avoid confusion, this invalid
flag should just be removed from the command.

Change-Id: I5f111ed58803a1bf5d34e828341d735099247108

Merge "Handle not having cinderclient.v1 available"

2018-10-15T22:07:43+00:00

Handle not having cinderclient.v1 available

2018-10-12T19:19:51+00:00

The Cinder v1 API was deprecated several years ago and may be removed
from python-cinderclient in the near future. To handle the case where v1
is no longer present, this updates cinderclient initialization to work
without it and give an appropriate error if v1 is requested with a
version where it is no longer available.

Change-Id: I277d7b48b8ad4cce383ec3722f8117938378f615
Signed-off-by: Sean McGinnis

Add volume backend pool list command

2018-10-09T20:56:58+00:00

Adds an equivalent for "cinder get-pools" with "volume backend pool list"
and "cinder get-pools --detail" with "volume backend pool list --long".

Story: 1655624
Task: 136949

Signed-off-by: Sean McGinnis 
Change-Id: I826c9946ffe11340d44ad57914f72fc2a72b6938

Add volume backend capability show command

2018-10-09T20:31:35+00:00

Adds and equivalend for "cinder get-capabilities" command to show the
capabilities supported by a Cinder backend.

Story: 1655624
Task: 26947

Change-Id: I38686a26cd503e45ce0102705a6632994ef10274
Signed-off-by: Sean McGinnis