[GitHub] libcloud pull request #856: [GCE] Support for HTTP(S) proxies with BackendSe...

[supertom <gi...@git.apache.org>]

GitHub user supertom opened a pull request:

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

    [GCE] Support for HTTP(S) proxies with BackendServices.

    ## [GCE] Support for HTTP(S) proxies with BackendServices.
    ### Description
    
    HTTP(S) proxies with Backend services are now supported.  Users can now take advantage of creating a global forwarding rule that maps to a Managed Instance Group (via a Backend Service) with these changes.
    
    ### High level flow of creating a forwarding rule:
    
    ```
    be = gce.ex_create_backend(instance_group=ig)
    bes = gce.ex_create_backendservice(
                bes_name, [hc], backends=[be], port_name='my-ssl', protocol='HTTP',
    	                description='bes desc', timeout_sec=60)
    
    urlmap = gce.ex_create_urlmap('myurlmap', bes)
    
    # create cert resources for use with https proxy
    print gce.ex_create_sslcertificate(ssl_name, certificate=certificate, private_key=private_key, description=ssl_desc)
    print gce.ex_list_sslcertificates()
    
    proxy = gce.ex_create_targethttpsproxy(targethttpproxy_name, urlmap, ssl_list)
    print gce.ex_list_targethttpsproxies()
    
    ... create forwarding rule to point to to HTTPS proxy...
    
    ```
    ### 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/supertom/libcloud gce-backend-support

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

    https://github.com/apache/libcloud/pull/856.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 #856
    
----
commit 7d27fcc2b6f959871c877a2551c72f73fbe8bc9f
Author: Tom Melendez <su...@google.com>
Date:   2016-08-25T23:57:27Z

    Added support for HTTP(S) proxies with BackendServices.  Includes support GCEBackendService, GCESslCertificate, GCEBackend, and tests.
    
    High level of what was added:
    
    be = gce.ex_create_backend(instance_group=ig)
    print gce.ex_create_backendservice(
                bes_name, [hc], backends=[be], port_name='my-ssl', protocol='HTTP',
    	                description='bes desc', timeout_sec=60)
    
    ... create URLMap that links to backend service ..
    
    print gce.ex_create_sslcertificate(ssl_name, certificate=certificate, private_key=private_key, description=ssl_desc)
    print gce.ex_list_sslcertificates()
    
    print gce.ex_create_targethttpsproxy(targethttpproxy_name, urlmap, ssl_list)
    print gce.ex_list_targethttpsproxies()
    
    Including modifications to backendservice as needed.  Now, with a forwarding rule, load balancer can be created that resolves to a Managed Instance Group via a Backend Service creation.

----


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

[GitHub] libcloud pull request #856: [GCE] Support for HTTP(S) proxies with BackendSe...

[asfgit <gi...@git.apache.org>]

Github user asfgit closed the pull request at:

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


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