meysamfarazmand opened a new issue #4390:
URL: https://github.com/apache/cloudstack/issues/4390
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Management Server
-->
~~~
~~~
##### CLOUDSTACK VERSION
<!--
4.13.0.0
-->
~~~
~~~
##### CONFIGURATION
<!--
cpu.overprovisioning.factor=6
mem.overprovisioning.factor=1.1
-->
##### OS / ENVIRONMENT
<!--
CentOS 6
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
My cloudstack deployment has 1000 VMs. i had configured
cpu.overprovisioning.factor=3.5 until i faced 95% of cpu allocation and decided
to change cpu.overprovisioning.factor=6 in cluster settings. i expected new
settings being applied and "Allocable" cpu goes higher than "Allocated" ,but
"Allocable" and "Allocated" cpus goes up together and no matter which number
has been set in "cpu.overprovisioning.factor". As i have read in cloudstack
documentations, it seems i MUST stop and start all VMs for new
"cpu.overprovisioning.factor" settings to be applied. is this true or there is
another way to reach my goal?
http://docs.cloudstack.apache.org/projects/archived-cloudstack-administration/en/latest/hosts.html#requirements-for-over-provisioning
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
