[pve-devel] RFC V2 Storage Replica

[Alexandre DERUMIER]

>>Maybe it would be easier to define replication on the target VM only? For
>>example,
>>add something like:
>>
>>replication-source: ip=1.2.3.4,sourcevmid=123,storage=mystorage


mmmm, yes, indeed !  (and run the cron on target cluster)

ip=could be an ip of the cluster.
(But I think we need to connect first to this ip, and find where the vm is located (in case of vm is moving), and reconnect to the vm node.

Don't known how to manage this first ip connect ? (do we allow to define multiple ips if 1 host is down?)



not sure we need to define storage=.

the storage config can be done at the targetvm creation.
(we create the targetvm with same disks than source, maybe with different storeid, but we have already all infos in disk config).

also, if something change on source vm (disk resize, new disk), I think we need to check that,
to do a new full sync. (if we replication through incremental snapshots).



for the replication itself, if storage support it (zfs,rbd), we can manage that with snapshots.
if storage is not supporting it, maybe use proxmox backup  or qemu backup (which allow incremental backup, and network target through nbd)




----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 21 Avril 2017 06:21:47
Objet: Re: [pve-devel] RFC V2 Storage Replica

> maybe: 
> 
> setup the first replication with an api call to target storage 
> 
> - create remotecopy vmid hostnameoftargetnode storeidoftargetnode. 
> 
> in target vmid.conf, store something like : sourcevmid :xxx and maybe 
> sourceclusterid:xxx (could be define somewhere in /etc/pve/... with a list of 
> ip/hostname) 
> 
> in source vmid.conf, store something like : remoteclusterid: xxx (could be 
> define somewhere n /etc/pve/...with a list of ip/hostname) 
> 
> 
> then, when replication occur on source vm, we connect to any node of 
> remoteclusterid , find the targetvmid where sourcevmid && sourceclusterid is 
> defined , then do the replication to the node where targetvmid is located. 

Maybe it would be easier to define replication on the target VM only? For 
example, 
add something like: 

replication-source: ip=1.2.3.4,sourcevmid=123,storage=mystorage 

???