[pve-devel] RFC: vm cloning implementation proposal

[Alexandre DERUMIER]

>>So IMHO, 'copy' and 'clone' are different features?

For me copy = full clone

but maybe full clone = copy of the same storage type ?

each hypersivor/solution have differents terms for them...





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

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mercredi 3 Octobre 2012 18:20:21 
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal 

> yes. 
> one note : for nfs,directory,filename/path can't be change after cloning, as 
> new qcow2 file have parent path/file hardcoded inside it. 

Yes, that is why volume templates will use a special path/name (They also has no owner VM). 
We will also make the file permissions read-only. 

> >>> 2.) clone template: make a writable copy of above templates 
> >> 
> >>nexenta, rdb and sheepdog: use storage clone feature 
> >> 
> >>nfs, directory: we have to options here 
> >> 
> >> - create linked clone: qcow2 with base image 
> >> - create full clone: copy template images 
> 
> Maybe (crazy) users want full clone from nexenta,rbd,sheepdog ? 
> (exports/import ?) 

I guess there is another action/feature called 'Copy VM'. This can be implemented 
with simple import/export commands. In theory, you can copy the VM 
to different storage. 

So IMHO, 'copy' and 'clone' are different features? 

> >>> 1.) create template: create a read-only snapshot of all used VM disks 
> >> 
> >>We can also have several different methods to create templates: 
> >> 
> >>a.) Create a template from any existing VM 
> >>b.) Create a template from a VM backup file (file import possible) 
> seem great 
> 
> >>other ideas? 
> 
> import a template from ovf or other public format ? (I never search about it, 
> but maybe this can be usefull) 

Ah, yes. We just need someone to implement that ;-)