Hi Matt, > On 5/9/2018 9:33 PM, saga...@nttdata.co.jp wrote: > > Operation planning of cold migration is difficult because cold migration > > time will vary drastically as it also depends on the load on storage > > servers at that point of time. If cold migration task stalls for any > > unknown reasons, operators may decide to cancel it manually. > > What storage backend are you using? What are some reasons that it has > stalled in the past?
Our storage backend is EMC VNX, and we have not shared the instance-store storage among compute nodes. The storage is also accessed by external system. We store the service logs which are created by VM on that storage. Our system needs to backup those logs by transferring to other storage. Those logs sometimes becomes very large, and the load of storage also becomes high. In those situation, migrating the VM takes more time than expected in advance, so we would like to cancel some migration task on the way if maintenance time being close to the end. > On 5/9/2018 9:33 PM, saga...@nttdata.co.jp wrote: > > We always do the maintenance work on midnight during limited time-slot to > > minimize impact to our users. > > Also, why are you doing maintenance with cold migration? Why not do live > migration for your maintenance (which already supports the abort function). We would like to migrate stopped servers as it is. As the reason above, we think we can operate the system more flexible if we able to cancel cold-migration as live-migration can. -------------------------------------------------- Yukinori Sagara <saga...@nttdata.co.jp> Platform Engineering Department, NTT DATA Corp. ________________________________________ 差出人: Matt Riedemann <mriede...@gmail.com> 送信日時: 2018年5月10日 22:59 宛先: openstack-operators@lists.openstack.org 件名: Re: [Openstack-operators] Need feedback for nova aborting cold migration function On 5/9/2018 9:33 PM, saga...@nttdata.co.jp wrote: > We always do the maintenance work on midnight during limited time-slot to > minimize impact to our users. Also, why are you doing maintenance with cold migration? Why not do live migration for your maintenance (which already supports the abort function). -- Thanks, Matt _______________________________________________ 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
