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

Marios Andreou commented on DTACLOUD-578:
-----------------------------------------

Hi Cristovao:                                                              
                                                                           
ok - finally got some time to look into this. So I checked the APIs for "first 
gen" servers @ [1] and "next gen" servers @ [2]. Now from a quick look the API 
calls for getting the images are the same in both APIs. I can't see a problem 
in the driver code (especially as both version of the API are the same) though 
the 'cloudservers' rubygem [3] the driver uses seems to be a little old -but 
again, can't see any obvious problems with the way that calls the /images in 
RAX.
                                                                           
So I suspect it is the authentication endpoint which is causing problems here. 
This was confirmed when I saw that for both first and next gen APIs the 
authentication endpoint is given as the same [4][5] - they both point you at 
the 'next gen' api interface - which may be the reason you are only seeing the 
next gen images as you started the server with:
                                                                           
deltacloudd -i rackspace -P https://lon.identity.api.rackspacecloud.com/v2.0/
                                                                           
i.e. specifying the 'next gen' auth. endpoint. After a little digging around I 
found the 'legacy' authentication URL for v1 of the API [6]. Can you try
                                                                           
deltacloudd -i rackspace -P https://lon.identity.api.rackspacecloud.com/v1.1
                                                                           
and see if that lists the older gen images? Let's take it from there. With 
respect to the other issue mentioned here (can't boot new instances) can you 
give me some more information? Are you getting an error?

thanks, marios                                                                
                                                                             
                                                                           
[1] http://docs.rackspace.com/servers/api/v1.0/cs-devguide/content/index.html
[2] http://docs.rackspace.com/servers/api/v2/cs-devguide/content/index.html
[3] https://github.com/rackerlabs/ruby-cloudservers                        
[4] http://docs.rackspace.com/servers/api/v1.0/cs-devguide/content/auth.html
[5] 
http://docs.rackspace.com/servers/api/v2/cs-devguide/content/auth_endpoints.html
[6] 
http://docs.rackspace.com/auth/api/v2.0/auth-client-devguide/content/Endpoints-d1e180.html



                
> Deltacloud and Rackspace
> ------------------------
>
>                 Key: DTACLOUD-578
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-578
>             Project: DeltaCloud
>          Issue Type: Question
>            Reporter: Cristovao Cordeiro
>            Priority: Critical
>
> Hi,
> I have several snapshots in Rackspace, being only one of them a 'New 
> Generation Image'. I was trying out Deltacloud with Rackspace's cloud, and 
> I've noticed that when I list the available images (through the DC's web 
> interface) I only get the New Gen. one...and not the older ones. 
> On the other end, and completely aside from Deltacloud, when I am using the 
> nova client from my UI and I do nova image-list, I can only see the older 
> images and not the New Gen one. 
> Can someone explain these please?
> Thanks
> P.S.: I am now adding some new information to the same issue. I just realized 
> that I can not boot new instances on Rackspace, even though I can list 
> instances and images and fully interact with Rackspace through the DC web 
> interface. I am just doing the follwoing:
>              deltacloudd -i rackspace -P 
> https://lon.identity.api.rackspacecloud.com/v2.0/ -v -r myserver.com
> Thanks in advance for the help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to