[openstack-dev] [nova][Libvirt] Disabling nova-compute when a connection to libvirt is broken.

Lingxian Kong anlin.kong at gmail.com
Sat Oct 12 09:42:15 UTC 2013


+1 for me. And I am willing to be a volunteer.


2013/10/12 Joe Gordon <joe.gordon0 at gmail.com>

> On Thu, Oct 10, 2013 at 4:47 AM, Vladik Romanovsky <
> vladik.romanovsky at 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 at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
*--------------------------------------------*
*Lingxian Kong*
Huawei Technologies Co.,LTD.
IT Product Line CloudOS PDU
China, Xi'an
Mobile: +86-18602962792
Email: konglingxian at huawei.com; anlin.kong at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131012/d6bd54e8/attachment.html>


More information about the OpenStack-dev mailing list