I think it won't. A hacky workaround you can try is change the total capacity itself to an increased value in the DB(tables - op_host_capacity, storage_pool). See if you like it and whether it works.
On 10/10/13 2:02 PM, "Chris Sciarrino" <chris.sciarr...@gmail.com> wrote: >Storage 461GB/5TB >Primary Storage Allocated 2.5TB/5TB > >I am not running out of real space, but when the allocated storage >gets too high I cannot deploy vms. The storage.overprovisioning.factor >multiplier is not having any effect in allowing me to overprovision >storage. > >On Thu, Oct 10, 2013 at 4:43 PM, Musayev, Ilya <imusa...@webmd.net> wrote: >> Goto Infrastructure, Zone, Resources >> >> Compare Storage value VS Primary Allocated Storage value. >> >> Storage value is the actual size used in my opinion. >> >> Are you running of space and cant launch vms? >> >>> -----Original Message----- >>> From: Chris Sciarrino [mailto:chris.sciarr...@gmail.com] >>> Sent: Thursday, October 10, 2013 2:36 PM >>> To: users@cloudstack.apache.org >>> Subject: Re: Cloudstack System Capacity - VMFS Storage >>> >>> Okay thanks Ilya for confirming, I'll have to look into why it's not >>>taking effect >>> in my setup. >>> >>> On Thu, Oct 10, 2013 at 1:37 PM, Musayev, Ilya <imusa...@webmd.net> >>> wrote: >>> > I don't believe ACS knows the difference between ISCSI and VMFS. >>> > >>> > I'm using VMFS. >>> > >>> >> -----Original Message----- >>> >> From: Chris Sciarrino [mailto:chris.sciarr...@gmail.com] >>> >> Sent: Thursday, October 10, 2013 12:48 PM >>> >> To: users@cloudstack.apache.org; Musayev, Ilya >>> >> Subject: Re: Cloudstack System Capacity - VMFS Storage >>> >> >>> >> Hi Ilya, >>> >> >>> >> Can you confirm that you are using fiber channel VMFS type as your >>> >> primary storage? I have tried enabling the >>> >> storage.overprovisioning.factor in the global settings previously >>>and >>> >> it made no difference. The docs show that VMware storage >>> >> overprovisioning is only supported on NFS and iSCSI, so I am >>>curious if this >>> is working for you. >>> >> >>> >> Thanks, >>> >> >>> >> Chris >>> >> >>> >> On Thu, Oct 10, 2013 at 11:38 AM, Musayev, Ilya >>> <imusa...@webmd.net> >>> >> wrote: >>> >> > Chris, >>> >> > >>> >> > Current solution is to enable storage.overprovisioning.factor in >>> >> > global >>> >> settings. Long term solution as per discussion with Edison, who >>> >> maintains storage framework, is to do real lookup of actual space. >>> >> > >>> >> > I'm in exact situation as you are, I've overprovisioned by factor >>> >> > of 20 >>> >> (maybe an over kill). I also rely on vSphere monitoring for space >>>alerts. >>> >> > >>> >> > Regards >>> >> > ilya >>> >> > >>> >> >> -----Original Message----- >>> >> >> From: Chris Sciarrino [mailto:chris.sciarr...@gmail.com] >>> >> >> Sent: Thursday, October 10, 2013 10:21 AM >>> >> >> To: users@cloudstack.apache.org >>> >> >> Subject: Cloudstack System Capacity - VMFS Storage >>> >> >> >>> >> >> Hi, >>> >> >> >>> >> >> I have the situation where I have deployed a fairly large amount >>> >> >> instances of the same template. This has increased the amount of >>> >> >> allocated primary storage used to over 2.5 TB . However due to >>>the >>> >> >> usage of linked clones I am really only using a couple of >>>hundred GB. >>> >> >> The primary storage type is a VMFS datastore so I do not believe >>>I >>> >> >> can overprovision it in cloudstack. The problem lies when trying >>> >> >> to deploy more instances it is failing because the amount I have >>> >> >> allocated is over the disable threshold even though I have plenty >>> >> >> of actual >>> >> storage left. >>> >> >> >>> >> >> Is there any way around this? Or any way to make cloudstack see >>> >> >> the actual storage usage on the VMFS datastores? >>> >> >> >>> >> >> Thanks, >>> >> >> >>> >> >> Chris >>> >> > >>> >> > >>> > >>> > >> >>
