From Dustin.Schoenbrun at netapp.com Thu Apr 26 15:24:38 2012 Content-Type: multipart/mixed; boundary="===============8886090590022400735==" MIME-Version: 1.0 From: Schoenbrun, Dustin To: devel at ovirt.org Subject: [Engine-devel] Disk Cloning When Creating a VM via a Template Date: Thu, 26 Apr 2012 19:24:17 +0000 Message-ID: <0A1534657992624AACDCA570F1D3E20003C29F05@SACEXCMBX03-PRD.hq.netapp.com> --===============8886090590022400735== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable --_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_ Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, I know that floating disks are coming in the next version of oVirt, but in = =3D the interim I want to know internally what the procedure is when a disk is = =3D cloned when creating a VM from a template. I see the AddVmImages() method = =3D in the AddVmFromTemplateCommand.java file, but could someone walk me throug= =3D h exactly what is going on when the disk gets cloned? Thanks! -- Dustin --_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_ Content-Type: text/html; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

I know that floating disks are coming in the next = ve=3D rsion of oVirt, but in the interim I want to know internally what the proce= =3D dure is when a disk is cloned when creating a VM from a template. I s= =3D ee the AddVmImages() method in the AddVmFromTemplateCommand.java file, but could someone walk me through exactly what is going on when the = =3D disk gets cloned? Thanks!

-- Dustin

