@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning
On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:
Hi
Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?
No. It is the real usage
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, October 24, 2013 13:13
To: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning
On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:
Hi
Thanks for this have reverted it back to .85, does
.
Is this a normal behavior?
Thanks for your input.
François
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, January 09, 2014 13:27
To: François Bousquet
Cc: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning
When you increase
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, January 09, 2014 13:27
To: François Bousquet
Cc: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning
When you increase the factor, the allocated percentage decreases and
hence you can
Hi
Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?
Is there a way to allow pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM
Hi
I am seeing an issue here with Cloudstack and VMWare storage and hope you
can help. VMWare is using dynamic storage so for a template of 20GB in
reality only 3GB is being used, VMWare currently has the size of the VM of
3GB and increases storage allocation to the VM as it requires it.
Advise you to not keep pool.storage.capacity.disablethreshold as 1 (100%).
This captures the actual usage of the storage and you do not want it to
reach 100% especially possible when you have over provisioned.
On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:
Hi
I am seeing an issue here
