[
https://issues.apache.org/jira/browse/CLOUDSTACK-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772531#comment-15772531
]
ASF GitHub Bot commented on CLOUDSTACK-9703:
--------------------------------------------
GitHub user anshul1886 opened a pull request:
https://github.com/apache/cloudstack/pull/1860
CLOUDSTACK-9703: Fixed Start VM does not honor
cluster.cpu.allocated.capacity.disablethreshold if the vm is startting on last
host
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-9703
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1860.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1860
----
commit 4d398b893991f6e94222489fe26cc32c37ca099f
Author: Anshul Gangwar <anshul.gang...@accelerite.com>
Date: 2016-06-22T08:05:11Z
CLOUDSTACK-9703: Fixed Start VM does not honor
cluster.cpu.allocated.capacity.disablethreshold if the vm is startting on last
host
----
> Start VM does not honor cluster.cpu.allocated.capacity.disablethreshold if
> the vm is startting on last host
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9703
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9703
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Anshul Gangwar
> Assignee: Anshul Gangwar
>
> Steps to reproduce:
> 1. Create a xen cluster with multiple instances. Keep some instances in STOP
> state
> 2. Check the CPU Allocated in Cluster Metrics page. It was 57%
> 3. Set cluster.cpu.allocated.capacity.disablethreshold to 50% and restart
> cloudstack-management service
> 4. Re-Login the server and goto cluster metrics page again. CPU Allocated
> field is highlighted in Red
> 5. Start an instance in which was in stopped state.
> 6. CPU allocation increases from 57% to 67%
> Expected:
> If CPU allocated values has already crossed
> cluster.cpu.allocated.capacity.disablethreshold start VM operation should not
> be allowed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
