On Thu, Oct 10, 2013 at 4:47 AM, Vladik Romanovsky < vladik.romanov...@enovance.com> wrote:
> Hello everyone, > > I have been recently working on a migration bug in nova (Bug #1233184). > > I noticed that compute service remains available, even if a connection to > libvirt is broken. > I thought that it might be better to disable the service (using > conductor.manager.update_service()) and resume it once it's connected again. > (maybe keep the host_stats periodic task running or create a dedicated > one, once it succeed, the service will become available again). > This way new vms wont be scheduled nor migrated to the disconnected host. > > Any thoughts on that? > Sounds reasonable to me. If we can't reach libvirt there isn't much that nova-compute can / should do. > Is anyone already working on that? > > Thank you, > Vladik > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
