[pve-devel] template considerations

[Alexandre DERUMIER]

>>Seems that both sheedpdog and RBD LS returns information about parent (base). 
>>
>>For Nexenta we already call get_zvol_props(), so we also have that info. 
>>
>>For LVM we can use --options '...,origin' to list the base image. 
>>
>>So we just need to implement a cache for directory based storage types. 
>>
>>@Alexandre: is my assumption correct? 

Yes.

Don't known for lvm, but for other storage (rbd,sheepdog,nexenta) it's already implemented in pve-storage (see sheepdog_ls, rbd_ls,...)


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

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Michael Rasmussen" <mir at datanom.net>, "Alexandre DERUMIER (aderumier at odiso.com)" <aderumier at odiso.com>, pve-devel at pve.proxmox.com 
Envoyé: Lundi 28 Janvier 2013 07:26:05 
Objet: RE: [pve-devel] template considerations 

> > > One problem I see is that we do not want to call 'qemu-img info' for 
> > > a normal content list, so that list would not include that information. 
> > > 
> > Could the information not be stored some how at creation time? The 
> > image is read-only and as such cannot change after creation in which 
> > case the info stored at creation time will always be same through out the 
> image life time. 
> 
> Sure, we could cache the information returned by qemu-img. But it is 
> necessarily needed, so it is unclear to add additional complexity for the 
> cache. 

Seems that both sheedpdog and RBD LS returns information about parent (base). 

For Nexenta we already call get_zvol_props(), so we also have that info. 

For LVM we can use --options '...,origin' to list the base image. 

So we just need to implement a cache for directory based storage types. 

@Alexandre: is my assumption correct?