- What is the nature and description of the request? Support for the performing sysprep operations such as attaching the sysprep "floppy image" from the RHEV API. - Why does the customer need this? (List the business requirements here) To make proper sysprep file, VM needs access to those sysprep file templates in /etc/ovirt-engine/sysprep on RHEV-M host, but and application that uses REST API does not have such access. The application runs on separate isolated host. From the RHEV-M admin web interface there is access to the option to attach the xml file to any VM on demand using "Run once", and it will be generated from /etc/ovirt-engine/sysprep automatically. It should be possible to provide those generated xml files on demand in similar manner to any VM using RHEV REST API only. - For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Sysprep a VM using the RHEV REST API
we planned to have an option to pass a custom sysprep file to be used instead of the system-wide file. Would it satisfy the requirement? It won't allow you to get the generated output as is generated in UI, but it allows you to specify and generate exactly what you want In other words supply a custom template sysprep file.
As long as it's fully controllable from the API, then the customer's needs would be met.
hopefully will be addressed by bug 1080002
this issue has been addressed as part of the sysprep custom script feature, in 3.5. Also when talking about API it has already been possible using the VM payload *** This bug has been marked as a duplicate of bug 1080002 ***