GitHub user watermelo opened a pull request:

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

    Implement security group egress and ingress method

    ## Implement security group egress and ingress method
    
    ### Description
    1, Implement security group egress and ingress method
    2, Provide unit test cases.
    
    ### Status
    
    - done, ready for review
    
    ### Checklist (tick everything that applies)
    
    - [ ] [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/watermelo/libcloud trunk

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

    https://github.com/apache/libcloud/pull/948.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 #948
    
----
commit 4412392d494ba2bb5aceaf02a464df1df52a09c9
Author: hequn <[email protected]>
Date:   2016-11-16T01:38:39Z

    Merge branch 'upstream' into trunk

commit ef7a9f8c3ec13bb6a47ee3cb252da603e5ff3593
Author: hequn <[email protected]>
Date:   2016-11-18T05:38:22Z

    Merge branch 'upstream' into trunk

commit 4ec7b97cdcdcc68f35cbde3bfedc66e3cf256cf1
Author: hequn <[email protected]>
Date:   2016-11-18T07:16:57Z

    Implement some security group methods
    
    1, Implement security group egress and ingress methods
    2, Provide unit test cases

----


---
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