[
https://issues.apache.org/jira/browse/CLOUDSTACK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011139#comment-14011139
]
ASF GitHub Bot commented on CLOUDSTACK-4568:
--------------------------------------------
GitHub user pdion891 opened a pull request:
https://github.com/apache/cloudstack-docs-rn/pull/13
New section: General Upgrade Notes
Add section: "General Upgrade Notes" which does not include Upgrade
instruction but considerations an changes against the new version to upgrade to.
ref issue: CLOUDSTACK-4568
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudops/cloudstack-docs-rn continuing_4.4
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack-docs-rn/pull/13.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13
----
----
> 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: Pierre-Luc Dion
> Labels: releasenotes
> Fix For: 4.4.0
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
