Hi Prachi,
When I said actual I was referring to the minimum memory available to a VM.
Bharat.
On Feb 6, 2013, at 1:11 AM, Prachi Damle wrote:
> Hi Bharat / Abhi,
>
> Even currently we always store actuals in the DB in op_host_capacity table.
> During allocation, the overprovisioning ratios
Bharat,
This is a 4.1 feature. Please update the progress and the git commit
sent for review in jira.
-abhi
On 05/02/13 12:14 PM, "Abhinandan Prateek"
wrote:
>
>On 01/02/13 4:22 PM, "Bharat Kumar" wrote:
>
>>Hi All,
>>
>>I have made changes to the way capacity is calculated in Cloudstack ,
>
Prachi,
For Hypervisor not supporting overcommit, the cluster of those
hypervisors cannot have a overcommit. It should not affect the current
capacity calculation. Bharat will be able to elaborate on this.
-abhi
On 06/02/13 1:11 AM, "Prachi Damle" wrote:
>Hi Bharat / Abhi,
>
>Even currently w
Hi Bharat / Abhi,
Even currently we always store actuals in the DB in op_host_capacity table.
During allocation, the overprovisioning ratios are applied dynamically to find
the overprovisioned "total" capacity.
So it's good that even the new way will follow that.
>Major differences are
>1.) In
