I think we are running away from the original question here,
'live-migration' and 'evacuate' aim to handle different scenarios. When you
use 'live migration', you have a plan that when your compute node will
shutdown. IMHO, The only way to provide VM high availability automatically
by using 'evacua
So we have to use the block-migrate flag in the live-migrate command set.
Also which is the minimum libvirt version that support this. We use
lbvirt-0.10.2-29
Thanks for the pointer to the patch. I will check that out.
Sangeeta
On 2/21/14, 9:38 AM, "Joe Gordon" wrote:
>On Thu, Feb 20, 2014 at
ng List (not for usage questions)"
Subject: Re: [openstack-dev] [Nova][glance] Question about evacuate with
no shared storage..
>On Thu, Feb 20, 2014 at 9:01 PM, Sangeeta Singh
>wrote:
>> Hi,
>>
>> At my organization we do not use a shared storage for VM disks bu
On Thu, Feb 20, 2014 at 9:01 PM, Sangeeta Singh wrote:
> Hi,
>
> At my organization we do not use a shared storage for VM disks but need to
> evacuate VMs from a HV that is down or having problems to another HV. The
> evacuate command only allows the evacuated VM to have the base image. What I
>
ists.openstack.org>>
Subject: Re: [openstack-dev] [Nova][glance] Question about evacuate with no
shared storage..
This looks like a useful feature, need some work to do that. evacuate function
based on rebuild, if we want to use snapshot images, we need pass the the
snapshot reference fr
This looks like a useful feature, need some work to do that. evacuate
function based on rebuild, if we want to use snapshot images, we need pass
the the snapshot reference from API layer ,and expose the interface from
python-novaclient. Correct me if I am wrong :)
2014-02-21 13:01 GMT+08:00 San
Hi,
At my organization we do not use a shared storage for VM disks but need to
evacuate VMs from a HV that is down or having problems to another HV. The
evacuate command only allows the evacuated VM to have the base image. What I am
interested in is to create a snapshot of the VM on the down
