Libvirt/include sasl auth#809
Closed
Katana-Steel wants to merge 3 commits into
Closed
Conversation
4b4bf8d to
3adf5f6
Compare
Member
|
Awesome, thanks. I will look into it ASAP. |
inlude sasl auth for uri='qemu+tcp://<host>/system' to provide access to remote libvirtd servers providing user and pass authentication.
3adf5f6 to
498d45f
Compare
updated the constructor documentation and added description for the callback function.
| except libvirt.libvirtError: | ||
| if key is None or secret is None: | ||
| raise RuntimeError('The remote Libvirt instance requires ' + | ||
| 'authenication, please set \'key\' and ' + |
Contributor
|
👍 |
asfgit
pushed a commit
that referenced
this pull request
Jun 24, 2016
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
include sasl auth to libvirt_driver
Description
Adding SASL authentication to QEMU+tcp remote connections
Because this really annoyed me. We have about +100 KVM servers and I'd
just to iterate over them and get all the available nodes. Apply a few filters
and then return a list of nodes where the end user don't need to worry about
which KVM host his VM is running on and just be able to reboot it should he
need to.
Status
Checklist (tick everything that applies)