cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-1704) allocatore is not disabling cluster after the threshold value, set in "cluster.cpu.allocated.capacity.disablethreshold"
Date Mon, 18 Mar 2013 07:12:15 GMT
prashant kumar mishra created CLOUDSTACK-1704:
-------------------------------------------------

             Summary: allocatore is not disabling cluster after the threshold value, set in
"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
             Fix For: 4.2.0


 "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.
Keep the corresponding notification threshold lower than this to be notified beforehand.


Hypervisor "xen"
Branch "Master"

Steps to reproduce
----------------------------
1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 ,
2-Restart MS
3-Deploy some vms , so  that cpu utilizatio should be >0.5

Expected
-------------
Cluster should be disabled by allocator after threshold value

Actual
-----------
Allocator is not disabling cluster 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

Mime
View raw message