--_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_-- --===============8886090590022400735== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS1fMDAwXzBBMTUzNDY1Nzk5MjYyNEFBQ0RDQTU3MEYxRDNFMjAwMDNDMjlGMDVTQUNFWENNQlgw M1BSRGhfCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0idXMtYXNjaWkiCkNvbnRl bnQtVHJhbnNmZXItRW5jb2Rpbmc6IHF1b3RlZC1wcmludGFibGUKCkdyZWV0aW5ncywKCkkga25v dyB0aGF0IGZsb2F0aW5nIGRpc2tzIGFyZSBjb21pbmcgaW4gdGhlIG5leHQgdmVyc2lvbiBvZiBv VmlydCwgYnV0IGluID0KdGhlIGludGVyaW0gSSB3YW50IHRvIGtub3cgaW50ZXJuYWxseSB3aGF0 IHRoZSBwcm9jZWR1cmUgaXMgd2hlbiBhIGRpc2sgaXMgPQpjbG9uZWQgd2hlbiBjcmVhdGluZyBh IFZNIGZyb20gYSB0ZW1wbGF0ZS4gIEkgc2VlIHRoZSBBZGRWbUltYWdlcygpIG1ldGhvZCA9Cmlu IHRoZSBBZGRWbUZyb21UZW1wbGF0ZUNvbW1hbmQuamF2YSBmaWxlLCBidXQgY291bGQgc29tZW9u ZSB3YWxrIG1lIHRocm91Zz0KaCBleGFjdGx5IHdoYXQgaXMgZ29pbmcgb24gd2hlbiB0aGUgZGlz ayBnZXRzIGNsb25lZD8gIFRoYW5rcyEKCi0tIER1c3RpbgoKCi0tXzAwMF8wQTE1MzQ2NTc5OTI2 MjRBQUNEQ0E1NzBGMUQzRTIwMDAzQzI5RjA1U0FDRVhDTUJYMDNQUkRoXwpDb250ZW50LVR5cGU6 IHRleHQvaHRtbDsgY2hhcnNldD0idXMtYXNjaWkiCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6 IHF1b3RlZC1wcmludGFibGUKCjxodG1sIHhtbG5zOnY9M0QidXJuOnNjaGVtYXMtbWljcm9zb2Z0 LWNvbTp2bWwiIHhtbG5zOm89M0QidXJuOnNjaGVtYXMtbWljcj0Kb3NvZnQtY29tOm9mZmljZTpv ZmZpY2UiIHhtbG5zOnc9M0QidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIg PQp4bWxuczptPTNEImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vb2ZmaWNlLzIwMDQvMTIv b21tbCIgeG1sbnM9M0QiaHR0cDo9Ci8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4KPGhlYWQ+ CjxtZXRhIGh0dHAtZXF1aXY9M0QiQ29udGVudC1UeXBlIiBjb250ZW50PTNEInRleHQvaHRtbDsg Y2hhcnNldD0zRHVzLWFzY2lpIj0KPgo8bWV0YSBuYW1lPTNEIkdlbmVyYXRvciIgY29udGVudD0z RCJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+CjxzdHlsZT48IS0tCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8KQGZvbnQtZmFjZQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7CglwYW5v c2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9Ci8qIFN0eWxlIERlZmluaXRpb25zICovCnAuTXNv Tm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwKCXttYXJnaW46MGluOwoJbWFyZ2lu LWJvdHRvbTouMDAwMXB0OwoJZm9udC1zaXplOjExLjBwdDsKCWZvbnQtZmFtaWx5OiJDYWxpYnJp Iiwic2Fucy1zZXJpZiI7fQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5OwoJY29sb3I6Ymx1ZTsKCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQphOnZp c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQKCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7 Cgljb2xvcjpwdXJwbGU7Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30Kc3Bhbi5FbWFpbFN0 eWxlMTcKCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOwoJZm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjsKCWNvbG9yOndpbmRvd3RleHQ7fQouTXNvQ2hwRGVmYXVsdAoJ e21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5OwoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjt9CkBwYWdlIFdvcmRTZWN0aW9uMQoJe3NpemU6OC41aW4gMTEuMGluOwoJbWFyZ2lu OjEuMGluIDEuMGluIDEuMGluIDEuMGluO30KZGl2LldvcmRTZWN0aW9uMQoJe3BhZ2U6V29yZFNl Y3Rpb24xO30KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4KPG86c2hhcGVkZWZh dWx0cyB2OmV4dD0zRCJlZGl0IiBzcGlkbWF4PTNEIjEwMjYiIC8+CjwveG1sPjwhW2VuZGlmXS0t PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPgo8bzpzaGFwZWxheW91dCB2OmV4dD0zRCJlZGl0Ij4K PG86aWRtYXAgdjpleHQ9M0QiZWRpdCIgZGF0YT0zRCIxIiAvPgo8L286c2hhcGVsYXlvdXQ+PC94 bWw+PCFbZW5kaWZdLS0+CjwvaGVhZD4KPGJvZHkgbGFuZz0zRCJFTi1VUyIgbGluaz0zRCJibHVl IiB2bGluaz0zRCJwdXJwbGUiPgo8ZGl2IGNsYXNzPTNEIldvcmRTZWN0aW9uMSI+CjxwIGNsYXNz PTNEIk1zb05vcm1hbCI+R3JlZXRpbmdzLDxvOnA+PC9vOnA+PC9wPgo8cCBjbGFzcz0zRCJNc29O b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPgo8cCBjbGFzcz0zRCJNc29Ob3JtYWwiPkkga25v dyB0aGF0IGZsb2F0aW5nIGRpc2tzIGFyZSBjb21pbmcgaW4gdGhlIG5leHQgdmU9CnJzaW9uIG9m IG9WaXJ0LCBidXQgaW4gdGhlIGludGVyaW0gSSB3YW50IHRvIGtub3cgaW50ZXJuYWxseSB3aGF0 IHRoZSBwcm9jZT0KZHVyZSBpcyB3aGVuIGEgZGlzayBpcyBjbG9uZWQgd2hlbiBjcmVhdGluZyBh IFZNIGZyb20gYSB0ZW1wbGF0ZS4mbmJzcDsgSSBzPQplZSB0aGUgQWRkVm1JbWFnZXMoKSBtZXRo b2QgaW4gdGhlIEFkZFZtRnJvbVRlbXBsYXRlQ29tbWFuZC5qYXZhCiBmaWxlLCBidXQgY291bGQg c29tZW9uZSB3YWxrIG1lIHRocm91Z2ggZXhhY3RseSB3aGF0IGlzIGdvaW5nIG9uIHdoZW4gdGhl ID0KZGlzayBnZXRzIGNsb25lZD8mbmJzcDsgVGhhbmtzITxvOnA+PC9vOnA+PC9wPgo8cCBjbGFz cz0zRCJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPgo8cCBjbGFzcz0zRCJNc29Ob3Jt YWwiPi0tIER1c3RpbjxvOnA+PC9vOnA+PC9wPgo8cCBjbGFzcz0zRCJNc29Ob3JtYWwiPjxvOnA+ Jm5ic3A7PC9vOnA+PC9wPgo8L2Rpdj4KPC9ib2R5Pgo8L2h0bWw+CgotLV8wMDBfMEExNTM0NjU3 OTkyNjI0QUFDRENBNTcwRjFEM0UyMDAwM0MyOUYwNVNBQ0VYQ01CWDAzUFJEaF8tLQo= --===============8886090590022400735==-- From lpeer at redhat.com Sun Apr 29 05:41:31 2012 Content-Type: multipart/mixed; boundary="===============3534679496694244946==" MIME-Version: 1.0 From: Livnat Peer To: devel at ovirt.org Subject: Re: [Engine-devel] Disk Cloning When Creating a VM via a Template Date: Sun, 29 Apr 2012 12:40:50 +0300 Message-ID: <4F9D0CA2.6070006@redhat.com> In-Reply-To: 0A1534657992624AACDCA570F1D3E20003C29F05@SACEXCMBX03-PRD.hq.netapp.com --===============3534679496694244946== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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. > = 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) Thanks, Livnat --===============3534679496694244946==-- From abaron at redhat.com Sun Apr 29 06:24:36 2012 Content-Type: multipart/mixed; boundary="===============1683224784003567229==" MIME-Version: 1.0 From: Ayal Baron To: devel at ovirt.org Subject: Re: [Engine-devel] Disk Cloning When Creating a VM via a Template Date: Sun, 29 Apr 2012 06:24:34 -0400 Message-ID: <4d827afc-97e6-48d6-9cf1-2c5a6e2e84d6@zmail13.collab.prod.int.phx2.redhat.com> In-Reply-To: 4F9D0CA2.6070006@redhat.com --===============1683224784003567229== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- 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 f= or 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 cop= ied, the engine creates copies of all of the template images (calls moveIma= ge in vdsm per Image). > = > = > Thanks, Livnat > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel >=20 --===============1683224784003567229==-- From Dustin.Schoenbrun at netapp.com Mon Apr 30 10:00:37 2012 Content-Type: multipart/mixed; boundary="===============3445589838674050238==" MIME-Version: 1.0 From: Schoenbrun, Dustin To: devel at ovirt.org Subject: Re: [Engine-devel] Disk Cloning When Creating a VM via a Template Date: Mon, 30 Apr 2012 14:00:11 +0000 Message-ID: <0A1534657992624AACDCA570F1D3E20003C2C846@SACEXCMBX03-PRD.hq.netapp.com> In-Reply-To: 4d827afc-97e6-48d6-9cf1-2c5a6e2e84d6@zmail13.collab.prod.int.phx2.redhat.com --===============3445589838674050238== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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, a= ll disks associated with the template are cloned to go with the new VM, cor= rect? Could I do something similar with the floating disks and just clone = all of the associated disks from a VM? 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(a)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 f= or 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 cop= ied, the engine creates copies of all of the template images (calls moveIma= ge in vdsm per Image). > = > = > Thanks, Livnat > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel >=20 --===============3445589838674050238==-- From abaron at redhat.com Tue May 1 19:32:32 2012 Content-Type: multipart/mixed; boundary="===============1189505925745446040==" MIME-Version: 1.0 From: Ayal Baron To: devel at ovirt.org Subject: Re: [Engine-devel] Disk Cloning When Creating a VM via a Template Date: Tue, 01 May 2012 19:32:31 -0400 Message-ID: <4f0e54a3-090e-417b-9f2b-1c5df74d477e@zmail13.collab.prod.int.phx2.redhat.com> In-Reply-To: 0A1534657992624AACDCA570F1D3E20003C2C846@SACEXCMBX03-PRD.hq.netapp.com --===============1189505925745446040== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- 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(a)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 > > = >=20 --===============1189505925745446040==--