we would like to have a mechanism to modify a template and have the guests started from that template recognize the changes at the next reboot. This will make system updates, patch deployment, deployment of applications in batch very easier for the admin. The requirement given is as below. "I create a VM at time t, from it I create a template. Out of this template, I create 200 VMs and provide it to my users. At t+1, I have got a patch + new applications to provide to my user. I would like to do a copy of my original template, start it and modify it. In an ideal world, I would like to say that at the next reboot of the VMs or at 5:00 AM, it should switch from the old template to my new template. I should not require to rebuild a new pool out of this new template." it will allow easy management and deployment of updates, patch, applications and etc.
design wiki page http://www.ovirt.org/Features/Template_Versions
Hi, a sub-feature of this would be to be able to copy a template. This is, at least via GUI, not possible atm (ovirt 3.3.2). Should I file another BZ for this RFE? How would you handle changed userdata in your 200 vms? how should it get merged into the new template? Or is this feature only intended for stateless vms?
(In reply to Sven Kieske from comment #2) > Hi, > > a sub-feature of this would be to be able to copy a template. > This is, at least via GUI, not possible atm (ovirt 3.3.2). how does copying a template helps if you want to change it (compared to launching a VM from it, updating it, creating a template. > > Should I file another BZ for this RFE? > > How would you handle changed userdata in your 200 vms? how should it > get merged into the new template? Or is this feature only intended for > stateless vms? staeless VMs, you'd need app-virtualization kind of a thing to cover user-data
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.