whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-326) Use jclouds provider metadata to help with cloud provider configuration
Date Mon, 06 Jun 2011 04:51:47 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044711#comment-13044711

Tom White commented on WHIRR-326:

> we should add jclouds-allcompute


Regarding the patch, the output showing the whirr properties to set might be indented, and
the provider names quoted in some way (e.g. <like this>). It would also be useful to
have a link to the provider's home page, and the provider's full name, if it's available.

We should also cover this feature in the configuration guide.

> 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
>         Attachments: 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

View raw message