[
https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Mehta resolved CLOUDSTACK-3664.
-------------------------------------
Resolution: Fixed
> 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
> Assignee: Nitin Mehta
> Fix For: 4.3.0
>
> Attachments: Logs_DB.rar, screenshot-1.jpg
>
>
> 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
> DB
> ====
> mysql> select *from cluster_details;
> +----+------------+----------------------------------------------------+-------+
> | id | cluster_id | name |
> value |
> +----+------------+----------------------------------------------------+-------+
> | 1 | 1 | cpuOvercommitRatio | 1.0
> |
> | 2 | 1 | memoryOvercommitRatio | 1.0
> |
> | 3 | 1 | cluster.memory.allocated.capacity.disablethreshold | 0.2
> |
> +----+------------+----------------------------------------------------+-------+
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
