[Kimchi-devel] [RFC]: for template cloning.

Adam King rak at linux.vnet.ibm.com
Wed Jan 29 15:06:16 UTC 2014


On 1/28/2014 10:11 AM, Sheldon wrote:
>
>
>         template cloning:
>         <https://github.com/kimchi-project/kimchi/wiki/template-cloning-and-customization#wiki-template-cloning>
>
> |1|||clone a template|  from|||template|
> 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.|
|Can we provide a reasonable default the name of the clone|? With the 
full edit flow in place, its tempting to just add
a "duplicate template" action to template. The action default everything 
in the new template.
> |
>
>
> 2.||we should also also user||||clone a template|  from vm|
> |I just concern the image volume.
> For vm may has no CDROM attribute.
> Then does the template need to copy the image volume.
> |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.
>
>
> http://libvirt.org/formatstorage.html#StorageVolBacking
>
> http://wiki.qemu.org/Documentation/CreateSnapshot
> |
Section 2 of the RFC gets very interesting, but somewhat more 
complicated than clone template.
I suggest we treat this scenario as a create template scenario, and 
separately from clone template.

> |
> |
> -- 
> Thanks and best regards!
>
> Sheldon Feng(???)<shaohef at linux.vnet.ibm.com>
> IBM Linux Technology Center
>
>
> _______________________________________________
> Kimchi-devel mailing list
> Kimchi-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/kimchi-devel

-- 
Adam King <rak at linux.vnet.ibm.com>
IBM CSI

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20140129/0c58a5ee/attachment.html>


More information about the Kimchi-devel mailing list