jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-443) Cannot use rackspace-cloudservers-us or aws-ec2 as the provider
Date Mon, 10 Feb 2014 15:57:19 GMT

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

Ignasi Barrera commented on JCLOUDS-443:
----------------------------------------

The issue you have is caused because "openstack-nova" is the compute api, not the blobstore
one. You might try with the Swift provider to be able to get the blob store context.

BTW, if you ask this kind of questions in the user mailing list (http://jclouds.apache.org/documentation/community/)
you will  get better feedback as more eyes will be reading them, and we can keep the issue
tracker just for issues and feature requests :)

> Cannot use rackspace-cloudservers-us or aws-ec2 as the provider
> ---------------------------------------------------------------
>
>                 Key: JCLOUDS-443
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-443
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.7.0
>         Environment: Ubuntu 13.10, Eclipse
>            Reporter: Jeremiah Robertson
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 1.7.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When I go to create the ComputeServiceContext with my credentials and provider in the
rackspace example for creating a server or for the Logging example (CreateServer.java and
Logging.java), it never fully compiles it cannot find the provider. I used rackspace-cloudservers-us
and aws-ec2 as the 2 providers with their set of credentials, and neither worked. Are these
still supported? Please email me back at jrspfd@gmail.com if you have aby ideas on what might
be wrong because it worked a week ago and I'm not really sure whats going on. Thank you!



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message