[
https://issues.apache.org/jira/browse/CLOUDSTACK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754841#comment-13754841
]
Bharat Kumar commented on CLOUDSTACK-4568:
------------------------------------------
same is the case for mem.overprovisoining.factor, used for cpu reservation.
> Need to add this to the release note of 4.2
> -------------------------------------------
>
> Key: CLOUDSTACK-4568
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4568
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.2.0
> Reporter: Bharat Kumar
> Assignee: Jessica Tomechak
> Labels: releasenotes
> Fix For: 4.2.1
>
>
> After upgrade to 4.2 the mem.overporvisioning.factor and
> cpu.overporvisioning.factor will be set to one that is the default value and
> are at cluster level now.
> In case if some one prior to the 4.2 was usign mem.overporvisioning.factor
> and cpu.overporvisioning.factor after the upgrade these will be reset to one
> and can be changed by editing the cluster settings.
> All the clusters created after the upgrade will get created with the values
> overcomit values specified at the global config by default.
--
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
