cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Luc Dion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4568) Need to add this to the release note of 4.2
Date Wed, 21 May 2014 01:41:38 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004195#comment-14004195
] 

Pierre-Luc Dion commented on CLOUDSTACK-4568:
---------------------------------------------

This text could be added to  4.4 release-notes in the upgrade section of  4.1,4.0, 3.x and
2.2.14.

{code}
Settings Changes
----------------

After upgrading to 4.2 and later, Settings ``mem.overporvisioning.factor`` and ``cpu.overporvisioning.factor``
are now at the cluster level and be set to 1 which is the default.

If Global Settings ``mem.overporvisioning.factor`` and ``cpu.overporvisioning.factor`` have
been changed prior the upgrade to 4.2 and later, the upgrade process will be reset them to
1. Values can be changed by editing clusters settings.

All clusters created after the upgrade will get created with the Global Settings values for
``mem.overporvisioning.factor`` and ``cpu.overporvisioning.factor``.
{code}

Please let me know  if the text make sense. I will add this the the RN.

> 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: Radhika Nair
>              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)

Mime
View raw message