You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2014/05/29 08:59:01 UTC

[jira] [Commented] (LIBCLOUD-567) Openstack driver returns a 404 when listing pool of available ips for HPcloud

    [ https://issues.apache.org/jira/browse/LIBCLOUD-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012135#comment-14012135 ] 

Tomaz Muraus commented on LIBCLOUD-567:
---------------------------------------

This pull request resolved this recently - https://github.com/apache/libcloud/pull/301

I do agree that shoving all the extension methods on the base driver is not ideal. I think we should use a mixin model. We define `OpenStackFloatingIPsMixin` which defines this functionality and then we have HP Cloud driver also inherit from this mixin.

> Openstack driver returns a 404 when listing pool of available ips for HPcloud
> -----------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-567
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-567
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.14.0-beta3
>            Reporter: Jesus Zambrano
>
> Resource request here:
> https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/openstack.py#L2169
> returns a 404 for HPCloud.
> It should be:
> {code}/os-floating-ips{code} instead of {code}/os-floating-ip-pools{code} according to the hpcloud docs found here:
> https://docs.hpcloud.com/api/v13/compute/#listFloatingIPs
> Should {noformat} ex_list_floating_ip_pools {noformat} be implemented in the hpcloud driver instead?
> https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/hpcloud.py



--
This message was sent by Atlassian JIRA
(v6.2#6252)