GitHub user micafer reopened a pull request:

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

    Add OpenStackIdentity_2_0_Connection_VOMS class to manage auth with VOMS 
proxy files

    ## Add OpenStackIdentity_2_0_Connection_VOMS class to manage auth with VOMS 
proxy files
    ### Description
    
    The class OpenStackIdentity_2_0_Connection_VOMS has been added to enable 
OpenStack driver to manage VOMS proxy files to get access to an OpenStack site.
    
    https://keystone-voms.readthedocs.io/en/stable-mitaka/
    
    ### Status
    - done, ready for review
    ### 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
    - [x] [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/indigo-dc/libcloud openstack_voms

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

    https://github.com/apache/libcloud/pull/959.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 #959
    
----
commit ec125bffd07f925083dce81fb1b1768f862e8723
Author: micafer <[email protected]>
Date:   2016-12-14T11:38:35Z

    Add OpenStackIdentity_2_0_Connection_VOMS class

commit 80b54cbe225feb81e07ff09f7ae324a07a09ebe2
Author: micafer <[email protected]>
Date:   2016-12-14T12:35:24Z

    Style changes

commit d551369367890477e37ec88a307cf1634b4be024
Author: micafer <[email protected]>
Date:   2016-12-16T08:04:26Z

    Enable to search for the tenant name if not specified

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to