[pve-devel] savevm tests

Alexandre DERUMIER aderumier at odiso.com
Wed Aug 29 17:52:07 CEST 2012


>>Putting qcow2 (or better qcow3) on those devices would solve the problem? If that works, 
>>there is no more need to use nexenta snapshot support? 

I want to use iscsi with nexenta, so qcow2 is not an option. (and I'm not sure using qcow2 on block device is possible)
Also, zfs snapshot are really fast. (qcow2 have some performance penality).
I also need zfs snapshot for cloning. 


More generally, I think it's always better to use snapshot capability of the storage (rbd,sheepdog,nexenta, or other).

Openstack implement netapp and nexenta snapshots using their api.
Vmware use vaai api for snapshots if storage support it.



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

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mercredi 29 Août 2012 17:34:32 
Objet: RE: [pve-devel] savevm tests 

> >>* create_snapshot: (savevm?) 
> Yes, if storage support it (qcow2,rbd,sheepdog). 
> I would like to implement also snasphot for external storage like nexenta We 
> simply need to define a create_snapshot sub for each storage module 

I am quite unsure about that, So far, we have many storage types which simply 
do not have any native snapshot support, for example: 

* iscsi: that standard simply does not define snapshots in any way 
* lvm: snapshots are simply not usable on shared storage 
* /dev/xyz: block devices are not aware of snapshots 

Putting qcow2 (or better qcow3) on those devices would solve the problem? If that works, 
there is no more need to use nexenta snapshot support? 



-- 

-- 



	

Alexandre D e rumier 

Ingénieur Systèmes et Réseaux 


Fixe : 03 20 68 88 85 

Fax : 03 20 68 90 88 


45 Bvd du Général Leclerc 59100 Roubaix 
12 rue Marivaux 75002 Paris 



More information about the pve-devel mailing list