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

[Aline Manera]

On 01/28/2014 01:11 PM, 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.
>
> |

ACK

> |
> 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
> |

For this second item, there is a specific item for sprint 4

"(alinefm) Create template from VM"

And I've already sent a patch for it long time ago: 
https://groups.google.com/forum/#!msg/project-kimchi/YR6ewAwFaEA/ZsaU4En7jlUJ

For sprint 3, I think we can focus only on item 1, which is the template 
clone itself.

> |
> |
> -- 
> 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



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