You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Dave King (Created) (JIRA)" <ji...@apache.org> on 2012/01/05 17:25:39 UTC
[dev] [jira] [Created] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Rackspace LB Driver: Update Configuration Options
-------------------------------------------------
Key: LIBCLOUD-140
URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
Project: Libcloud
Issue Type: Improvement
Affects Versions: 0.7.1
Reporter: Dave King
Priority: Minor
Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Posted by "Dave King (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181317#comment-13181317 ]
Dave King commented on LIBCLOUD-140:
------------------------------------
Just attached a first attempt at a patch (libcloud-140-attempt-1.patch). This exposes most of the updates and deletes in the LB API.
New functions:
* ex_destroy_balancers(self, balancers):
* ex_balancer_detach_members(self, balancer, members):
* ex_balancer_detach_members_no_poll(self, balancer, members):
* ex_balancer_update_member(self, balancer, member, **kwargs):
* ex_balancer_update_member_no_poll(self, balancer, member, **kwargs):
* ex_update_balancer_health_monitor(self, balancer, health_monitor):
* ex_update_balancer_health_monitor_no_poll(self, balancer,
* ex_disable_balancer_health_monitor(self, balancer):
* ex_disable_balancer_health_monitor_no_poll(self, balancer):
* ex_update_balancer_connection_throttle(self, balancer,
* ex_update_balancer_connection_throttle_no_poll(self, balancer,
* ex_disable_balancer_connection_throttle(self, balancer):
* ex_disable_balancer_connection_throttle_no_poll(self, balancer):
* ex_enable_balancer_connection_logging(self, balancer):
* ex_enable_balancer_connection_logging_no_poll(self, balancer):
* ex_disable_balancer_connection_logging(self, balancer):
* ex_disable_balancer_connection_logging_no_poll(self, balancer):
* ex_enable_balancer_session_persistence(self, balancer):
* ex_enable_balancer_session_persistence_no_poll(self, balancer):
* ex_disable_balancer_session_persistence(self, balancer):
* ex_disable_balancer_session_persistence_no_poll(self, balancer):
* ex_update_balancer_error_page(self, balancer, page_content):
* ex_update_balancer_error_page_no_poll(self, balancer, page_content):
* ex_disable_balancer_custom_error_page(self, balancer):
* ex_disable_balancer_custom_error_page_no_poll(self, balancer):
* ex_create_balancer_access_rule(self, balancer, rule):
* ex_create_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rule(self, balancer, rule):
* ex_destroy_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rules(self, balancer, rules):
* ex_destroy_balancer_access_rules_no_poll(self, balancer, rules):
This defaults all update/disables to polling the Load Balancer until it returns to RUNNING state, as that's what was done for the recent update_balancer function.
I'm a little concerned: currently old functions like attach_members won't poll until the Load Balancer is finished. Should these be changed to match these new code patterns as well? (Doing the polling client side seems kind of a pain.)
--
I added accessList to a Load Balancer 'extra's as I noticed it was being returned with the full detials. (This has either changed since I implemented most of the 'extra' work or I just missed it the first time.)
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Attachment: libcloud-140-attempt-1.patch
First attempt to address this.
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Dave King (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182518#comment-13182518 ]
Dave King commented on LIBCLOUD-140:
------------------------------------
Updated patch with changes.
Sorry about missing pydoc, I'll be more careful about that in the future.
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch, libcloud-140-attempt-4.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Issue Comment Edited] (LIBCLOUD-140) Rackspace LB Driver:
Update Configuration Options
Posted by "Dave King (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181317#comment-13181317 ]
Dave King edited comment on LIBCLOUD-140 at 1/6/12 1:32 PM:
------------------------------------------------------------
Just attached a first attempt at a patch (libcloud-140-attempt-2.patch -- ignore attempt-1, that's a git am patch). This exposes most of the updates and deletes in the LB API.
New functions:
* ex_destroy_balancers(self, balancers):
* ex_balancer_detach_members(self, balancer, members):
* ex_balancer_detach_members_no_poll(self, balancer, members):
* ex_balancer_update_member(self, balancer, member, **kwargs):
* ex_balancer_update_member_no_poll(self, balancer, member, **kwargs):
* ex_update_balancer_health_monitor(self, balancer, health_monitor):
* ex_update_balancer_health_monitor_no_poll(self, balancer,
* ex_disable_balancer_health_monitor(self, balancer):
* ex_disable_balancer_health_monitor_no_poll(self, balancer):
* ex_update_balancer_connection_throttle(self, balancer,
* ex_update_balancer_connection_throttle_no_poll(self, balancer,
* ex_disable_balancer_connection_throttle(self, balancer):
* ex_disable_balancer_connection_throttle_no_poll(self, balancer):
* ex_enable_balancer_connection_logging(self, balancer):
* ex_enable_balancer_connection_logging_no_poll(self, balancer):
* ex_disable_balancer_connection_logging(self, balancer):
* ex_disable_balancer_connection_logging_no_poll(self, balancer):
* ex_enable_balancer_session_persistence(self, balancer):
* ex_enable_balancer_session_persistence_no_poll(self, balancer):
* ex_disable_balancer_session_persistence(self, balancer):
* ex_disable_balancer_session_persistence_no_poll(self, balancer):
* ex_update_balancer_error_page(self, balancer, page_content):
* ex_update_balancer_error_page_no_poll(self, balancer, page_content):
* ex_disable_balancer_custom_error_page(self, balancer):
* ex_disable_balancer_custom_error_page_no_poll(self, balancer):
* ex_create_balancer_access_rule(self, balancer, rule):
* ex_create_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rule(self, balancer, rule):
* ex_destroy_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rules(self, balancer, rules):
* ex_destroy_balancer_access_rules_no_poll(self, balancer, rules):
This defaults all update/disables to polling the Load Balancer until it returns to RUNNING state, as that's what was done for the recent update_balancer function.
I'm a little concerned: currently old functions like attach_members won't poll until the Load Balancer is finished. Should these be changed to match these new code patterns as well? (Doing the polling client side seems kind of a pain.)
--
I added accessList to a Load Balancer 'extra's as I noticed it was being returned with the full details. (This has either changed since I implemented most of the 'extra' work or I just missed it the first time.)
The fixture changes were to make the returned ids in the fixtures consistent with the ids used MockHttp fixture (I messed this up when adding them.)
was (Author: tildedave):
Just attached a first attempt at a patch (libcloud-140-attempt-2.patch -- ignore attempt-1, that's a git am patch). This exposes most of the updates and deletes in the LB API.
New functions:
* ex_destroy_balancers(self, balancers):
* ex_balancer_detach_members(self, balancer, members):
* ex_balancer_detach_members_no_poll(self, balancer, members):
* ex_balancer_update_member(self, balancer, member, **kwargs):
* ex_balancer_update_member_no_poll(self, balancer, member, **kwargs):
* ex_update_balancer_health_monitor(self, balancer, health_monitor):
* ex_update_balancer_health_monitor_no_poll(self, balancer,
* ex_disable_balancer_health_monitor(self, balancer):
* ex_disable_balancer_health_monitor_no_poll(self, balancer):
* ex_update_balancer_connection_throttle(self, balancer,
* ex_update_balancer_connection_throttle_no_poll(self, balancer,
* ex_disable_balancer_connection_throttle(self, balancer):
* ex_disable_balancer_connection_throttle_no_poll(self, balancer):
* ex_enable_balancer_connection_logging(self, balancer):
* ex_enable_balancer_connection_logging_no_poll(self, balancer):
* ex_disable_balancer_connection_logging(self, balancer):
* ex_disable_balancer_connection_logging_no_poll(self, balancer):
* ex_enable_balancer_session_persistence(self, balancer):
* ex_enable_balancer_session_persistence_no_poll(self, balancer):
* ex_disable_balancer_session_persistence(self, balancer):
* ex_disable_balancer_session_persistence_no_poll(self, balancer):
* ex_update_balancer_error_page(self, balancer, page_content):
* ex_update_balancer_error_page_no_poll(self, balancer, page_content):
* ex_disable_balancer_custom_error_page(self, balancer):
* ex_disable_balancer_custom_error_page_no_poll(self, balancer):
* ex_create_balancer_access_rule(self, balancer, rule):
* ex_create_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rule(self, balancer, rule):
* ex_destroy_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rules(self, balancer, rules):
* ex_destroy_balancer_access_rules_no_poll(self, balancer, rules):
This defaults all update/disables to polling the Load Balancer until it returns to RUNNING state, as that's what was done for the recent update_balancer function.
I'm a little concerned: currently old functions like attach_members won't poll until the Load Balancer is finished. Should these be changed to match these new code patterns as well? (Doing the polling client side seems kind of a pain.)
--
I added accessList to a Load Balancer 'extra's as I noticed it was being returned with the full detials. (This has either changed since I implemented most of the 'extra' work or I just missed it the first time.)
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Posted by "Dave King (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180505#comment-13180505 ]
Dave King commented on LIBCLOUD-140:
------------------------------------
For a first attempt I am going to add functions to the driver like:
* ex_balancer_disable_connection_throttle
* ex_balancer_disable_connection_throttle_no_poll
* ex_balancer_update_connection_throttle
* ex_balancer_update_connection_throttle_no_poll
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Attachment: libcloud-140-attempt-2.patch
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Attachment: libcloud-140-attempt-4.patch
grant rights to apache
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch, libcloud-140-attempt-4.patch, libcloud-140-attempt-4.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Comment: was deleted
(was: First attempt to address this.)
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Attachment: libcloud-140-attempt-3.patch
remove trailing slash from bulk accesslist deletes.
this call is currently not working in the API (202 accepted but nothing gets deleted). I've filed a bug with the Cloud Load Balancer team about this.
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Issue Comment Edited] (LIBCLOUD-140) Rackspace LB Driver:
Update Configuration Options
Posted by "Dave King (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181317#comment-13181317 ]
Dave King edited comment on LIBCLOUD-140 at 1/6/12 1:31 PM:
------------------------------------------------------------
Just attached a first attempt at a patch (libcloud-140-attempt-2.patch -- ignore attempt-1, that's a git am patch). This exposes most of the updates and deletes in the LB API.
New functions:
* ex_destroy_balancers(self, balancers):
* ex_balancer_detach_members(self, balancer, members):
* ex_balancer_detach_members_no_poll(self, balancer, members):
* ex_balancer_update_member(self, balancer, member, **kwargs):
* ex_balancer_update_member_no_poll(self, balancer, member, **kwargs):
* ex_update_balancer_health_monitor(self, balancer, health_monitor):
* ex_update_balancer_health_monitor_no_poll(self, balancer,
* ex_disable_balancer_health_monitor(self, balancer):
* ex_disable_balancer_health_monitor_no_poll(self, balancer):
* ex_update_balancer_connection_throttle(self, balancer,
* ex_update_balancer_connection_throttle_no_poll(self, balancer,
* ex_disable_balancer_connection_throttle(self, balancer):
* ex_disable_balancer_connection_throttle_no_poll(self, balancer):
* ex_enable_balancer_connection_logging(self, balancer):
* ex_enable_balancer_connection_logging_no_poll(self, balancer):
* ex_disable_balancer_connection_logging(self, balancer):
* ex_disable_balancer_connection_logging_no_poll(self, balancer):
* ex_enable_balancer_session_persistence(self, balancer):
* ex_enable_balancer_session_persistence_no_poll(self, balancer):
* ex_disable_balancer_session_persistence(self, balancer):
* ex_disable_balancer_session_persistence_no_poll(self, balancer):
* ex_update_balancer_error_page(self, balancer, page_content):
* ex_update_balancer_error_page_no_poll(self, balancer, page_content):
* ex_disable_balancer_custom_error_page(self, balancer):
* ex_disable_balancer_custom_error_page_no_poll(self, balancer):
* ex_create_balancer_access_rule(self, balancer, rule):
* ex_create_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rule(self, balancer, rule):
* ex_destroy_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rules(self, balancer, rules):
* ex_destroy_balancer_access_rules_no_poll(self, balancer, rules):
This defaults all update/disables to polling the Load Balancer until it returns to RUNNING state, as that's what was done for the recent update_balancer function.
I'm a little concerned: currently old functions like attach_members won't poll until the Load Balancer is finished. Should these be changed to match these new code patterns as well? (Doing the polling client side seems kind of a pain.)
--
I added accessList to a Load Balancer 'extra's as I noticed it was being returned with the full detials. (This has either changed since I implemented most of the 'extra' work or I just missed it the first time.)
was (Author: tildedave):
Just attached a first attempt at a patch (libcloud-140-attempt-1.patch). This exposes most of the updates and deletes in the LB API.
New functions:
* ex_destroy_balancers(self, balancers):
* ex_balancer_detach_members(self, balancer, members):
* ex_balancer_detach_members_no_poll(self, balancer, members):
* ex_balancer_update_member(self, balancer, member, **kwargs):
* ex_balancer_update_member_no_poll(self, balancer, member, **kwargs):
* ex_update_balancer_health_monitor(self, balancer, health_monitor):
* ex_update_balancer_health_monitor_no_poll(self, balancer,
* ex_disable_balancer_health_monitor(self, balancer):
* ex_disable_balancer_health_monitor_no_poll(self, balancer):
* ex_update_balancer_connection_throttle(self, balancer,
* ex_update_balancer_connection_throttle_no_poll(self, balancer,
* ex_disable_balancer_connection_throttle(self, balancer):
* ex_disable_balancer_connection_throttle_no_poll(self, balancer):
* ex_enable_balancer_connection_logging(self, balancer):
* ex_enable_balancer_connection_logging_no_poll(self, balancer):
* ex_disable_balancer_connection_logging(self, balancer):
* ex_disable_balancer_connection_logging_no_poll(self, balancer):
* ex_enable_balancer_session_persistence(self, balancer):
* ex_enable_balancer_session_persistence_no_poll(self, balancer):
* ex_disable_balancer_session_persistence(self, balancer):
* ex_disable_balancer_session_persistence_no_poll(self, balancer):
* ex_update_balancer_error_page(self, balancer, page_content):
* ex_update_balancer_error_page_no_poll(self, balancer, page_content):
* ex_disable_balancer_custom_error_page(self, balancer):
* ex_disable_balancer_custom_error_page_no_poll(self, balancer):
* ex_create_balancer_access_rule(self, balancer, rule):
* ex_create_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rule(self, balancer, rule):
* ex_destroy_balancer_access_rule_no_poll(self, balancer, rule):
* ex_destroy_balancer_access_rules(self, balancer, rules):
* ex_destroy_balancer_access_rules_no_poll(self, balancer, rules):
This defaults all update/disables to polling the Load Balancer until it returns to RUNNING state, as that's what was done for the recent update_balancer function.
I'm a little concerned: currently old functions like attach_members won't poll until the Load Balancer is finished. Should these be changed to match these new code patterns as well? (Doing the polling client side seems kind of a pain.)
--
I added accessList to a Load Balancer 'extra's as I noticed it was being returned with the full detials. (This has either changed since I implemented most of the 'extra' work or I just missed it the first time.)
> Rackspace LB Driver: Update Configuration Options
> -------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182870#comment-13182870 ]
Tomaz Muraus commented on LIBCLOUD-140:
---------------------------------------
Merged with some modifications:
- use urlencode from libcloud.utils.py otherwise it won't work with python 3.x
Thanks!
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Fix For: 0.8.0
>
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch, libcloud-140-attempt-4.patch, libcloud-140-attempt-4.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Tomaz Muraus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181792#comment-13181792 ]
Tomaz Muraus commented on LIBCLOUD-140:
---------------------------------------
Hey, I just checked the patch and here are a few comments:
- to_dict should be a "private" method for now (prefixed with an underscore)
- RackspaceAccessRule id attribute seems to be an int. In other places ids are string so for consistency we should also stick to strings here
- missing docstrings for new methocs
Otherwise it looks pretty good!
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Attachment: libcloud-140-attempt-4.patch
Updated with changes from feedback. Notably includes pydoc for all new methods.
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch, libcloud-140-attempt-4.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-140:
-------------------------------
Summary: Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes (was: Rackspace LB Driver: Update Configuration Options)
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Resolved] (LIBCLOUD-140) Rackspace LB Driver: Update
Configuration Options/Update Members/Bulk Deletes
Posted by "Tomaz Muraus (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus resolved LIBCLOUD-140.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
> Rackspace LB Driver: Update Configuration Options/Update Members/Bulk Deletes
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-140
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-140
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.7.1
> Reporter: Dave King
> Priority: Minor
> Labels: loadbalancer, rackspace
> Fix For: 0.8.0
>
> Attachments: libcloud-140-attempt-1.patch, libcloud-140-attempt-2.patch, libcloud-140-attempt-3.patch, libcloud-140-attempt-4.patch, libcloud-140-attempt-4.patch
>
>
> Currently the Rackspace Cloud Load Balancer API exposes Health Monitors, Connection Throttle, Connection Logging, Session Persistence, Error Pages, and Access Lists.
> Libcloud should expose these to be updated/disabled (like name, protocol, and port are currently allowed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira