You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2014/03/02 00:36:20 UTC

[jira] [Commented] (CLOUDSTACK-6191) Volume provisioning type option

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917224#comment-13917224 ] 

Marcus Sorensen commented on CLOUDSTACK-6191:
---------------------------------------------

Is this is largely specific to QCOW2-based storage? I think many storage pool types either aren't capable of some of these features, or don't make a distinction (e.g. thin is often implemented by using sparse, or there may be a thin option on a storage type but no sparse). At any rate, it's probably best implemented as a disk offering parameter, that way it doesn't have to be selected globally, one could run any and all combinations. It would be similar to the iops tuneables in the disk offerings, and passed along when volumes are created so that individual storage drivers can choose whether or not to pay attention to the parameters.

> Volume provisioning type option
> -------------------------------
>
>                 Key: CLOUDSTACK-6191
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Management Server
>            Reporter: Yoshikazu Nojima
>            Assignee: Yoshikazu Nojima
>            Priority: Minor
>             Fix For: Future
>
>
> Thin provisioning of a volume saves consumption of a storage, and fat provisioning minimizes IOPS performance overhead.
> This feature implements a global setting to provide users an option to select how to provision volumes.
> Design doc:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)