Suresh Kumar Anaparti created CLOUDSTACK-9175:
-------------------------------------------------
Summary: [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
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 CCP 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 CCP.
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 CCP 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)
