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-9175) [VMware DRS] Adding new host to DRS cluster does not participate in load balancing
Date Thu, 17 Dec 2015 18:52:46 GMT

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

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

GitHub user sureshanaparti opened a pull request:

    https://github.com/apache/cloudstack/pull/1257

    CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not participate in load
balancing.

    Summary: When a new host is added to a cluster, Cloudstack doesn't create all the port
groups (created by cloudstack earlier in other hosts) present in the cluster. Since the new
host doesn't have all the necessary networking port groups of cloudstack, it is not eligible
to participate in DRS load balancing or HA.
    Solution: When adding a host to the cluster in Cloudstack, use VMware API to find the
list of unique port groups on a previously added host (older host in the cluster) if exists
and then create them on the new host.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9175

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1257.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 #1257
    
----
commit 9091829ed9423fbb4db4202bcdfc379003b3a082
Author: Suresh Kumar Anaparti <sureshkumar.anaparti@citrix.com>
Date:   2015-12-17T18:47:38Z

    CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not participate in load
balancing.
    
    Summary: When a new host is added to a cluster, Cloudstack doesn't create all the port
groups (created by cloudstack earlier in other hosts) present in the cluster. Since the new
host doesn't have all the necessary networking port groups of cloudstack, it is not eligible
to participate in DRS load balancing or HA.
    Solution: When adding a host to the cluster in Cloudstack, use VMware API to find the
list of unique port groups on a previously added host (older host in the cluster) if exists
and then create them on the new host.

----


> [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)

Mime
View raw message