libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-407) Better name attributes on some compute node classes
Date Mon, 07 Oct 2013 18:07:44 GMT

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

Tomaz Muraus commented on LIBCLOUD-407:
---------------------------------------

Yeah I agree, current provider matrix table is not ideal.

This is especially true for EC2 and Rackspace driver in trunk which use "region" argument
in favor of "class per region" model.

Once this "region" argument changes are released we will probably need to add some more metadata
to the driver (which region it supports) and include this information in the table.

For existing drivers and now, updating "name" attribute seems reasonable so feel free to make
this change.

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

Mime
View raw message