CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not participate in load balancing.#1248
Conversation
…for guest traffic over VMware deployments.
…r level for guest traffic over VMware deployments." This reverts commit c22ce36.
… 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.
|
|
|
@resmo, Out of all the running hosts present in the cluster, the port groups are fetched from the host which was first added to the cloudstack, assuming that it has all the cloudstack created port groups. So existent may not be the right word. Any other? |
|
@sureshanaparti Ok, I see. then I would indeed use old but suggest |
|
@resmo, You mean findOldestExistentHypervisorHostInCluster. I'm OK with it. |
|
@sureshanaparti that would be great. appreciate your work on vmware parts! |
|
@resmo Sure. I'll do that. Thanks. |
|
since #1257 replaces this PR I would do so, yes. |
|
@resmo ok sure. thanks! |
|
@sureshanaparti yes, that would be great |
|
@sureshanaparti can you rebase against latest master and share state of your PR, thanks; squash all changes into a single commit tag:vmware-pickup |
ACS CI BVT RunSumarry: Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 Failed tests: Skipped tests: Passed test suits: |
|
This PR is no longer valid since #1257 replaces this. Closing... |
4 participants
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.