Hi,<br><br>So, if I restart my physical nodes, all virtual machines after this operation will be in 'unknown' state. I can then restart them manually and this works. But in my solution it would be good if this happen without user intervention (automatic VMs start after nodes restart).<br>
<br>Is there any good practice? Maybe one should monitor this situation and after restart physical nodes should be able to run VMs in automatic way (e.g. hooks invoked when host goes from 'err' to 'on' state)?<br>
<br>Best regards<br>Piotr Kandziora<br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 6:28 PM, Ruben S. Montero <span dir="ltr"><<a href="mailto:rubensm@dacya.ucm.es">rubensm@dacya.ucm.es</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<div><br></div><div>OpenNebula monitors VMs in unknown state. So, if the VMs are restarted, OpenNebula should be able to recover those VMs and move them from unknown to running. The requirement is to and the id's are preserved at the hypervisor level (e.g. autostart i think)</div>
<div><br></div><div>Cheers</div><div><br></div><div>Ruben<div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Fri, Feb 18, 2011 at 6:05 PM, Shi Jin <span dir="ltr"><<a href="mailto:jinzishuai@gmail.com" target="_blank">jinzishuai@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you for the discussion.<div><br></div><div>Yes, there is definitely a possible problem of out of sync between the host and OpenNebula.<div>For example, after the node power failure, the one status for the VMs would be unknown. If people then deleted the VM, restarting the VM upon power resumption would cause a problem.</div>
<div>But this seems to be a more operational problem: just don't delete the VMs on a power failure node.</div><div>There are many other ways to cause out of sync under existing OpenNebula setup and it is up to the administrator's operation to ensure everything is consistent.</div>
<div><br></div><div>Also, starting a power failure VM definitely has the potential problem of disk corruption. But this is the best we can do upon such a tragic situation. One should ask more on why on the earth did the power fail in the first place? The autostart setup would simply ease a little bit of the pain.</div>
<div><br></div><div>Shi<div><div></div><div><br><br><div class="gmail_quote">On Thu, Feb 17, 2011 at 8:42 PM, Manikanta Kattamuri <span dir="ltr"><<a href="mailto:mani.kattamuri@hexagrid.com" target="_blank">mani.kattamuri@hexagrid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Assume all this is set and the vm's automatically come up after the servers get online.<div>would it not create more problems then solve as you one is not in sync with all the vm states?. </div>
<div>If there are any monitoring tools configured based on one status, will report failure.</div>
<div>Starting of the vms through oned will not succeed or cause disk corruption?</div><div><br></div><div>Mani.<br><br><div class="gmail_quote"><div><div></div><div>On Fri, Feb 18, 2011 at 4:03 AM, Shi Jin <span dir="ltr"><<a href="mailto:jinzishuai@gmail.com" target="_blank">jinzishuai@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>Hi there,<div><br></div><div>Right now, all KVM (I think Xen too but I don't know it for sure) VMs are started as a transient libvirt domain using the "virsh create <xml>" command.</div>
<div>There is nothing wrong with it but recently I had a facility wide power failure and all VMs running on the node are gone upon the server shutdown. I had to manually start all the domains that were running at the point of failure after power is resumed. Then I thought that if I put the VMs as libvirt autostart domains, they will be automatically started upon boot, which would save me a lot of manual process. But to do that, I have to make the VMs persistent libvirt domains using the "virsh define" and "virsh start" commands in sequence instead of the single "virsh create".</div>
<div><br></div><div>Is this a good idea? Comments welcome.</div><div>Thanks.</div><div>Shi<br clear="all">
<br>-- <br>Shi Jin, Ph.D.<br><br>
</div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br>
</div>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>Shi Jin, Ph.D.<br><br>
</div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div>Dr. Ruben Santiago Montero<br>Associate Professor (Profesor Titular), Complutense University of Madrid<br><br>URL: <a href="http://dsa-research.org/doku.php?id=people:ruben" target="_blank">http://dsa-research.org/doku.php?id=people:ruben</a><br>
Weblog: <a href="http://blog.dsa-research.org/?author=7" target="_blank">http://blog.dsa-research.org/?author=7</a><br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br>