[jira] [Commented] (CLOUDSTACK-9703) Start VM does not honor cluster.cpu.allocated.capacity.disablethreshold if the vm is startting on last host

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865056#comment-15865056
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9703:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1860
  
 ### ACS CI BVT Run
 **Sumarry:**
 Build Number 320
 Hypervisor xenserver
 NetworkType Advanced
 Passed=104
 Failed=0
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_routers_network_ops.py
test_disk_offerings.py


> 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.15#6346)

[jira] [Commented] (CLOUDSTACK-9703) Start VM does not honor cluster.cpu.allocated.capacity.disablethreshold if the vm is startting on last host

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
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)