Not going to argue with that, it's rather pointless, but:
http://www.ovirt.org/OVirt_3.5_Release_Notes#Import_Storage_Domain

Now this feature only needs to make it into RHEV.

My suggestion is as safe as it gets, in fact I migrated a large setup from 2.2 to 3.4 this summer with no problems

On Thu, Nov 20, 2014 at 3:42 PM, John Gardeniers <jgardeniers@objectmastery.com> wrote:
Thanks Dan,

If that's the case it would be an extremely time-consuming and painful process, even to the point where it may not even be viable. :-(

It's increasingly looking to me like a deliberate decision has been taken to make it as difficult as possible to migrate VMs away from Ovirt/RHEV. It's the only virtualisation system I've encountered that doesn't have a real export system (export domains don't cut it).

regards,
John



On 21/11/14 07:27, Dan Yasny wrote:
Not an official answer here, but I'd assume the procedure would be to redeploy the engine and hosts, and use export domains

On Thu, Nov 20, 2014 at 3:21 PM, John Gardeniers <jgardeniers@objectmastery.com> wrote:
Bump.

On 17/11/14 15:41, John Gardeniers wrote:
What is the procedure to use when migrating Ovirt to or from RHEV? I'm assuming of course that there's little difference for the two directions. Is it just a matter of detaching the storage domain(s), dumping the engine database and attaching/importing them into the other system?

regards,
John

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________