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 of the disk equivalent of "df -h". > >Is there a way to allow pool.storage.allocated.capacity.disablethreshold >utilise the overprovisining factor and stop blocking VM creation when we >reach the 85% threshold Nope. Do read https://cwiki.apache.org/confluence/display/CLOUDSTACK/Understanding+Dashbo ard To understand allocated and real usage that CS captures > >Thanks >Noel > > >On 24 October 2013 01:32, Nitin Mehta <nitin.me...@citrix.com> wrote: > >> 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 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. >>However >> >Cloudstack thinks 20GB has been consumed >> > >> >So to overcome this we set >> > >> >storage.overprovisioning.factor to 5 >> > >> >But we still had issues when we hit 85% (which is not 85% based on >>VMWare >> >storage allocation). The following values were set to .85 and >>increasing >> >these has offered little benefit up to 100% >> > >> > >> > - pool.storage.capacity.disablethreshold >> > - pool.storage.allocated.capacity.disablethreshold >> > >> > >> >Any advise on other settings on Cloudstack 4.1.1 that could help us. >> > >> >Kind regards >> > >> >Noel >> >>
