012 16:41:54
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> I don't know how it's works on the storage side (maybe they do implicit clone
> or snapshots, when converting from/to template)
They simply make full copies?
_
> I don't know how it's works on the storage side (maybe they do implicit clone
> or snapshots, when converting from/to template)
They simply make full copies?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/l
> they have 2 ways to create template:
>
> 1) transform vm as template. (just rename the vm as template, so original vm
> is no more displayed as vm)
>
> 2) copy the vm to template. (original vm is available)
>
> seem more easy, they are no vm with clones, so we can delete them without
> any pro
;
À: "Dietmar Maurer"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 13:05:02
Objet: Re: [pve-devel] RFC: vm cloning implementation proposal
>>I want to delete the original, not the snapshot.
I don't see how it's possible,the snapshot by itself, it's
obre 2012 13:05:02
Objet: Re: [pve-devel] RFC: vm cloning implementation proposal
>>I want to delete the original, not the snapshot.
I don't see how it's possible,the snapshot by itself, it's just a referecence
in a point of time.
if you have a simple schema like this
1
ame key)
- Mail original -----
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 11:47:25
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> >>why not (we have a snaphot)? - those dr
> >>why not (we have a snaphot)? - those drivers do not allow that?
>
> Not sure for sheepdog, but rbd,nexenta you can't delete a snapshot if clone
> exist on the snasphot.
I want to delete the original, not the snapshot.
>(or storage should have some method to copy
> baseimage datas in each clo
SIZE
9 snap1 104857600
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 11:10:19
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> >>When you create a
> >>When you create a template, you only need to create a volume snapshot.
> >>
> >>Is that more clear now?
>
> Yes,ok. So snapshot tabs on vm only display live-snapshots, and not all
> volume snapshots.
yes.
> For implementation, that give us something like this (oversimplified): ?
>
>
> cre
originalvm -> template ?(we can't delete the originalvm is a template is
made from it (sheepdog,rbd,nexenta)
what do you think ?
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2
> could you give an example for sheepdog,rbd? (as we need a snapshot of the
> disk) What happen to the original vm when you create the template ?
>
> Does it create a snapshot of the disks, and snapshot name(on the storage) is
> the template name ?
We need to define the terms we use:
a.) live-sn
napshot name(on the storage) is
the template name ?
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 09:51:02
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> o
> one more question:
>
> to create a template from a snapshot,
> do you want:
I dont want to create template from snapshots.
I want to create templates form stopped VM
sub create_template(vmid) ...
> 1) create a snapshot
> 2) create a template
>
> or do it in 1 step:
>
> 1)create template (w
pshot tree of the vm ?
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@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
> 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:
- i
"Alexandre DERUMIER"
Cc: pve-devel@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 par
> 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.
>>Ah, I see (But it is unrelated to our snapshot implementation inside
>>qemu-server).
>>
>>So cloning is a 2-step process in general:
>>1.) create template: create a read-only snapshot of all used VM disks
>>2.) clone template: make a writable copy of above templates
>>
Yes, I think this is
> 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)
other ideas?
___
Also, that 2-step approach makes implementation straight forward:
> 1.) create template: create a read-only snapshot of all used VM disks
nexenta, rdb and sheepdog: use storage snapshot feature
nfs, directory: we simply make a copy of the image
> 2.) clone template: make a writable copy of abo
> >>I do not understand why we need that? Please can you explain?
>
> with rbd,nexenta,sheepdog, it's mandatory to clone from a snapshot. (that's
> why the sourcevm don't need to be readonly after the clone, like qcow2)
Ah, I see (But it is unrelated to our snapshot implementation inside
qemu-se
ERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 3 Octobre 2012 13:24:12
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> >>You want to clone a specific snapshot?
> Yes. we need to clone from a snapshot for sheepdog,rbd,nexenta.
> So choosing the snap
> >>You want to clone a specific snapshot?
> Yes. we need to clone from a snapshot for sheepdog,rbd,nexenta.
> So choosing the snapshot we want is good.
I do not understand why we need that? Please can you explain?
> >>Live cloning include VM state?
> I don't think we need to clone the vmstate, B
irst start of the cloned vm
. ( we can't rollback on the clone without a first snap)
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 3 Octobre 2012 12:35:53
Objet: RE: [pve-devel] RFC: vm clonin
> like a linux image or windows image,
> you want to do security updates or install new packages on the image, then
> make a new snapshot, and clone from this new snapshot.
You want to clone a specific snapshot?
> Live cloning can be also good to duplicate a vm to do tests in parallel.
>
> So, I
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 3 Octobre 2012 10:51:57
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> >>But first, why do I want to clone a VM? Please can you elaborate on
> >>the usage scenario first?
>
t;
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 3 Octobre 2012 10:51:57
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal
> >>But first, why do I want to clone a VM? Please can you elaborate on
> >>the usage scenario first?
>
> Cloning vm is a current s
> >>But first, why do I want to clone a VM? Please can you elaborate on
> >>the usage scenario first?
>
> Cloning vm is a current scenario in enterprise, generally, you have a basevm
> you want to duplicate in 1 second.
> Other scenario can be vdi desktop, you can clone in live a vm if a user need
Clones" (copy) and "Linkend Clones" (true clone)
http://www.vmware.com/support/ws55/doc/ws_clone_overview.html#wp1028798
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
Envoyé: Mercredi 3 Octobre 2012 06:40:40
> Vm cloning is instant duplicate vm config and disk (qm clone sourcevmid
> targetvmid).
This is an over-simplification. For examply, user want to clone a VM, but to
different storage?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.pro
> 2 types Storage which support cloning:
>
> 1)-sheepdog,rbd (>=0.52),nexenta :
>- the clone is made from a snapshot
>- can be done when sourcevm is online
>- we can use source vm after cloning
>- we can't delete a snapshot if a clone is made from the snapshot
>- we can't delet
Hi,
Now that we have vm snapshots, I would like to work on vm cloning in the coming
weeks (for proxmox 2.3 as 2.2 will be release soon).
Vm cloning is instant duplicate vm config and disk (qm clone sourcevmid
targetvmid).
2 types Storage which support cloning:
1)-sheepdog,rbd (>=0.52),nexen
32 matches
Mail list logo
