deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-579) Using the EC2 frontend with the Openstack driver
Date Wed, 18 Sep 2013 07:04:51 GMT


Marios Andreou commented on DTACLOUD-579:

Chris, thanks very much for looking into this and thanks for your patience; I'm being pulled
in different directions lately and haven't had much time to look at this or JIRA.
Thanks for the patch. So first off, I must admit I have never used the Deltacloud EC2 frontend
to talk to the OpenStack EC2 frontend. I've not looked at the EC2 frontend code for a loong
time and this was actually mfojtik & lutter creation. I don't know what params are being
passed from the EC2 frontend to the driver [1].
If I have understood correctly, the patch @
doesn't resolve the issue? If that's the case I'd rather not commit it before we've found
out exactly what's going on. I don't think I have time to get into that today but at least
its now on my to-do - unless someone beats me to it,
Last thing, would be great if you could help me out with the recreation. If you are using
cURL or some other text-based client can you paste me an example request I can use (no creds
thanks!). It will help people get to debugging this faster
thanks again, marios                                                       
[1] The Deltacloud OpenStack driver is actually using the 'ruby-openstack' rubygem to talk
to OpenStack services; this gem only implements the native OpenStack API so am really not
sure what's being passed back to the OpenStack EC2 frontend.

> Using the EC2 frontend with the Openstack driver
> ------------------------------------------------
>                 Key: DTACLOUD-579
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>            Reporter: Cristovao Cordeiro
> Hello,
> I've noticed that when trying to make launch requests (and only launch requests) through
the DC's EC2 frontend with the Openstack driver, it fails.
> Basically I have a DC server with the EC2 frontend connected to an Openstack provider.
I'm issuing the following:
>     curl --user "user+tenant:pass" "localhost:3004/ec2/?Action=RunInstances&ImageId=b8018jdb-fgfc-412c-9337-6129xj4n152a"
> I get the following:
> Deltacloud::Exceptions::ValidationFailure - Instance name is not a valid hostname:
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/openstack-1.1.0/lib/openstack/connection.rb:474:in
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/openstack-1.1.0/lib/openstack/compute/connection.rb:120:in
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/deltacloud-core-1.1.3/lib/deltacloud/drivers/openstack/openstack_driver.rb:205:in
`block in create_instance'
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/deltacloud-core-1.1.3/lib/deltacloud/drivers/exceptions.rb:220:in
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/deltacloud-core-1.1.3/lib/deltacloud/drivers/exceptions.rb:220:in
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/deltacloud-core-1.1.3/lib/deltacloud/drivers/openstack/openstack_driver.rb:204:in
> ...
> ...
> ...
> This line: "params[:name] = (opts[:name] && opts[:name].length>0)? opts[:name]
: "server#{}" " in the openstack_driver.rb file is the issue. 
> And, even after fast fixing it a new error is raised if I point a flavor in the EC2 request
(like m1.small). This error is:
> Deltacloud::Exceptions::ValidationFailure - Invalid flavorRef provided.:
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/openstack-1.1.0/lib/openstack/connection.rb:474:in
> 	/usr/local/rvm/gems/ruby-2.0.0-p0/gems/openstack-1.1.0/lib/openstack/compute/connection.rb:120:in
> which refers to the second line below the one about the server name.
> Can someone look into this?
> Thanks
> Cris

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:

View raw message