[ovirt-devel] Live export/import
Christopher Pereira
kripper at imatronix.cl
Sun Jun 21 16:10:50 UTC 2015
Hi Allon,
We are on the same track, since the additional steps I mentioned are
only for reducing downtime (big backing chain images should be copied
while VMs are still running and writing to a small active snapshot that
would be copied at the end).
I'm basically reattaching an existing storage domain (with VM and
OVF_STORE disks) on another ovirt installation, but doing a copy of the
storage domain, instead of detaching it from the source data center.
Benefit for oVirt : Live export/import
The problem is that something is missing, since the VMs are not
displayed when I attach and activate the cloned storage domain on the
destination data center.
Maybe the detach process does something that is required to show the VMs
later. Again, I'm not doing a detach, but cloning the storage domain
with active VMs.
I saw in the logs that oVirt is getting the OVF files from a tar file.
Start fetching OVF files from tar file
File 'info.json' is not an OVF file, will be ignored.
Finish to fetch OVF files from tar file. The number of OVF entities
are 0
_*Maybe this tar file is written by the detach process? What else could
be missing?*_
I reported and shared the logs here:
https://bugzilla.redhat.com/show_bug.cgi?id=1234137
On 21-06-2015 12:04, Allon Mureinik wrote:
> Another way, if you have a domain to spare, would be to detach the domain containing the VM and attaching it to another setup.
> Otherwise, you're limited to either an export domain (which requires copying twice, as you mentioned), or some manual procedure like you suggested.
>
> ----- Original Message -----
>> From: "Christopher Pereira" <kripper at imatronix.cl>
>> To: devel at ovirt.org
>> Sent: Saturday, June 20, 2015 2:48:20 AM
>> Subject: [ovirt-devel] Live export/import
>>
>> Hi,
>>
>> I would like to migrate a VM between two different ovirt installations with
>> minimum down time.
>>
>> Using a export domain is slow (requires copying twice) and requires to stop
>> the VM.
>>
>> It seems like the best option is to 1) create a snapshot, 2) transfer the
>> backing chain images and OVF files to the destination storage domain 3) stop
>> the VM, 4) transfer the active snapshot and 5) import the VM from the
>> destination storage domain.
>>
>> Can you please comment and suggest other alternatives?
>>
>> Thanks.
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20150621/f8c30c5f/attachment-0001.html>
More information about the Devel
mailing list