On 17 February 2017 at 17:05, Marcus Furlong <furlo...@gmail.com> wrote: > On 17 February 2017 at 16:47, Rikimaru Honjo > <honjo.rikim...@po.ntts.co.jp> wrote: >> Hi all, >> >> I found and reported a unkind behavior of "openstack server migrate" command >> when I maintained my environment.[1] >> But, I'm wondering which solution is better. >> Do you have opinions about following my solutions by operating point of >> view? >> I will commit a patch according to your opinions if those are gotten. >> >> [1]https://bugs.launchpad.net/python-openstackclient/+bug/1662755 >> --- >> [Actual] >> If user run "openstack server migrate --block-migration <UUID>", >> openstack client call Cold migration API. >> "--block migration" option will be ignored if user don't specify "--live". >> >> But, IMO, this is unkindly. >> This cause unexpected operation for operator. > > +1 This has confused/annoyed me before.
And having said that, the nova client itself also has some confusing verbs which require explanation: http://www.danplanet.com/blog/2016/03/03/evacuate-in-nova-one-command-to-confuse-us-all/ >> >> P.S. >> "--shared-migration" option has same issue. > > For the shared migration case, there is also this bug: > > https://bugs.launchpad.net/nova/+bug/1459782 > > which, if fixed/implemented would negate the need for > --shared-migration? And would fix also "nova resize" on shared > storage. > > Cheers, > Marcus. -- Marcus Furlong _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
