[pve-devel] vm migration + storage migration with ndb workflow notes

Alexandre DERUMIER aderumier at odiso.com
Sun Jan 20 11:01:50 CET 2013


>>There is no need to change the storage name - we just migrate 
>>from 'local:disk1' to 'local:disk1' (storage/image is not changed, but be 
>>copy data because storage is not shared). 

Ok, It'll be indeed easier to manage, no need to upgrade the vm config file or to pass new arguments.


So,i'm not sure, maybe it doesn't make sense to extend "qm migrate" ?

maybe simply a new "qm storagemigrate" to only move between storages on a single node is enough ?




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

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Samedi 19 Janvier 2013 17:18:22 
Objet: RE: [pve-devel] vm migration + storage migration with ndb workflow notes 

> >>We only want to be able to migrate local disks (changing storage is not 
> really needed?). 
> >>I guess that would make 'remote' migrate much easier? 
> I think the main feature is indeed live migrate from a local non shared 
> storage to a another remote local non shared storage. 

Yes 

> I see another usage (for my own need), migrate between 2 remote 
> datacenters (1proxmox cluster across both), with a local san on each 
> datacenter. 
> Each datacenter can use differents storage, with differents protocol (nfs -> 
> iscsi for exemple). 
> 
> 
> What do you mean by ("changing storage is not really needed?"). Do you 
> mean changing storage format ? (local raw -> remote local lvm by example) 
> Because,For online remote storage migration, with ndb, it's easy to mirror 
> from any source storage to any remote storage. 

There is no need to change the storage name - we just migrate 
from 'local:disk1' to 'local:disk1' (storage/image is not changed, but be 
copy data because storage is not shared). 



More information about the pve-devel mailing list