Bug 1037478

Summary:	[RFE] Have ability to modify VM template - template versions
Product:	[Retired] oVirt	Reporter:	Omer Frenkel <ofrenkel>
Component:	ovirt-engine-core	Assignee:	Omer Frenkel <ofrenkel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.4	CC:	acathrow, ahoness, byount, dsimmons, iheim, jeffj, jfenal, jkt, jwest, kroberts, mavital, michal.skrivanek, mrao, orenault, psubrama, Rhev-m-bugs, scohen, s.kieske, ssekidde, tao, ukar, vvasilev, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.4.0
Hardware:	All
OS:	Linux
Whiteboard:	virt
Fixed In Version:	ovirt-3.4.0-beta2	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	558995	Environment:
Last Closed:	2014-03-31 15:05:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Omer Frenkel 2013-12-03 09:20:41 UTC

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.

Comment 1 Omer Frenkel 2013-12-03 09:24:32 UTC

design wiki page
http://www.ovirt.org/Features/Template_Versions

Comment 2 Sven Kieske 2014-01-10 08:29:47 UTC

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?

Comment 3 Itamar Heim 2014-01-10 21:03:27 UTC

(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

Comment 4 Sandro Bonazzola 2014-03-31 15:05:39 UTC

This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.