[
https://issues.apache.org/jira/browse/LIBCLOUD-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637921#comment-13637921
]
robert commented on LIBCLOUD-316:
---------------------------------
I have a workaround for the time being which is fine, however, my concern would
be that with the hard-coding, should the Service Provider bring a new dc
online, that your code release cycle will not provide the user community access
to it as and when that datacenter comes online, without modifying the code
locally or taking an unstable release of libcloud. Both solutions have their
own problems.
If the concern is latency in the constructor then a possible solution, might be
to provide the default datacenter listing via a configuration file, with code
in the driver to allow for query/update of that information.
> Add list_locations method to joyent driver
> ------------------------------------------
>
> Key: LIBCLOUD-316
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-316
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: robert
> Priority: Trivial
> Labels: features
>
> Currently the locations are hardcoded as a string array in the joyent driver.
> Would like to see a list_locations method as part of the class which returns
> those locations.
> Ultimately these items should be updated via a query to the joyent cloud,
> understand there may be reasons for not doing so.
--
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
