Sean McGinnis f00ffebea6 Remove invalid 'unlock-volume' migration arg ... 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		2018-10-26 12:02:58 -05:00
..
v1	Update help text for encryption provider	2018-02-23 16:26:39 -05:00
v2	Remove invalid 'unlock-volume' migration arg	2018-10-26 12:02:58 -05:00
v3	Add Cinder v3 client support for volumes	2017-02-20 20:37:36 +00:00
__init__.py	Remove copyright from empty files	2014-01-20 17:28:13 +04:00
client.py	Add Cinder v3 client support for volumes	2017-02-20 20:37:36 +00:00