[one-users] Fail-over from dead HV node

[SZÉKELYI Szabolcs]

On 2010. November 11. 15:25:33 Tino Vazquez wrote:
> We are working on an extension of the hooks mechanism, so when a host
> gets into the ERROR state a script can be triggered with information
> about the (allegedly) running VMs in that host, so it can resume them
> elsewhere.

How do you plan to distinguish VMs that crashed due to host hardware failure 
from the ones those were shut down by their administrator from inside the WM?

Thanks,
-- 
cc

> --
> Constantino Vázquez Blanco | dsa-research.org/tinova
> Virtualization Technology Engineer / Researcher
> OpenNebula Toolkit | opennebula.org
> 
> On Fri, Oct 29, 2010 at 12:03 PM, Oscar Elfving <sofam84 at gmail.com> wrote:
> > Hi,
> > When a hypervisor node dies (or becomes inaccessible), how are you
> > supposed to handle the machines that were running on it? ONE of course
> > still lists the machines as running since it can't check the machine
> > state. How are you guys handling it? In my case I have some single
> > purpose webservers running on the nodes and if a hypervisor node dies, I
> > would like to have some monitoring software start them up on one of the
> > remaining nodes. Best regards,
> > Oscar Elfving
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> 
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org