[pve-devel] template considerations

[Alexandre DERUMIER]

>>Note: extending the volume name parse should be really easy? 
Yes, sure no problem, we can go this way,it's just some regex to change ;)



One thing I'm not sure it's about to have a "semi" template, if a vm have 2 disks, and we convert only 1 disk to base image.

When we have converted the first disk to base image, we can't start anymore the vm.
But we can't clone the template because the second disk is not a base image.
So we need to delete or convert the second disk to base image, to be able to clone the template.

Isn't more easy to allow only full vm conversion (all disks) to template and don't allow  specific disk to base image conversion ?




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

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Dimanche 27 Janvier 2013 12:56:10 
Objet: RE: template considerations 

> No, it is not needed. I just thought it is good to know? 
> 
> > With your proposal,how do you do if a base volume is also a clone of 
> > another volume ? 
> 
> >>What problem do you see? 
> 
> Oh, you want only it in config file ? (not in directory structure, or volume 
> name) 

yes. 

> base volume clone of another base volume : 
> local:base/test.raw/base/test2.raw 
> local volume clone of a base volume : local:base/test.raw/100/vm-100- 
> disk1.raw 
> 
> I think it should be ok. But we can also simply use a hint,like for size, 
> parent=base/test.raw (files) or parent=base-test (sheepdog,rbd,..) 

IMHO that is more complex. And you can lose that information easily 
if you pass the volume name around. 

Note: extending the volume name parse should be really easy? 

For now, we just need to consider that our clone() method (can) return a new 
volume name. We can decide later if we use that feature.