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
..
api	Re-implement novaclient bits removed in 10.0	2018-03-13 09:10:45 -05:00
common	Merge "Fix limits show command without Nova and Cinder"	2018-04-23 09:49:35 +00:00
compute	Merge "Add --image-property parameter in 'server create'"	2018-03-31 17:20:27 +00:00
identity	Clean up W503 and E402 pep8 errors	2018-04-15 12:23:06 +09:00
image	Clean up W503 and E402 pep8 errors	2018-04-15 12:23:06 +09:00
locale/tr_TR/LC_MESSAGES	Imported Translations from Zanata	2018-03-01 07:25:50 +00:00
network	Merge "Network: Add tag support for floating ip"	2018-04-23 08:12:25 +00:00
object	Allow objects to be streamed to stdout	2017-07-05 20:08:18 -03:00
tests	Remove invalid 'unlock-volume' migration arg	2018-10-26 12:02:58 -05:00
volume	Remove invalid 'unlock-volume' migration arg	2018-10-26 12:02:58 -05:00
__init__.py	Clean up W503 and E402 pep8 errors	2018-04-15 12:23:06 +09:00
i18n.py	Remove log translations	2017-03-21 17:23:09 +08:00
shell.py	Useless line of code in shell.py	2017-09-08 06:28:15 +00:00