Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 12 Jun 2013 09:36:20 +0000 (UTC)
From: "Harikrishna Patnala (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12637491.1363590632534.102995.1371029780835@arcas>
In-Reply-To: <JIRA.12637491.1363590632534@arcas>
References: <JIRA.12637491.1363590632534@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-1704) cluster is not getting disabled
 after threshold value set to global parameter
 "cluster.cpu.allocated.capacity.disablethreshold"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harikrishna Patnala resolved CLOUDSTACK-1704.
---------------------------------------------

    Resolution: Fixed
    
> cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1704
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Harikrishna Patnala
>             Fix For: 4.2.0
>
>         Attachments: cloud-backup.dmp, log.rar
>
>
> --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available.
>  -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank character at cluster level , Global parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working.
> Steps to reproduce
> ----------------------------
> 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 ,
> 2-Restart MS
> 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character
> 4-Deploy some vms , so  that cpu utilizatio should be >0.5
> Expected
> -------------
> Cluster should be disabled  after threshold value
> Actual
> -----------
> cluster is not getting disabled  after threshold value 

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