<div dir="auto"><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">smelamud@redhat.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Hi!<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">I'm currently working on integration of virt-sysprep into oVirt.<br><br></div><div class="gmail_default" 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 class="gmail_default" 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><div dir="auto">User selects a VM or a template disk? </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">virt-sysprep works directly on VM's filesystem. It accepts list of all disks of the VM as parameters:<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">virt-sysprep -a disk1.img -a disk2.img -a disk3.img<br></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">I would suggest for the 1st phase implementing it on the boot device only. </div><div dir="auto">Yes, theoretically it may have to do some work on other disks (swap may be on a separate disk, etc.). Practically, I think we can live with the limitation. </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">The architecture is as follows: command on the Engine side runs a job on VDSM side and tracks its success/failure. The job on VDSM side runs virt-sysprep.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">The question is how to implement the job correctly?<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">I thought about using storage jobs, but they are designed to work only with a single volume, correct? Is is possible to use them with operation that is performed on multiple volumes?<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Or, alternatively, is it possible to use some kind of 'VM jobs' - that work on VM at whole? How v2v solves this problem?<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Any ideas?<font color="#888888"><br><br></font></div><font color="#888888"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Shmuel<br></div></font></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div></div></div>