Re: [Engine-devel] Disk Cloning When Creating a VM via a Template
----- Original Message -----
Okay, I'll have a look at master and play around with things a
little
bit. Thanks for that insight, Ayal! So, when a VM is cloned from a
template, all disks associated with the template are cloned to go
with the new VM, correct? Could I do something similar with the
floating disks and just clone all of the associated disks from a VM?
I think there is some misunderstanding here.
A floating disk is a disk which is not associated with any VM, so what are all of the
associated disks? The only place where different disks have any relation to each other us
within the context of a VM.
Note that if you clone while engine thinks you're creating a qcow snapshot then
you'd need to handle merge (snapshot delete) differently as well
In the meantime, I'll read up a bit more on Floating Disks on
the
feature pages on the wiki. Thanks again!
-- Dustin
-----Original Message-----
From: Ayal Baron [mailto:abaron@redhat.com]
Sent: Sunday, April 29, 2012 6:25 AM
To: Livnat Peer
Cc: engine-devel(a)ovirt.org; Schoenbrun, Dustin
Subject: Re: [Engine-devel] Disk Cloning When Creating a VM via a
Template
----- Original Message -----
> On 26/04/12 22:24, Schoenbrun, Dustin wrote:
> > I know that floating disks are coming in the next version of
> > oVirt,
> > but in the interim I want to know internally what the procedure
> > is
> > when a disk is cloned when creating a VM from a template.
I'm not sure what floating disks have to do with it (it would be
relevant for cloning a single disk, not cloning an entire VM).
For cloning a single disk I believe that floating disk is already
available in master by the way.
> >
>
> Hi,
>
> Today when creating a VM from template the user can choose the
> provisioning method:
> - It can be 'Thin' in which the engine is taking a snapshot of the
> template disks (running AddVMCommand which executes
> CreateSnapshotFromTemplateCommand)
> - Or 'Clone' which results in cloning the template disks (executes
> AddVmFromTemplateCommand which in turn executes
> CreateCloneOfTemplateCommand)
For createCloneOfTemplateCommand, other than the VM configuration
being copied, the engine creates copies of all of the template
images (calls moveImage in vdsm per Image).
>
>
> Thanks, Livnat
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>