We discussed this very thing awhile back, and decided the correct fix
was to have the storage drivers contain a method that would decide if
a pool type is capable of thin provisioning. It's a bigger fix than
this though.

On Sun, Feb 8, 2015 at 10:27 PM, ghxandsky <g...@git.apache.org> wrote:
> GitHub user ghxandsky opened a pull request:
>
>     https://github.com/apache/cloudstack/pull/74
>
>     Cloudstack doesn't consider storage overprovisioning factor when using 
> t...
>
>     ...hin Provisioning over ShareMountPoint with KVM.
>
> You can merge this pull request into a Git repository by running:
>
>     $ git pull https://github.com/ghxandsky/cloudstack 4.4
>
> Alternatively you can review and apply these changes as the patch at:
>
>     https://github.com/apache/cloudstack/pull/74.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
>     This closes #74
>
> ----
> commit e08815db152e469c6de8009b2d5058458c271d25
> Author: 郭华星 <guohuax...@96900.com.cn>
> Date:   2015-02-09T06:23:06Z
>
>     Cloudstack doesn't consider storage overprovisioning factor when using 
> thin Provisioning over ShareMountPoint with KVM.
>
> ----
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---

Reply via email to