openstack team mailing list archive

[Alejandro Comisario <alejandro.comisario@xxxxxxxxxxxxxxxx>]

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 instance using euca / nova
*
*
*Ale*

On Wed, Sep 19, 2012 at 4:03 AM, Wolfgang Hennerbichler <
wolfgang.hennerbichler@xxxxxxxxxxxxxxxx> wrote:

> 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 compute node. I tried fiddling around
> in the mysql-db with no success.
> Any help is really appreciated.
>
> Wolfgang
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>