Replying more to the "thread" and stream of thought than a specific message.
1) Yes, it is confusing. Rikimaru's description is more or less what I believe. 2) Because it is confusing, I continue to use NovaClient commands instead of OpenstackClient I don't know what drove the creation of the OpenStack Client server commands the way that they are it might be a good deep dive of launchpad and git to find out. i.e., I can't "guess" what drove the design as it seems wrong and overly opaque and complex. On Fri, Feb 17, 2017 at 3:38 AM, Rikimaru Honjo < honjo.rikim...@po.ntts.co.jp> wrote: > Hi Marcus, > > > On 2017/02/17 15:05, Marcus Furlong 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. >> >> >>> 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. >> > In my understanding, that report says about libvirt driver's behavior. > In the other hand, my report says about the logic of openstack client. > > Current "openstack server migrate" command has following logic: > > * openstack server migrate > +-User don't specify "--live" > | + Call cold-migrate API. > | Ignore "--block-migration" and "--shard-migration" option if user > specify those. > | > +-User specify "--live" > | + Call live-migration API. > | > +-User specify "--live --block-migration" > | + Call block-live-migration API. > | > +-User specify "--live --shared-migration" > + Call live-migration API.[1] > > [1] > "--shared-migration" means live-migration(not block-live-migrate) in > "server migrate" command. > In other words, "server migrate --live" and "server migrate --live > --shared-migration" > are same operation. > I'm wondering why "--shared-migration" is existed... > > > Cheers, >> Marcus. >> >> > -- > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > NTTソフトウェア株式会社 > クラウド&セキュリティ事業部 第一事業ユニット(CS1BU) > 本上力丸 > TEL. :045-212-7539 > E-mail:honjo.rikim...@po.ntts.co.jp > 〒220-0012 > 横浜市西区みなとみらい4丁目4番5号 > 横浜アイマークプレイス 13階 > > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators