Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 17 Dec 2015 10:29:46 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12922271.1450250260000.52900.1450348186676@Atlassian.JIRA>
In-Reply-To: <JIRA.12922271.1450250260000@Atlassian.JIRA>
References: <JIRA.12922271.1450250260000@Atlassian.JIRA>
 <JIRA.12922271.1450250260069@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9175) [VMware DRS] Adding new host
 to DRS cluster does not participate in load balancing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user sureshanaparti commented on the pull request:

    https://github.com/apache/cloudstack/pull/1248#issuecomment-165412102
  
    @resmo, You mean findOldestExistentHypervisorHostInCluster. I'm OK with it. 
    Shall I create new PR without all these merges?


> [VMware DRS] Adding new host to DRS cluster does not participate in load balancing
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9175
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9175
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, VMware
>    Affects Versions: 4.5.2
>            Reporter: Suresh Kumar Anaparti
>            Assignee: Suresh Kumar Anaparti
>
> When a new VMware host is added into a cluster, Cloudstack, by default, doesn't create all the port groups present in the cluster. And since it doesn't have all the necessary networking port groups (existing VM's port groups) it is not eligible to participate in DRS load balancing or HA.
> Steps:
> 1. Have a DRS and HA cluster in fully automated mode, with two hosts H1 and H2 created in the vCenter.
> 2. Configure this cluster in Cloudstack and create couple of VMs.
> 3. Start stressing the host by running some cpu hogging scripts in each of the VM.
> 4. Enable maintenance mode on one of the host - say H1 from Cloudstack.
> 5. Also, quickly enable maintenance mode on host H1 from vCenter.
> (This should migrate all the VMs to host H2) Make sure none of the VMs are present on host H1.
> 6. Add host H3 into DRS cluster from vCenter and from Cloudstack as well.
> 7. At this point, the load is definitely imbalanced. This can be verified from vCenter ( Click on cluster -> Go to Summary tab -> under vSphere DRS section, it should show 'Load imbalanced'
> Now, as per DRS rules, the load should be balanced across all the available hosts.
> In this case, even after adding new host, the load is imbalanced. 
> The reason for the load imbalance is VMs (created from Cloudstack) are not eligible to migrate to new host because networks or the cloud portgroups are not available on the new host H3 (except for private).


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