whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help with cloud provider configuration
Date Sun, 05 Jun 2011 21:31:47 GMT

     [ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrei Savu updated WHIRR-326:
------------------------------

    Attachment: WHIRR-326.patch

First iteration on this. I've noticed that we should add jclouds-allcompute as a dependency
so that Whirr could (in theory) work with all the cloud providers supported by jclouds. 

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

Mime
View raw message