[pve-devel] [PATCH] implement vdisk_clone and vdisk_create_base
Alexandre DERUMIER
aderumier at odiso.com
Thu Jan 31 11:37:24 CET 2013
>>Yes, sure, no problem. I'll look on differents storage what string we can use.
ok, __base__ is working on rbd,sheepdog,nexenta (and also netapp)
So, I think we can use this.
----- Mail original -----
De: "Alexandre DERUMIER" <aderumier at odiso.com>
À: "Dietmar Maurer" <dietmar at proxmox.com>
Cc: pve-devel at pve.proxmox.com
Envoyé: Jeudi 31 Janvier 2013 11:27:54
Objet: Re: [pve-devel] [PATCH] implement vdisk_clone and vdisk_create_base
>>I would simply use a reasonable default snapshot name. Using '@base' is good, but maybe
>>this can clash with user specified names (live snapshots)? So we are better off using an uncommon
>>name, something like '__base__' (if the backend allows that)?
Yes, sure, no problem. I'll look on differents storage what string we can use.
----- Mail original -----
De: "Dietmar Maurer" <dietmar at proxmox.com>
À: "Alexandre DERUMIER" <aderumier at odiso.com>
Cc: pve-devel at pve.proxmox.com
Envoyé: Jeudi 31 Janvier 2013 11:02:59
Objet: RE: [pve-devel] [PATCH] implement vdisk_clone and vdisk_create_base
> For rbd,sheepdog,nexenta :
> - We can assume that snapshot name to clone is always "@base" if the
> volume is a base volume.
> - Or specify the snapname in base volid. (But you don't want base-6000-disk-
> 9 at base/vm-7000-disk-9)
I would simply use a reasonable default snapshot name. Using '@base' is good, but maybe
this can clash with user specified names (live snapshots)? So we are better off using an uncommon
name, something like '__base__' (if the backend allows that)?
_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list