<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 5, 2016 at 10:57 AM, Moran Goldboim <span dir="ltr"><<a href="mailto:mgoldboi@redhat.com" target="_blank">mgoldboi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="gmail-">On Mon, Dec 5, 2016 at 9:45 AM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Dec 5, 2016 at 9:18 AM, Shmuel Melamud <span dir="ltr"><<a href="mailto:smelamud@redhat.com" target="_blank">smelamud@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace;font-size:x-small"><br></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Sun, Dec 4, 2016 at 10:39 PM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><span><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Dec 4, 2016 8:50 PM, "Shmuel Melamud" <<a href="mailto:smelamud@redhat.com" target="_blank">smelamud@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail-m_-7764855345669564754m_4733179259224627847m_2212154011490898003m_-7282233544101988070quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace;font-size:x-small">Hi!<br><br></div><div style="font-family:monospace,monospace;font-size:x-small">I'm currently working on integration of virt-sysprep into oVirt.<br><br></div><div style="font-family:monospace,monospace;font-size:x-small">Usually, if user creates a template from a regular VM, and then creates new VMs from this template, these new VMs inherit all configuration of the original VM, including SSH keys, UDEV rules, MAC addresses, system ID, hostname etc. It is unfortunate, because you cannot have two network devices with the same MAC address in the same network, for example.<br><br></div><div style="font-family:monospace,monospace;font-size:x-small">To avoid this, user must clean all machine-specific configuration from the original VM before creating a template from it. You can do this manually, but there is virt-sysprep utility that does this automatically.<br><br>Ideally, virt-sysprep should be seamlessly integrated into template creation process. But the first step is to create a simple button: user selects a VM, clicks the button and oVirt executes virt-sysprep on the VM.<br></div></div></blockquote></div></div></div><div dir="auto"><br></div></span><div dir="auto">User selects a VM or a template disk? </div><span></span></div></blockquote></span><div><br><div>A VM. It is not safe to modify template disks. We cannot guarantee that there are no VMs based on this template, because some of them may reside on a detached storage.</div></div></div></div></div></blockquote><div><br></div></span><div>Any template disk that VM were derived from it is not safe to perform this operation. On a pristine template disk it is Ok - and it is exactly where I expect this process to take place.</div><div>The user flow should be a checkbox in the create template flow.</div><div>Y.</div><div> </div></div></div></div></blockquote><div><br></div></span><div>big +1 here, a general bottom doesn't indicate the user when to perform the action, and takes it away from the desired flow. since the problem you are presenting here is specifically around template creation, i also thing that a checkbox here with the ability to "seal" the template, is the desired solution to be aiming for.<br></div></div></div></div></blockquote><div><br></div><div>another aspect of this specific user story, is the ability to directly transform this "sealed" vm directly to a template - many of the times it's just being deleted afterwards and the user is just "paying" for the storage actions<br><br></div><div>please look at<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1013675"><b> Bug 1013675</b></a> -<span id="gmail-summary_alias_container">
<span id="gmail-short_desc_nonedit_display">[RFE] In-place transformation of a VM to a Template - for details.<br></span></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span class="gmail-"><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><span class="gmail-m_-7764855345669564754m_4733179259224627847HOEnZb"><font color="#888888"> <br></font></span></div></div><span class="gmail-m_-7764855345669564754m_4733179259224627847HOEnZb"><font color="#888888"><div>Shmuel</div><br></font></span></div></div>
</blockquote></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>