cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anshul Gangwar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-9703) Start VM does not honor cluster.cpu.allocated.capacity.disablethreshold if the vm is startting on last host
Date Fri, 23 Dec 2016 10:41:58 GMT
Anshul Gangwar created CLOUDSTACK-9703:
------------------------------------------

             Summary: 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)

Mime
View raw message