GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/1248
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_VMwareDRSIssue
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1248.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 #1248
----
commit c22ce365936ac08e28527d9192277d8768ecabfa
Author: Suresh Kumar Anaparti <[email protected]>
Date: 2015-09-21T14:27:03Z
CLOUDSTACK-7151: Support multiple physical networks at cluster level for
guest traffic over VMware deployments.
commit 0d51865f0f7d679d068dd510e00e431ba02c36d8
Author: Suresh Kumar Anaparti <[email protected]>
Date: 2015-12-15T11:48:31Z
Revert "CLOUDSTACK-7151: Support multiple physical networks at cluster
level for guest traffic over VMware deployments."
This reverts commit c22ce365936ac08e28527d9192277d8768ecabfa.
commit 2bdb194783284cdf9bdd067f8e757e913151029f
Author: Suresh Kumar Anaparti <[email protected]>
Date: 2015-12-15T12:13:53Z
Merge branch 'master' of https://github.com/sureshanaparti/cloudstack
commit d3c3f498d19ae623e6b658627087cfc2ec734e67
Author: Suresh Kumar Anaparti <[email protected]>
Date: 2015-12-16T10:29:14Z
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.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
