cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4538) Need to update the vmware clusters with the global overporvisioning factors after upgrade to 4.2.
Date Tue, 03 Sep 2013 23:11:54 GMT

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

ASF subversion and git services commented on CLOUDSTACK-4538:
-------------------------------------------------------------

Commit 30c5388253db121f5557231523c23a80e72ac3b7 in branch refs/heads/4.2 from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=30c5388 ]

CLOUDSTACK-4538: set default value of cpu.overprovisioning.factor and mem.overprovisioning.factor
to 1

On a fresh environment, some values in cloud.configuration table are persisted in com.cloud.server.ConfigurationServerImpl.persistDefaultValues()
A default value need to be set before com.cloud.upgrade.DatabaseUpgradeChecker
(cherry picked from commit 1a67750cb66cf74175e2776ba3f3ba76fde0d1bb)
(cherry picked from commit 61ebfad4493d4f3fe4ced948985e69202080654b)

Signed-off-by: animesh <animesh@apache.org>

                
> Need to update the vmware clusters with the global overporvisioning factors after upgrade
to 4.2.
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4538
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4538
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.0
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>             Fix For: 4.2.0
>
>


--
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

Mime
View raw message