[
https://issues.apache.org/jira/browse/CLOUDSTACK-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815626#comment-13815626
]
ASF subversion and git services commented on CLOUDSTACK-4810:
-------------------------------------------------------------
Commit 10c513a2592d2be4a06b0478672a3ea0b1ad0da3 in branch refs/heads/master
from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=10c513a ]
CLOUDSTACK-4810: Enable hypervisor snapshots for CloudStack-managed storage
(for XenServer and VMware)
> Enable hypervisor snapshots for CloudStack-managed storage (for XenServer and
> VMware)
> -------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4810
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4810
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Environment: Ubuntu 12.04
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Fix For: 4.3.0
>
>
> CloudStack-managed storage was introduced into CloudStack with the new
> storage framework in 4.2.
> This allows CloudStack to create and delete storage repositories and
> datastores as needed.
> For 4.2 the VDI inside of an SR takes up almost as much space as is available
> in the SR (so there is a one-to-one mapping between an SR and a VDI). This is
> the same idea for datastores and VMDKs.
> The SR or datastore should be sized larger than its VDI or VMDK so there is
> space available for hypervisor snapshots that get stored on the same SR or
> datastore.
> How much larger can be determined by a cluster-level setting.
> For example, if you want a 10 GB CloudStack volume, the storage plug-in in
> question can create, say, a 20 GB volume on its SAN. 10 GB to be used for the
> CloudStack volume and an additional 10 GB for hypervisor snapshots.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
