Hello Folks,
Although it seems a pretty straightforward scenario I have a hard time finding
documentation on this.
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
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 :
virsh define /path/to/XML
virsh start instance_name
>From that moment, you can manage the ins
Hi Ale,
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.
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 pat
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 rep
On 20/09/12 13:50, Vishvananda Ishaya wrote:
**
On Wed, Sep 19, 2012 at 4:03 AM, Wolfgang Hennerbichler
mailto:wolfgang.hennerbich...@risc-software.at>> wrote:
Hello Folks,
Although it seems a pretty straightforward scenario I have a hard
time finding documentation on this.
One
Sorry for the top post.
FYI, in folsom we modified reboot to do a lot of the below for you, so you
might be able to get away with:
> Update the vm's compute host.
>
> UPDATE instances SET host = 'np-rcc46' WHERE uuid =
> '3f57699a-e773-4650-a443-b4b37eed5a06';
>
and then:
nova reboot --hard
Thanks, that's what I ended up doing (by intuition rather than knowledge)
yesterday. I didn't know about nova rescue either.
I think this is a Big Big room for improvement here. In the best case this
should be discovered automatically and the switchover should be done without
human Intervention
,
Cc: "openstack@lists.launchpad.net"
Date: 20/09/2012 09:19 AM
Subject: Re: [Openstack] Compute Node Down!
Sent by:openstack-bounces+glikson=il.ibm@lists.launchpad.net
Thanks, that's what I ended up doing (by intuition rather than knowledge)
yesterday
8 matches
Mail list logo
