You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Kiran manohar Chavala <ki...@gmail.com> on 2013/04/03 08:16:43 UTC
Global settings parameter configuration
Hi all
General question
If i change the value host.capacityType.to.order.clusters = cpu to ram
which other parameter does it affect
These two parameters
Param1) cluster.cpu.allocated.capacity.disablethreshold
Param2) cluster.cpu.allocated.capacity.notificationthreshold
Regards
Kiran
Re: Global settings parameter configuration
Posted by prasanna <ts...@apache.org>.
On 3 April 2013 11:46, Kiran manohar Chavala <ki...@gmail.com> wrote:
> Hi all
>
> General question
>
> If i change the value host.capacityType.to.order.clusters = cpu to ram
>
> which other parameter does it affect
The above setting is the heuristic used by the deployment planner to
decide on the cluster to house a VM into. That heuristic is affected
by the cpu OverCommit and memory overcommit ratios only.
The following two parameters are not directly affected by the above setting.
>
> These two parameters
> Param1) cluster.cpu.allocated.capacity.disablethreshold
However, this param disables the cluster for further deployment. So
the disabled cluster is removed from being considered by the planner
while computing the aggregate capacity using the host.capacityType
setting.
> Param2) cluster.cpu.allocated.capacity.notificationthreshold
This is the setting used to send out an alert event that you see on
the dashboard. So it doesn't affect the planner.