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 communicating with Xen API over TLS (#85) #86

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

chqr
Copy link

@chqr chqr commented Jul 5, 2017

This commit adds two new config flags:

  • remote_url: url to use when connecting to the Xen API (defaults to http://{remote_host})
  • remote_url_tls_skip_verify: disables certificate verification for remote_url

I've added the second option because we are using self-signed certs on some of our our Xen servers (there are plans to fix this soon), but it could also be useful for others during testing/evaluation.

@chqr chqr changed the title #85 Support communicating with Xen API over TLS Support communicating with Xen API over TLS #85 Jul 5, 2017
@chqr chqr changed the title Support communicating with Xen API over TLS #85 Support communicating with Xen API over TLS (#85) Jul 5, 2017
@rdobson
Copy link
Contributor

rdobson commented Oct 18, 2017

@chqr - thanks for the PR.

Rather than make the user specify the full URL, do you not just need to be able to configure between using HTTP/HTTPS? I think having a protocol value default to HTTP which can be overiden might be nice from a config perspective. What do you think?

@chqr
Copy link
Author

chqr commented Oct 20, 2017

@rdobson You are right, since there is existing configuration option called remote_host, remote_protocol probably makes more sense

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

Successfully merging this pull request may close these issues.

2 participants