Bug 954211

Summary:	[Docs][Admin] Note in "Creating a Template from an Existing Virtual Machine" incorrect.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Tim Hildred <thildred>
Component:	Documentation	Assignee:	Jodi Biddle <jbiddle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, chetan, gianluca.cecchi, gklein, sfolkwil, yeylon
Target Milestone:	---	Keywords:	Documentation
Target Release:	3.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Hildred 2013-04-21 23:46:20 UTC

Description of problem:

This note isn't required:
"Take a snapshot of the virtual machine at this stage if you wish to use the virtual machine (as a virtual machine) after using it to create a template."

You can use the virtual machine as a virtual machine after you make a template from it, even if you haven't taken a snapshot.

Comment 1 Tim Hildred 2013-04-22 00:00:33 UTC

Raised here:
http://lists.ovirt.org/pipermail/users/2013-March/013575.html

Comment 2 Gianluca Cecchi 2013-04-22 06:48:12 UTC

I think it could be important to put sort of note here, taking in consideration also what Rene' wrote in the trhead link provided.

A suggestion could be to transform it in:

Unlike other virtualization platforms, which convert a vm into a template, RHEV makes a copy of the vm into a template as a separate entity.
Take a snapshot of the virtual machine at this stage (for example before sealing phase) if you wish to use it (as a virtual machine) after template creation.

Comment 3 Gianluca Cecchi 2013-04-22 06:55:58 UTC

Unlike other virtualization platforms, which convert a vm into a template, RHEV makes a copy of the vm into a template as a separate entity.
The original VM will be there and usable after template creation.
Take a snapshot of it at this stage (for example before the sealing phase) if you wish to use it (as a virtual machine) after template creation.
Otherwise you can safely delete your original VM, without any impact on template.

Comment 4 Jodi Biddle 2013-05-13 05:10:23 UTC

After examining the surrounding context, I decided to go with the following for the admonition: 

"When a template is made, the virtual machine is copied so that both the existing virtual machine and its template are usable after template creation." 

This keeps the statement broad enough for the scope of an admonition. The need/desire to take a snapshot seems like it would only apply to specific use cases. 

Gianluca, do you think the snapshot part is important enough to mention anyway? If so, I'll find another way to include it; probably by editing an existing concept topic or creating a new one relating to template creation.

Comment 5 Gianluca Cecchi 2013-05-13 07:11:12 UTC

I think it is ok what you wrote. Something related to the snapshot part could be put then at the following 9.3.1 inside the "Summary" paragraph as a reminder.

Comment 7 Gianluca Cecchi 2013-05-29 09:04:37 UTC

Hello,
I have no access to ip of documentation-devel.engineering.redhat.com server ...
Let me know if I have to check it or not...

Comment 8 Jodi Biddle 2013-05-29 23:19:51 UTC

Apologies Gianluca. That was supposed to be an internal message. The documentation will be changed as you suggested but you probably won't see the changes until the 3.2 GA in mid-June.