[
https://issues.apache.org/jira/browse/LIBCLOUD-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789149#comment-13789149
]
ASF subversion and git services commented on LIBCLOUD-407:
----------------------------------------------------------
Commit d11a513b64ca4794f535dd844ae93e30c3c3c659 in branch refs/heads/trunk from
[~briancurtin]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=d11a513 ]
Issue LIBCLOUD-407: Better name for Node drivers
Some classes in libcloud.compute.drivers aren't easily identifiable in
the supported provider matrix due to their name attributes being
generic. This change adds detail to NodeDriver classes where there are
multiple per provider, e.g., Amazon EC2.
Signed-off-by: Tomaz Muraus <[email protected]>
> Better name attributes on some compute node classes
> ---------------------------------------------------
>
> Key: LIBCLOUD-407
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-407
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Reporter: Brian Curtin
> Priority: Minor
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> I noticed that the
> https://ci.apache.org/projects/libcloud/docs/compute/supported_providers.html
> page shows many providers more than once, but doesn't identify what makes
> them different. For example, "Amazon EC2" shows up a ton, but it doesn't
> identify what region. Same for Rackspace not identifying first gen or next
> gen, etc. The supported provider matrices for other packages doesn't have
> this problem because the relevant classes have that extra info.
> The fix would be to have better `name` attributes on the NodeDriver classes.
> If that's reasonable, I can put together the patch.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
