GitHub user Katana-Steel opened a pull request:

    https://github.com/apache/libcloud/pull/809

    Libvirt/include sasl auth

    ## include sasl auth to libvirt_driver
    
    ### Description
    
    Adding SASL authentication to QEMU+tcp remote connections
    
    ### Status
    
    - work in progress
    
    ### Checklist (tick everything that applies)
    
    - [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Katana-Steel/libcloud 
libvirt/include_sasl_auth

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/809.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 #809
    
----
commit c3fc08c40ea87aa0a78b0b885924d6a1be1b9964
Author: Rene Kjellerup <rkjelle...@touchcommerce.com>
Date:   2016-05-16T20:07:40Z

    [LIBCLOUD-820] added check if libvirt uri is local
    
    without this listing nodes on a remote KVM server will fail to
    lookup the IPs in the arp cache

commit caa3c9c9c82e8b03c154579d708b20e05411d05f
Author: Rene Kjellerup <rkjelle...@touchcommerce.com>
Date:   2016-06-09T06:53:10Z

    Libvirt include sasl authentication setup
    
    inlude sasl auth for uri='qemu+tcp://<host>/system' to provide
    access to remote libvirtd servers providing user and pass
    authentication.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to