<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 1/28/2014 10:11 AM, Sheldon wrote:<br>
</div>
<blockquote cite="mid:52E7C895.7090408@linux.vnet.ibm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<h4><a moz-do-not-send="true"
href="https://github.com/kimchi-project/kimchi/wiki/template-cloning-and-customization#wiki-template-cloning">template
cloning: </a><br>
</h4>
<pre><code>1 </code><code><code>clone a template</code> from </code><code><code>template</code>
The user may clone a template from an existing template with different name.
Later he can customize some parts of the template to save the effort to create a full new template.
For example, he can update the network of the template cloned to have a new different template. </code></pre>
</blockquote>
<code>Can we provide a reasonable default the name of the clone</code>?
With the full edit flow in place, its tempting to just add <br>
a "duplicate template" action to template. The action default
everything in the new template.<br>
<blockquote cite="mid:52E7C895.7090408@linux.vnet.ibm.com"
type="cite">
<pre><code>
2. </code><code>we should also also user </code><code><code><code>clone a template</code> from vm</code>
</code>I just concern the image volume.
For vm may has no CDROM attribute.
Then does the template need to copy the image volume.
<code>For VM clone, can we make the the vm image as a backing file(or we can
call it base image).
Then we can create two new images for this vm and new vm.
All these two new images are a read/write snapshot of the original image,
-- any changes to new images will not be reflected in original image.
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://libvirt.org/formatstorage.html#StorageVolBacking">http://libvirt.org/formatstorage.html#StorageVolBacking</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.qemu.org/Documentation/CreateSnapshot">http://wiki.qemu.org/Documentation/CreateSnapshot</a>
</code></pre>
</blockquote>
Section 2 of the RFC gets very interesting, but somewhat more
complicated than clone template. <br>
I suggest we treat this scenario as a create template scenario, and
separately from clone template.<br>
<br>
<blockquote cite="mid:52E7C895.7090408@linux.vnet.ibm.com"
type="cite">
<pre><code>
</code></pre>
<pre class="moz-signature" cols="72">--
Thanks and best regards!
Sheldon Feng(冯少合)<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:shaohef@linux.vnet.ibm.com"><shaohef@linux.vnet.ibm.com></a>
IBM Linux Technology Center</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Adam King <a class="moz-txt-link-rfc2396E" href="mailto:rak@linux.vnet.ibm.com"><rak@linux.vnet.ibm.com></a>
IBM CSI</pre>
</body>
</html>