Hi Matt, > > We store the service logs which are created by VM on that storage. > > I don't mean to be glib, but have you considered maybe not doing that?
The load issue on storage is due to the way we deploy our business softwares on VM. The best way is introducing a new storage and separate the SAN, but we cannot change our deployment method due to it's cost and other limitations. On a long-term, our operation team will change the deployment method to better one to resolve this problem. On the other hand, we would like to build a tool to support VM migration that is unaware of which migration method is used for VM migration (Cold or Live). Feature parity wise, if live migration supports cancel feature, then we think that cold migration must support it as well. -------------------------------------------------- Yukinori Sagara <saga...@nttdata.co.jp> Platform Engineering Department, NTT DATA Corp. ________________________________________ 差出人: Matt Riedemann <mriede...@gmail.com> 送信日時: 2018年5月18日 1:39 宛先: openstack-operators@lists.openstack.org 件名: Re: [Openstack-operators] Need feedback for nova aborting cold migration function On 5/15/2018 3:48 AM, saga...@nttdata.co.jp wrote: > We store the service logs which are created by VM on that storage. I don't mean to be glib, but have you considered maybe not doing that? -- 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
