You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Eric Dey (JIRA)" <ji...@apache.org> on 2012/11/19 18:02:06 UTC
[jira] [Commented] (CLOUDSTACK-491) Instance Cloning
[ https://issues.apache.org/jira/browse/CLOUDSTACK-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500384#comment-13500384 ]
Eric Dey commented on CLOUDSTACK-491:
-------------------------------------
I am currently out of the office and will return on August 10th. If you require immediate support on a Caringo product, please use our help web site at: [1]https://support.caringo.com/
-Eric
----------------------------------
Eric Dey [2]<er...@caringo.com>
Caringo, Inc. (512)782-9902
----------------------------------------------------------------------------------------
[1] https://support.caringo.com/
[2] mailto:eric.dey@caringo.com
> Instance Cloning
> ----------------
>
> Key: CLOUDSTACK-491
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-491
> Project: CloudStack
> Issue Type: Improvement
> Components: Template
> Reporter: Clayton Weise
> Priority: Minor
>
> In some cases the template process can be exhaustive and wasteful. Templates make sense for large scale deployments of a common image but sometimes there is a need to make one or two clones of a system. The process of creating a template, offloading to secondary storage, then loading it _back_ onto primary only to make one or two copies of an instance seems unnecessary if there was simply an ability clone either directly on primary storage using a writable snapshot feature or offloading to secondary storage temporarily then removing the data once the copy has been made (similar to how volumes are imported).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira