Hi, >From the first sight there are no restrictions for instance_path option. Could you please provide some details about the use case? I wonder would this functionality be really useful for cloud-operators, or we just should add description to instance path option, forcing to use the same path on compute nodes?
Timofey On Fri, Apr 29, 2016 at 4:47 AM, Eli Qiao <liyong.q...@intel.com> wrote: > hi team, > > Is there any require that all compute node's instance_dir should be same? > > I recently get an issue while doing live migration with migrateToURI3 > method of libvirt python interface, if > source and dest host are configured with difference instance_dir, > migration will fail since migrateToURI3 > requires a new xml, but we don't modified the instance_dir of dest xml. > > I reported a bug on [1]_ , would like to get confirmation before spend > effort working on it. > > [1] https://bugs.launchpad.net/nova/+bug/1576245 > > Thanks. > > -- > > Best Regards, Eli Qiao (乔立勇) > Intel OTC China > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
