[
https://issues.apache.org/jira/browse/LIBCLOUD-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540453#comment-13540453
]
John Carr commented on LIBCLOUD-169:
------------------------------------
I didn't see this ticket and have also started work on this. My progress (and
it is still in progress) is here:
https://github.com/Jc2k/libcloud/compare/elb
(I have still to add tests and remove some code duplication with other amazon
drivers).
There are some interface violations I need help with:
1. balance_attach_member is not supported by aws, only
balance_attach_compute_node
2. A backend cannot be given a particular port. Rather the backend port has to
be passed to the LoadBalancer when it is created at the same time as the front
end port. To clarify, on other providers you might have a LB on port 80 that
directs traffic to 8081 on host a and 9081 on host b. On ELB, you have to pass
the 8081 to the load balancer when you create it and you can then only use 8081.
> Add AWS elastic loadbalancer support to libcloud
> ------------------------------------------------
>
> Key: LIBCLOUD-169
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-169
> Project: Libcloud
> Issue Type: New Feature
> Affects Versions: 0.8.0
> Environment: N/A
> Reporter: Suvish V.T.
> Labels: aws, libcloud, loadbalancer
> Fix For: 0.8.0
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Aims to add ELB support for libcloud.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
