cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9650) Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting
Date Fri, 30 Dec 2016 13:44:58 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9650:
--------------------------------------------

Github user cloudmonger commented on the issue:

    https://github.com/apache/cloudstack/pull/1812
  
    ### ACS CI BVT Run
     **Sumarry:**
     Build Number 202
     Hypervisor xenserver
     NetworkType Advanced
     Passed=98
     Failed=7
     Skipped=7
    
    _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
    
    
    **Failed tests:**
    * test_snapshots.py
    
     * test_01_snapshot_root_disk Failing since 9 runs
    
    * test_deploy_vm_iso.py
    
     * test_deploy_vm_from_iso Failing since 33 runs
    
    * test_nic.py
    
     * test_01_nic Failed
    
    * test_vm_life_cycle.py
    
     * test_10_attachAndDetach_iso Failing since 34 runs
    
    * test_routers_network_ops.py
    
     * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failing since 2 runs
    
     * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 2 runs
    
     * test_03_RVR_Network_check_router_state Failing since 2 runs
    
    
    **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_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_deploy_vm_root_resize.py
    test_resource_detail.py
    test_secondary_storage.py
    test_disk_offerings.py


> Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9650
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9650
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.10.0.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.10.1.0
>
>
> VM deployments are not allowed on clusters where resource (cpu/memory) allocation has
exceeded the cluster disabled thresholds. The same policy also gets applied in case of start
VM if last host where the VM was running doesn't have enough capacity and a new host is picked
up. In certain scenarios this can be restrictive and despite having capacity, the VM cannot
be started.
> This improvement is to provide administrator an option to disable/enable cluster threshold
enforcement during start of a stopped VM as long as sufficient capacity is available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message