Comment 3 for bug 1233184
Revision history for this message
| Vladik Romanovsky (vladik-romanovsky) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi everyone,
I have proposed a patch for this a while ago: https:/
However, it's still WIP.
I think the best way is that libvirt driver will respond with a meaningful error, when the connection is broken.
This way we will be able to catch in the conductor task.
Moreover, I think we should relay on libvirt events (on the source host), as its the only component that knows the status of the vm.
The more general solution, in my opinion would be to disable the nova compute service, when libvirt is not available and resume it when its available.
I have started a discussion on this topic on the mailing list. Maybe you would like to share your thoughts there as well (Subject : "Disabling nova-compute when a connection to libvirt is broken.")
What do you think?