You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/06/03 22:40:47 UTC
[jira] [Created] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
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
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
[jira] [Commented] (WHIRR-326) Use jclouds provider metadata to
help with cloud provider configuration
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044038#comment-13044038 ]
Adrian Cole commented on WHIRR-326:
-----------------------------------
this class is specifically org.jclouds.providers.Providers
> 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
>
> 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
[jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-326:
------------------------------
Fix Version/s: 0.6.0
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (WHIRR-326) Use jclouds provider metadata to
help with cloud provider configuration
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ 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
It should be ready. I really like this jclouds feature. Great work!
> 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, 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
[jira] [Commented] (WHIRR-326) Use jclouds provider metadata to
help with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046236#comment-13046236 ]
Andrei Savu commented on WHIRR-326:
-----------------------------------
How does the output look like? Usable?
> 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
[jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu reassigned WHIRR-326:
---------------------------------
Assignee: Andrei Savu
> 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
[jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-326:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Tom for taking a look.
> 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, 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
[jira] [Commented] (WHIRR-326) Use jclouds provider metadata to
help with cloud provider configuration
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
Agreed.
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
[jira] [Updated] (WHIRR-326) Use jclouds provider metadata to help
with cloud provider configuration
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ 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
Updated patch.
> 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, 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