Bug 790159

Summary: [ovirt] [RFE] support for storage domain migration (copy domain)
Product: [Retired] oVirt Reporter: Haim <hateya>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, amureini, bazulay, hateya, iheim, mgoldboi, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 813743 (view as bug list) Environment:
Last Closed: 2013-03-12 09:37:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 813743    

Description Haim 2012-02-13 19:51:09 UTC 
Description of problem:

I would like to propose the following RFE: Storage domain replication\migration

case: User wants to migrate his data from one storage domain to another, this will supress the procedure of export all vms\templates, and import back.
Comment 1 Itamar Heim 2012-02-14 03:36:35 UTC 
can't user just move the VMs/Disks between them?
(this should be easier when storage live migration will allow moving disks between hosts not in same DC for that use case)
Comment 2 Haim 2012-02-14 07:30:44 UTC 
(In reply to comment #1)
> can't user just move the VMs/Disks between them?
> (this should be easier when storage live migration will allow moving disks
> between hosts not in same DC for that use case)

my aim is quit simple: one click replication\migration of storage domain.
when you start move vms\templates one by one, putting aside the fact its a lot of work (maybe process can be automated using python-sdk, but its not that obvious), you expose the system to the various locking issues, where async tasks may collide one another, resulting new error flows we don't want to get in-to. 
the implementation of such RFE, shouldn't be hard, as you have all mechanism inside LVM (when speaking about block based devices) - we call it pvmove, where you move all data from one pv (in our case, "lun"), to another - we just need to wrap it up nicely, but again, its just a suggestion.
Comment 3 Itamar Heim 2013-03-12 09:37:47 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.