As an operator dealing with platforms that do cold migration I would like to be able to abort and rollback the process.
That would give us a better service quality and availability. We do have no choices but to use cold migration on some of our remote sites as they don’t get a unified storage such as CEPH for cost management. Those remote sites have to growth and gain traction before being budgeted for a truly powerful distributed storage backend. Due to such limitations I would love to be able to reduce the time our customers are impacted by such move while doing maintenance or any other jobs requiring us to do a migration. Thanks for the hard work on this topic! Le mar. 1 mai 2018 à 03:03, Takashi Natsume <natsume.taka...@lab.ntt.co.jp> a écrit : > Hi everyone, > > I'm going to add the aborting cold migration function [1] in nova. > I would like to ask operators' feedback on this. > > The cold migration is an administrator operation by default. > If administrators perform cold migration and it is stalled out, > users cannot do their operations (e.g. starting the VM). > > In that case, if administrators can abort the cold migration by using > this function, > it enables users to operate their VMs. > > If you are a person like the following, would you reply to this mail? > > * Those who need this function > * Those who will use this function if it is implemented > * Those who think that it is better to have this function > * Those who are interested in this function > > [1] https://review.openstack.org/#/c/334732/ > > Regards, > Takashi Natsume > NTT Software Innovation Center > E-mail: natsume.taka...@lab.ntt.co.jp > > > _______________________________________________ > 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
