[
https://issues.apache.org/jira/browse/LIBCLOUD-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635594#comment-13635594
]
Jed Smith commented on LIBCLOUD-313:
------------------------------------
The big downfall here is that you're adding the overhead of a single API call
every time the driver is instantiated for, ultimately, what amounts to static
data. That data hadn't changed since I added it in 2010, but I agree that it
breaking is kind of lame; I noticed the NextGen announcement and had it on my
list, but it was broken during that time.
Perhaps this overhead isn't as big as I'm letting on and it's the right thing
to do. The patch looks fine to me, and I'd +1 merging it.
> Incorrect plan ids at linode driver
> -----------------------------------
>
> Key: LIBCLOUD-313
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-313
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Affects Versions: 0.12.3
> Reporter: Juan Carlos Moreno
> Assignee: Jed Smith
> Priority: Minor
> Attachments: linode_plans.diff
>
>
> Incorrect plan ids at linode driver:
> Replace common/linode.py constant LINODE_PLAN_IDS by updated plan ids from
> function. Currently there are no plan 512 or 768 at LINODE, and plan id 3
> Returns 1024 plan, but now is 2048
> see commit at:
> https://github.com/apache/libcloud/pull/100
> PD: I'm working at loadbalancer linode driver too, hope to push it in a few
> days... :)
--
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
