[pve-devel] RFC: vm cloning implementation proposal
Alexandre DERUMIER
aderumier at odiso.com
Thu Oct 4 09:07:00 CEST 2012
>>We can define our own Terms ;-)
>>clone:
>>- uses storage cloning features.
>>- a clone is always on the same storage
>>copy:
>>- is simply a copy of all data
>>- you can copy data to any other storage
>>So those are slightly different things.
Yes, I agree with that.
That seem to be more clear in my mind.
one more question:
to create a template from a snapshot,
do you want:
1) create a snapshot
2) create a template
or do it in 1 step:
1)create template (with implicit snapshot).
And is this snapshot displayed in the snapshot tree of the vm ?
----- Mail original -----
De: "Dietmar Maurer" <dietmar at proxmox.com>
À: "Alexandre DERUMIER" <aderumier at odiso.com>
Cc: pve-devel at pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 05:56:13
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> For me copy = full clone
>
> but maybe full clone = copy of the same storage type ?
>
> each hypersivor/solution have differents terms for them...
We can define our own Terms ;-)
clone:
- uses storage cloning features.
- a clone is always on the same storage
copy:
- is simply a copy of all data
- you can copy data to any other storage
So those are slightly different things.
More information about the pve-devel
mailing list