[pve-devel] template considerations

[Alexandre DERUMIER]

>>Maybe it is also convenient to allow to transform a single disk 
>>to a template on the GUI. The disks gets simple replaced by 
>>a clone in the VM config. 

I don't understand , can you provide an example ?


>>
>>
>>Another thing I am thinking about is how we can mark cloned 
>>disks. I would be convenient to use some other naming so that 
>>we can see if a volume is cloned or not. For example: 
>>
>>
>>normal volume: local:100/vm-100-disk1.raw 
>>base volume: local:base/test.raw 
>>cloned volume: local:base/test.raw/100/vm-100-disk1.raw 

I don't know, currently we can see if it's a clone with browsing volumes.
(qemu-img info for files, rbd/sheepdog/nexenta with listing commands).

Currently I check only if clones exist when deleting a template.
Do we need to known if volume are clones for other thing ?


With your proposal,how do you do if a base volume is also a clone of another volume ?



----- 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 09:29:56 
Objet: RE: template considerations 

> > >>2.) Transform an existing VM automatically. 
> > >> 
> > 
> > >>If the user wants to modify a template, he need to: 
> > >> 
> > >>1.) clone/copy the VM 
> > >>2.) start the VM, do any modification, then stop 
> > >>3.) create a new template from that 
> > 
> > I could be great to rollback a template to a vm, if no clone of the 
> > template exist. (You create a template, but forgot something by 
> > example) 
> 
> maybe - but you can do that manually with above steps above. 
> (yes, it is harder to do). 

Maybe it is also convenient to allow to transform a single disk 
to a template on the GUI. The disks gets simple replaced by 
a clone in the VM config. 

That way template creation is decomposed into simple steps. 

Another thing I am thinking about is how we can mark cloned 
disks. I would be convenient to use some other naming so that 
we can see if a volume is cloned or not. For example: 

normal volume: local:100/vm-100-disk1.raw 
base volume: local:base/test.raw 
cloned volume: local:base/test.raw/100/vm-100-disk1.raw 

What do you think?