>>>
>> >>> pool.setUsedBytes(existingInfo.getCapacityBytes() -
>> >>> existingInfo.getAvailableBytes());
>> >>>
>> >>>
>> >>> On Mon, May 5, 2014 at 10:21 AM, Nitin Mehta
>> >>> wrote:
>> >>
>> This column is not used for calculating capacity for pool.
> >>>> We have always used op host capacity table. Nevertheless please do
> file
> >>>> a
> >>>> bug
> >>>>
> >>>> Thanks,
> >>>> -Nit
for pool.
>>>> We have always used op host capacity table. Nevertheless please do file
>>>> a
>>>> bug
>>>>
>>>> Thanks,
>>>> -Nitin
>>>>
>>>> From: Mike Tutkows
gt; >
> >> This column is not used for calculating capacity for pool.
> >> We have always used op host capacity table. Nevertheless please do file
> >>a
> >> bug
> >>
> >> Thanks,
> >> -Nitin
> >> __
t; -Nitin
>>
>> From: Mike Tutkowski [mike.tutkow...@solidfire.com]
>> Sent: Monday, May 05, 2014 9:12 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: How is this working?
>>
>> My storage plug-in actually uses a
gt; Thanks,
> -Nitin
>
> From: Mike Tutkowski [mike.tutkow...@solidfire.com]
> Sent: Monday, May 05, 2014 9:12 PM
> To: dev@cloudstack.apache.org
> Subject: Re: How is this working?
>
> My storage plug-in actually uses a custom host listener, so I have not
> encountered
@cloudstack.apache.org
Subject: Re: How is this working?
My storage plug-in actually uses a custom host listener, so I have not
encountered this issue.
I don't remember off hand if it was in 4.2 or 4.3, but at some point
someone changed the storage_pool table's available_bytes column to be
used_
My storage plug-in actually uses a custom host listener, so I have not
encountered this issue.
I don't remember off hand if it was in 4.2 or 4.3, but at some point
someone changed the storage_pool table's available_bytes column to be
used_bytes.
It looks like this code you reference was missed.
