[pve-devel] storage migration: extend "qm migrate"?

Alexandre DERUMIER aderumier at odiso.com
Thu Jan 17 12:47:32 CET 2013


>>I see your point. This particular situation is not handle in my code 
>>since it will only migrate between common attached storage backends. The 
>>case of migrating to an unattached storage is in my opinion a completely 
>>different usecase. 

Yes, I known. 
But It's not too much different, we can reuse code, just using nbd as target instead a volume file/device.

My proposal was to reuse "qm migrate",to avoid having 2 apis for migrate storage(1 for target storage on localhost, 1 for target storage on remote host)

if hosttarget = sourcetarget, then we simply migrate the disks
if hosttarget != sourcetarget, we mirror the disks with nbd (only if the storage is non-shared on both hosts), then we migrate the vm.

Maybe Dietmar have you an opinion about this ?


----- Mail original ----- 

De: "Michael Rasmussen" <mir at datanom.net> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Jeudi 17 Janvier 2013 12:38:07 
Objet: Re: [pve-devel] storage migration: extend "qm migrate"? 

On 01-17-2013 12:00, Alexandre DERUMIER wrote: 
> 
> How do think it can work, if the the storage is attached on target 
> host, but not on source host, 
> and that vm is running on source host ? 
> 
I see your point. This particular situation is not handle in my code 
since it will only migrate between common attached storage backends. The 
case of migrating to an unattached storage is in my opinion a completely 
different usecase. 

-- 
Hilsen/regards 
Michael Rasmussen 



More information about the pve-devel mailing list