[
https://issues.apache.org/jira/browse/CLOUDSTACK-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753583#comment-13753583
]
Bharat Kumar edited comment on CLOUDSTACK-4538 at 8/29/13 1:00 PM:
-------------------------------------------------------------------
Hi Wei,
I had the fix in the review board since long
(https://reviews.apache.org/r/13886/diff/1-2/). but was trying to decide on the
default behaviour. The cpu and memory over provisioning values are there in
3.0.7 and may be even before. but there was no validation of these parameters
earlier.
was trying to decide if we need to stop the upgrade procedure with a error
message or set the default value in case of erroneous config while upgrade.
However thanks for fixing the issue.
was (Author: bharat.kumar):
Hi Wei,
I had the fix in the review board since long
(https://reviews.apache.org/r/13886/diff/1-2/). but was trying to decide on the
default behaviour. The cpu and memory over provisioning values are there in
3.0.7 and may be even before. but there was no validation of these parameters
earlier.
was trying to decide if we need to stop the upgrade procedure with a error
message or set the default value.
However thanks for fixing the issue.
> 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
