----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: dron(a)redhat.com
Cc: "Maurice James" <midnightsteel(a)msn.com>, "Ofer Blaut"
<oblaut(a)redhat.com>, users(a)ovirt.org, "Michal Skrivanek"
<mskrivan(a)redhat.com>, "Dan Kenigsberg" <danken(a)redhat.com>
Sent: Thursday, February 27, 2014 9:15:24 AM
Subject: Re: [Users] Disk Migration
----- Original Message -----
> From: "Dafna Ron" <dron(a)redhat.com>
> To: "Maurice James" <midnightsteel(a)msn.com>
> Cc: "Ofer Blaut" <oblaut(a)redhat.com>, users(a)ovirt.org
> Sent: Wednesday, February 26, 2014 7:34:11 PM
> Subject: Re: [Users] Disk Migration
>
> On 02/26/2014 05:24 PM, Maurice James wrote:
> > I have a specific interface set up for migrations. Why do disk
> > migrations not use the interface that I have set for migrations? Is
> > that by design? Shouldnt it use the interfaces that I have set aside
> > for migrations? VM migrations work as they should but not disk migrations
>
> I don't think that you can configure interface for disk migration.
> Disk migration is actually copy of information from the original disk to
> a new disk created on a new domain + delete of the original disk once
> that is done.
> it's not actually a migration and so I am not sure you can actually
> configure an interface for that.
> adding ofer - perhpas he has a solution or it's possible and I am not
> aware of it.
I guess that *not* using the migration network for storage operation is
the expected behavior, to make migration faster and safer.
This seems to be the only documentation for the migration network:
www.ovirt.org/Features/Migration_Network
And it seems that it works as intended.
Nir