libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lrvan <>
Subject [GitHub] libcloud pull request #936: [LIBCLOUD-869] Implement get methods for AWS ALB...
Date Tue, 01 Nov 2016 15:47:47 GMT
GitHub user lrvan opened a pull request:

    [LIBCLOUD-869] Implement get methods for AWS ALB driver

    ## AWS ALB Driver - get methods.
    ### Description
    AWS has introduced new type of load balancer - Application Load Balancer (ALB).
    It's supported in APIv2 (2015-12-01) whereas current libcloud AWS load balancer driver
implementation works with APIv1 (2012-06-01). API versions aren't compatible - it's impossible
to operate with classic load balancer (ELB) using v2 API and vice versa. So separate driver
for ALB needs to be implemented.
    This change implements Provider.ALB driver with basic read functionality provided by the
following methods:
    - list_balancers;
    - get_balancer;
    - balancer_list_members;
    - ex_balancer_list_listeners.
    ### Status
    done, ready for review
    ### Checklist (tick everything that applies)
    - [ ] [Code linting](
(required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](
    - [ ] [ICLA](
(required for bigger changes)

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

    $ git pull LIBCLOUD-869

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #936
commit c53331f60094c8600e29b6e145cf3216abb218cf
Author: Anton Kozyrev <>
Date:   2016-10-28T13:58:58Z

    [LIBCLOUD-869] - AWS ALB driver with basic get methods

commit fc883f8f451eb58df18354dbf4f0b2cef45a2fbe
Author: Anton Kozyrev <>
Date:   2016-11-01T15:35:26Z

    [LIBCLOUD-869] - AWS ALB driver tests for get methods


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

View raw message