[ovirt-devel] [VDSM] Correct implementation of virt-sysprep job

[Yaniv Kaul]

On Mon, Dec 5, 2016 at 9:18 AM, Shmuel Melamud <smelamud at redhat.com> wrote:

>
>
> On Sun, Dec 4, 2016 at 10:39 PM, Yaniv Kaul <ykaul at redhat.com> wrote:
>
>>
>>
>> On Dec 4, 2016 8:50 PM, "Shmuel Melamud" <smelamud at redhat.com> wrote:
>>
>> Hi!
>>
>> I'm currently working on integration of virt-sysprep into oVirt.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>>
>> User selects a VM or a template disk?
>>
>
> ​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.​
>

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.
The user flow should be a checkbox in the create template flow.
Y.


>
> ​Shmuel​
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20161205/1a92e202/attachment-0001.html>