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
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
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
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
On 20/09/12 13:50, Vishvananda Ishaya wrote:
**
On Wed, Sep 19, 2012 at 4:03 AM, Wolfgang Hennerbichler
wolfgang.hennerbich...@risc-software.at
mailto:wolfgang.hennerbich...@risc-software.at wrote:
Hello Folks,
Although it seems a pretty straightforward scenario I have a hard
time
5 matches
Mail list logo
