[
https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046349#comment-13046349
]
Tom White commented on WHIRR-326:
---------------------------------
+1 Looks good. Thanks for making the changes. One minor thing - I would have
the configuration options grouped under the same heading as the other settings.
E.g.
{noformat}
* Rackspace Cloud Servers US - tested
Homepage: http://www.rackspace.com/cloud/cloud_hosting_products/servers
Console: https://manage.rackspacecloud.com
API:
http://docs.rackspacecloud.com/servers/api/v1.0/cs-devguide/content/ch01.html
Configuration options:
whirr.provider = cloudservers-us
whirr.identity = <Username>
whirr.credential = <API Key>
{noformat}
> Use jclouds provider metadata to help with cloud provider configuration
> -----------------------------------------------------------------------
>
> Key: WHIRR-326
> URL: https://issues.apache.org/jira/browse/WHIRR-326
> Project: Whirr
> Issue Type: New Feature
> Components: cli
> Reporter: Tom White
> Assignee: Andrei Savu
> Fix For: 0.6.0
>
> Attachments: WHIRR-326.patch, WHIRR-326.patch
>
>
> The new ProviderMetadata class in jclouds 1.0.0 allows discovery of metadata
> for all supported providers. We could use this in the CLI to list the
> provider IDs and name of the credential to supply for Whirr. We could also
> have a list of providers we've tested with Whirr so this is shown to the user
> too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
