Re: [Engine-devel] ovirt core MOM

From: "Itamar Heim" <iheim(a)redhat.com&gt; To: "Ayal Baron" <abaron(a)redhat.com&gt; Cc: engine-devel(a)ovirt.org Sent: Friday, January 20, 2012 2:12:27 AM Subject: Re: [Engine-devel] ovirt core MOM On 01/19/2012 11:58 AM, Ayal Baron wrote: > > > ----- Original Message ----- >> On 01/18/2012 05:53 PM, Livnat Peer wrote: >>> Hi All, >>> >>> This is what we've discussed in the meeting today: >>> >>> Multiple storage domain: >>> - Should have a single generic verb for removing a disk. >>> - We block removing the last template disk - template is >>> immutable. >> >> but it will be deleted when deleting the template, right? > > Of course. > The point is that the template is an immutable object and should > not change (until we support editing a template at which point the > user would have to change the template to edit mode before being > able to make such changes and maybe also be able to run it and > make changes internally?). When i hear "edit a template" i don't expect replacing the files. I expect a new edition of disks appearing as a new version of the template. but they don't have to derive from same original template. say i want to create a "Fedora 16 template", then update it every month with latest "yum update". it doesn't matter if i use a VM from same template or just create a new one. then specify it is V2 of the "Fedora 16 template". when someone creates a VM from this template, default version would be latest (but we can let them choose specific older versions as well)

_______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel