Mailing-List: contact dev-help@libcloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@libcloud.apache.org
Date: Thu, 21 Mar 2013 19:19:16 +0000 (UTC)
From: "Chris Psaltis (JIRA)" <jira@apache.org>
To: dev@libcloud.apache.org
Message-ID: <JIRA.12636817.1363197244353.29202.1363893556328@arcas>
In-Reply-To: <JIRA.12636817.1363197244353@arcas>
References: <JIRA.12636817.1363197244353@arcas>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: [dev] [jira] [Commented] (LIBCLOUD-305) list_locations() for new
 Rackspace provider


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

Chris Psaltis commented on LIBCLOUD-305:
----------------------------------------

I see it as a uniformity issue. For example in RACKSPACE_FIRST_GEN, LINODE and EC2 drivers you can always do list_locations() and get a meaningful answer, even if there is only one location as in the case of RACKSPACE_FIRST_GEN. In the RACKSPACE_NOVA_* drivers list_locations() gets you a NodeLocation object containing only the driver name which is common on all RACKSPACE_* drivers. It is true that RACKSPACE_NOVA_* drivers have only one location/datacenter, but wouldn't be useful to return it with list_locations() so the interface is the same in all cases?
                
> list_locations() for new Rackspace provider
> -------------------------------------------
>
>                 Key: LIBCLOUD-305
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-305
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>            Reporter: Chris Psaltis
>            Priority: Minor
>         Attachments: rackspace_list_locations.patch
>
>
> For the RACKSPACE_FIRST_GEN it is already there. For RACKSPACE it returns an empty NodeLocation object. Will post a patch imitating what is already there really soon.

--
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