Hi Valery,
if you change the cpu.overprovisioning.factor for a cluster it will not
effect the running VMs, only the VMs deployed after
overcommit change will be effected. In other words cloudstack will not
reconfigure the running VMs with the new overcommit values.
Also cloudstack adjusts
Hi, Bharat
No, I see incorrect values AFTER the capacity checker runs again. During
first 5 minutes after changes values are correct.
On Tue, Oct 15, 2013 at 12:29 PM, Bharat Kumar wrote:
> Hi Valery,
> you will see incorrect values until the capacity checker runs again. By
> default i think it
Hi Valery,
you will see incorrect values until the capacity checker runs again. By default
i think it runs every 5 min.
you can change the interval at which capacity checker runs by changing the
capacity.check.period
global config.
-Bharat.
On Oct 15, 2013, at 1:56 PM, Valery Ciareszka
wrot
Hi all.
I'm using CS 4.2.0 / CentOS 6.4/KVM and I faced the following problem:
If cpu.overprovisioning.factor for cluster is being changed, dashboard
reports incorrect values, unless all vms are restarted (stop/start).
I.e. I configured cluster and set cpu.overprovisioning.factor to 6 and
starte
