Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Hyper-V cluster #260

Open
fabioteixei opened this issue Apr 23, 2024 · 1 comment
Open

Support for Hyper-V cluster #260

fabioteixei opened this issue Apr 23, 2024 · 1 comment

Comments

@fabioteixei
Copy link

Hello,

I’m using a provider with standalone Hyper-V servers and it’s working fine. However, I’m experiencing some issues when I try to use it with a clustered Hyper-V server.

In the provider configuration, I’ve entered the Fully Qualified Domain Name (FQDN) of my cluster instead of the FQDN of the standalone server. The provider can communicate with the server, but due to the round-robin DNS setup for the cluster FQDN, the provider ends up connecting to different Hyper-V servers instead of the cluster itself.

This leads to a situation where sometimes the provider is unable to locate a Virtual Machine (VM) on the server. This is because the VM is running on a different server in the cluster, not on the server that the provider is currently connected to.

I’m not sure how to resolve this. Is there a way to provide a list of servers to the provider instead of just one? This way, I could include all the servers in the cluster in this list, and the provider would attempt to fetch data from all servers instead of just one in the cluster.

Thank you.

@ashkraba
Copy link

Is interesting for me too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants