You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/07/19 12:58:49 UTC
[jira] [Updated] (CLOUDSTACK-3664) scaling up vms is not
considering parameter
"cluster.(memory/cpu).allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
prashant kumar mishra updated CLOUDSTACK-3664:
----------------------------------------------
Summary: scaling up vms is not considering parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold" (was: scaling up vm is not considering cluster parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold")
> scaling up vms is not considering parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3664
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3664
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Environment: xen 4.2
> Reporter: prashant kumar mishra
> Attachments: Logs_DB.rar
>
>
> steps to reproduce
> ================
> 1-prepare a CS setup with xen 6.1
> 2-set "cluster.memory.allocated.capacity.disablethreshold" to some lower value say 0.2
> 3-deploy some vms until unless deployment fails because of threshold value.
> 4-Try to scale up vms
> Expected
> --------------
> scaling up should get failed because threshold value
> Actual
> ----------
> scaling up is successful
--
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