[
https://issues.apache.org/jira/browse/CLOUDSTACK-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734467#comment-13734467
]
Bharat Kumar commented on CLOUDSTACK-856:
-----------------------------------------
Hi Jessica,
I have gone through the doc. we need to add some more details to this.
There has been a change in the add cluster API we cannot specify the overcommit
values at the time of adding the cluster.
when the cluster is add the overcommit values from the global setting are set
to the new cluster. Later after adding these values can be changed from
the settings tab.
Also if the overcommit ratios is changed while some of the vms in the cluster
are still running, the change of the overcommit will effect only newly create
vms i.e. vms created after overcommit change.
In order to effete the previously deployed vms we need to start stop them. Also
in this case the used and the reserved capacities will be recalculated or
scaled based on the new overcommit ratios. This is done to keep track of
correct amount of free capacity.
The scaling happens when the capacity checker runs. We do not stop the vm
deployment while capacity is being recalculated. But it is not recommended to
deploy VMs before capacity
is recalculated as in some cases this might lead to greater capacity allocation
than what is available.
In case of kvm we need to create a separate title and mention that Kvm dose not
adjust the guest memory dynamically based on the contention.
Regards,
Bharat.
And if the overcommit ratios are dynamically changed the
> [DOC] Document CPU and memory overcommit functionality.
> --------------------------------------------------------
>
> Key: CLOUDSTACK-856
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-856
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Reporter: David Nalley
> Assignee: Sudha Ponnaganti
> Fix For: 4.2.0
>
>
> Document CPU and memory overcommit functionality
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
