<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">rescue does not bring back nodes from dead hosts. It reboots the instance with a fresh copy of the image it booted with as the base drive and attaches the current drive as a second drive so you can mount it and fix things. Unrescue switches back to the original drive after you have made your repairs.<div><br></div><div>Vish</div><div><br><div><div>On Sep 19, 2012, at 7:13 PM, Sam Stoelinga <<a href="mailto:sammiestoel@gmail.com">sammiestoel@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Ale,<div><br></div><div>It's the first time I see nova rescue, maybe this should be somewhere else in the documentation. Maybe the part related to migration, that's where I looked and tried.</div><div><br></div>
<div>I first tried to do migration of the VM on a dead host, but that didn't work then after searching I stumbled upon this patch to enable the functionality to move VMs from a dead host:</div><div><a href="https://review.openstack.org/#/c/11086/12">https://review.openstack.org/#/c/11086/12</a></div>
<div>But it wasn't available for Essex, and won't be in Folsom either. So I thought this functionality was not there yet either. Searched for ours documentation and google, but never saw anything about rescue.</div>
<div>Is the functionality the same as the above patch? I looked at the code, and the code seems much smaller. The above patch seems to do more cleaning up also.</div><div><br></div><div>Because I didn't know about nova rescue I already copied the patch to Essex successfully, but maybe it's safe to use nova rescue.</div>
<div>This is the evacuate patch for stable essex: <a href="https://review.openstack.org/#/c/13282/">https://review.openstack.org/#/c/13282/</a></div><div><br></div><div>Do I understand right that this is the workflow: </div>
<div>nova rescue instance1</div><div>Look if the state changed to RESCUED</div><div>if it's rescued do a nova unrescue instance1</div><div>which cleans up the resources used for rescuing and changes the state back to ACTIVE on the vm?</div>
<div><br></div><div>Thanks a lot, sure is helpful.</div><div><br></div><div>Sam</div><div><br><div class="gmail_quote">On Wed, Sep 19, 2012 at 9:12 PM, Alejandro Comisario <span dir="ltr"><<a href="mailto:alejandro.comisario@mercadolibre.com" target="_blank">alejandro.comisario@mercadolibre.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font><font><font face="courier new,monospace">if you are on essex, you can issue a "nova rescue", if in cactus, you have to manipulate the "instances" table to tell where the new instance will be running, and then from the new compute node issue a :</font></font></font><div>
<font><font><font face="courier new,monospace"><br></font></font></font></div><div><font><font><font face="courier new,monospace">virsh define /path/to/XML</font></font></font></div><div><font><font><font face="courier new,monospace">virsh start instance_name</font></font></font></div>
<div><font><font><font face="courier new,monospace"><br></font></font></font></div><div><font><font><font face="courier new,monospace">From that moment, you can manage the instance using euca / nova<br clear="all">
</font></font></font><div><b><br></b></div><div><b>Ale</b></div><div><div class="h5"><br><div class="gmail_quote">On Wed, Sep 19, 2012 at 4:03 AM, Wolfgang Hennerbichler <span dir="ltr"><<a href="mailto:wolfgang.hennerbichler@risc-software.at" target="_blank">wolfgang.hennerbichler@risc-software.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Folks,<br>
<br>
Although it seems a pretty straightforward scenario I have a hard time finding documentation on this.<br>
One of my compute nodes broke down. All the instances are on shared storage, so no troubles here, but I don't know how to tell openstack that the VM should be deployed on another compute node. I tried fiddling around in the mysql-db with no success.<br>
Any help is really appreciated.<br>
<br>
Wolfgang<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></body></html>