I removed cached data and it asks me username and password through browser now. 
it works!

However, EC2_ACCESS_KEY in OpenStack contains a colon to contain a project ID 
which causes a problem to authenticate because a project ID and a colon are 
truncated when it requests with it to a server. 

Thanks,
Kyoungho

On Aug 24, 2011, at 2:24 PM, Sang-Min Park wrote:

> in theory, it should work as long as openstack backend implements AWS api 
> correctly and that's theory.
> 
> one way to debug is to see wire message. For example:
> tcpdump -i eth0 -A -s0 -l 'tcp port 8773'
> 
> 
> On Wed, Aug 24, 2011 at 12:17 PM, Kyoungho An <[email protected]> wrote:
> I tried to execute the command, and there is no error messages. However, I 
> can see nothing about images or instances. Actually, I am using OpenStack 
> which can be controlled through Euca2ools, so I thought it would be 
> compatible with Eucalyptus driver. Do you think it is the problem that I 
> can't see anything?
> 
> Thanks,
> Kyoungho
> 
> 
> On Aug 24, 2011, at 9:54 AM, Sang-Min Park wrote:
> 
>> Hmm strange. My browser always prompted me to enter uname / password.
>> Can you try this?
>> 
>> curl -G -u $(echo $EC2_ACCESS_KEY):$(echo $EC2_SECRET_KEY) -H 
>> "X-Deltacloud-Driver: eucalyptus"  
>> http://localhost:3001/api/images?format=xml
>> 
>> This should return the images in your eucalyptus cloud. 
>> 
>> --SM
>> 
>> On Wed, Aug 24, 2011 at 7:19 AM, Kyoungho An <[email protected]> wrote:
>> The following is the logs until "internal Server Error" occurred: 
>> 
>> kyoungho@ubuntu:/var/lib/gems/1.8/gems/deltacloud-core-0.3.0/bin$ 
>> ./deltacloudd -i eucalyptus -p 3001 -P 
>> "ec2=129.59.104.94:8773;s3=129.59.104.94:3333"
>> Starting Deltacloud API :: eucalyptus :: 
>> ec2=129.59.104.94:8773;s3=129.59.104.94:3333 :: http://localhost:3001/api
>> 
>> ./../lib/sinatra/rack_etag.rb:33: warning: already initialized constant 
>> DEFAULT_CACHE_CONTROL
>> => Ctrl-C to shutdown server
>> [2011-08-24 07:14:37] INFO  WEBrick 1.3.1
>> [2011-08-24 07:14:37] INFO  ruby 1.8.7 (2010-01-10) [i486-linux]
>> [2011-08-24 07:14:37] WARN  TCPServer Error: Address already in use - bind(2)
>> [2011-08-24 07:14:37] INFO  WEBrick::HTTPServer#start: pid=27439 port=3001
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:105: warning: 
>> already initialized constant HEX
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:107: warning: 
>> already initialized constant TO_REMEMBER
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:108: warning: 
>> already initialized constant ASCII
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/errors.rb:128: warning: 
>> already initialized constant DEFAULT_CLOSE_ON_4XX_PROBABILITY
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/parsers.rb:47: warning: 
>> already initialized constant DEFAULT_XML_LIBRARY
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/awsbase.rb:66: warning: 
>> already initialized constant AMAZON_PROBLEMS
>> /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/awsbase.rb:86: warning: 
>> already initialized constant DEFAULT_SIGNATURE_VERSION
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /api HTTP/1.1" 200 4357 0.0722
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /api HTTP/1.1" 200 4357 0.2069
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /stylesheets/compiled/screen.css 
>> HTTP/1.1" 304 - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /stylesheets/compiled/screen.css 
>> HTTP/1.1" 304 - 0.0006
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /stylesheets/compiled/print.css 
>> HTTP/1.1" 304 - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /stylesheets/compiled/print.css 
>> HTTP/1.1" 304 - 0.0009
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET 
>> /stylesheets/compiled/application.css HTTP/1.1" 304 - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET 
>> /stylesheets/compiled/application.css HTTP/1.1" 304 - 0.0007
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /javascripts/jquery-1.4.2.min.js 
>> HTTP/1.1" 304 - 0.0004
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /javascripts/jquery-1.4.2.min.js 
>> HTTP/1.1" 304 - 0.0006
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /javascripts/application.js 
>> HTTP/1.1" 304 - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /javascripts/application.js 
>> HTTP/1.1" 304 - 0.0006
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/logo-wide.png HTTP/1.1" 
>> 304 - 0.0004
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/logo-wide.png HTTP/1.1" 
>> 304 - 0.0006
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/topbar-bg.png HTTP/1.1" 
>> 304 - 0.0007
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/topbar-bg.png HTTP/1.1" 
>> 304 - 0.0008
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/bread-bg.png HTTP/1.1" 304 
>> - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:44] "GET /images/bread-bg.png HTTP/1.1" 304 
>> - 0.0006
>> 127.0.0.1 - - [24/Aug/2011 07:14:47] "GET /favicon.ico HTTP/1.1" 304 - 0.0005
>> 127.0.0.1 - - [24/Aug/2011 07:14:47] "GET /favicon.ico HTTP/1.1" 304 - 0.0006
>> Aws::AwsError - AWS access keys are required to operate on EC2:
>>  /var/lib/gems/1.8/gems/aws-2.5.6/lib/ses/../awsbase/awsbase.rb:138:in `init'
>>  /var/lib/gems/1.8/gems/aws-2.5.6/lib/ec2/ec2.rb:133:in `initialize'
>>  ./../lib/deltacloud/drivers/eucalyptus/eucalyptus_driver.rb:137:in `new'
>>  ./../lib/deltacloud/drivers/eucalyptus/eucalyptus_driver.rb:137:in 
>> `new_client'
>>  ./../lib/deltacloud/drivers/ec2/ec2_driver.rb:131:in `images'
>>  ./../lib/deltacloud/helpers/application_helper.rb:80:in `send'
>>  ./../lib/deltacloud/helpers/application_helper.rb:80:in `filter_all'
>>  /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
>>  ./../lib/deltacloud/helpers/application_helper.rb:79:in `filter_all'
>>  ./../server.rb:195
>>  ./../lib/sinatra/rabbit.rb:104:in `instance_eval'
>>  ./../lib/sinatra/rabbit.rb:104:in `GET /api/images'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1151:in `call'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1151:in `compile!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:724:in 
>> `instance_eval'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:724:in `route_eval'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:708:in `route!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:758:in 
>> `process_route'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:755:in `catch'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:755:in 
>> `process_route'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:707:in `route!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:706:in `each'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:706:in `route!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:843:in `dispatch!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:644:in `call!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:808:in 
>> `instance_eval'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:808:in `invoke'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:808:in `catch'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:808:in `invoke'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:644:in `call!'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:629:in `call'
>>  ./../lib/sinatra/rack_driver_select.rb:45:in `call'
>>  ./../lib/sinatra/rack_matrix_params.rb:80:in `call'
>>  ./../lib/sinatra/rack_runtime.rb:36:in `call'
>>  ./../lib/sinatra/rack_etag.rb:42:in `call'
>>  /var/lib/gems/1.8/gems/rack-accept-0.4.4/lib/rack/accept/context.rb:22:in 
>> `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/head.rb:9:in `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/commonlogger.rb:20:in `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/methodoverride.rb:24:in `call'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1272:in `call'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1303:in 
>> `synchronize'
>>  /var/lib/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1272:in `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/reloader.rb:44:in `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/commonlogger.rb:20:in `call'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/handler/webrick.rb:59:in 
>> `service'
>>  /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
>>  /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
>>  /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
>>  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
>>  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
>>  /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
>>  /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
>>  /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
>>  /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
>>  /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
>>  /var/lib/gems/1.8/gems/rack-1.3.2/lib/rack/handler/webrick.rb:13:in `run'
>>  ./deltacloudd:96
>> 127.0.0.1 - - [24/Aug/2011 07:14:58] "GET /api/images HTTP/1.1" 500 30 0.0028
>> 127.0.0.1 - - [24/Aug/2011 07:14:58] "GET /api/images HTTP/1.1" 500 30 0.0741
>> 
>> On Aug 23, 2011, at 7:15 PM, Sang-Min Park wrote:
>> 
>>> It sounds like a different problem in the backend. Do you see any 
>>> suspicious logs by the daemon?
>>> 
>>> Sent from my Motorola ATRIX™ 4G on AT&T
>>> 
>>> 
>>> -----Original message-----
>>> From: Kyoungho An <[email protected]>
>>> To: "[email protected]" 
>>> <[email protected]>
>>> Sent: Wed, Aug 24, 2011 00:00:49 GMT+00:00
>>> Subject: Re: Eucalyptus credentials
>>> 
>>> The deltacloud daemon has been started with the endpoint as you suggested, 
>>> and I access http://localhost:3001 as a client through a browser, but when 
>>> I select an operation which needs username/password, the browser shows 
>>> "internal error" without asking username/password. Can you let me know how 
>>> to set up username/password in a browser?
>>> 
>>> Thanks!
>>> Kyoungho
>>> 
>>> On Aug 23, 2011, at 6:27 PM, Sang-Min Park wrote:
>>> 
>>> > Hi Kyoungho,
>>> >
>>> > You need to set them as username / password in the HTTP request.
>>> > You don't need to set it when you starts deltacloud daemon. It's for 
>>> > client
>>> > request.
>>> >
>>> > If you use web browser to access the deltacloud, you don't need to set it.
>>> > When you point to some operation that needs username/password, the browser
>>> > will most likely prompt and will cache your input.
>>> >
>>> > The two parameters you should supply to deltacloud server are URL of your
>>> > eucalyptus and S3 service. Here's the example:
>>> >
>>> > ./bin/deltacloudd -i eucalyptus -p 3001 -P "ec2=192.168.1.1:8773;s3=
>>> > 192.168.1.1:8773"
>>> >
>>> >
>>> > ---SM
>>> >
>>> > On Tue, Aug 23, 2011 at 4:10 PM, Kyoungho An <[email protected]> 
>>> > wrote:
>>> >
>>> >> Hi all,
>>> >>
>>> >> I am trying to use Eucalyptus driver executing like deltacloudd -i
>>> >> eucalyptus. However, there is an error on the log:
>>> >> Aws::AwsError - AWS access keys are required to operate on EC2:
>>> >>
>>> >> Therefore, I tried to set up Access Key ID, Secret Access Key, and 
>>> >> endpoint
>>> >> on the drivers.yaml file, but it still does not work. I don't know where 
>>> >> I
>>> >> need to set up these kinds of stuffs.
>>> >>
>>> >> Can you please help me to find out any solutions for this problem?
>>> >>
>>> >> Thanks,
>>> >> Kyoungho
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > ----------------------------------------------------
>>> > Sang-Min Park
>>> > Engineer
>>> > Eucalyptus Systems
>>> 
>> 
>> On Aug 23, 2011, at 7:15 PM, Sang-Min Park wrote:
>> 
>>> It sounds like a different problem in the backend. Do you see any 
>>> suspicious logs by the daemon?
>>> 
>>> Sent from my Motorola ATRIX™ 4G on AT&T
>>> 
>>> 
>>> -----Original message-----
>>> From: Kyoungho An <[email protected]>
>>> To: "[email protected]" 
>>> <[email protected]>
>>> Sent: Wed, Aug 24, 2011 00:00:49 GMT+00:00
>>> Subject: Re: Eucalyptus credentials
>>> 
>>> The deltacloud daemon has been started with the endpoint as you suggested, 
>>> and I access http://localhost:3001 as a client through a browser, but when 
>>> I select an operation which needs username/password, the browser shows 
>>> "internal error" without asking username/password. Can you let me know how 
>>> to set up username/password in a browser?
>>> 
>>> Thanks!
>>> Kyoungho
>>> 
>>> On Aug 23, 2011, at 6:27 PM, Sang-Min Park wrote:
>>> 
>>> > Hi Kyoungho,
>>> >
>>> > You need to set them as username / password in the HTTP request.
>>> > You don't need to set it when you starts deltacloud daemon. It's for 
>>> > client
>>> > request.
>>> >
>>> > If you use web browser to access the deltacloud, you don't need to set it.
>>> > When you point to some operation that needs username/password, the browser
>>> > will most likely prompt and will cache your input.
>>> >
>>> > The two parameters you should supply to deltacloud server are URL of your
>>> > eucalyptus and S3 service. Here's the example:
>>> >
>>> > ./bin/deltacloudd -i eucalyptus -p 3001 -P "ec2=192.168.1.1:8773;s3=
>>> > 192.168.1.1:8773"
>>> >
>>> >
>>> > ---SM
>>> >
>>> > On Tue, Aug 23, 2011 at 4:10 PM, Kyoungho An <[email protected]> 
>>> > wrote:
>>> >
>>> >> Hi all,
>>> >>
>>> >> I am trying to use Eucalyptus driver executing like deltacloudd -i
>>> >> eucalyptus. However, there is an error on the log:
>>> >> Aws::AwsError - AWS access keys are required to operate on EC2:
>>> >>
>>> >> Therefore, I tried to set up Access Key ID, Secret Access Key, and 
>>> >> endpoint
>>> >> on the drivers.yaml file, but it still does not work. I don't know where 
>>> >> I
>>> >> need to set up these kinds of stuffs.
>>> >>
>>> >> Can you please help me to find out any solutions for this problem?
>>> >>
>>> >> Thanks,
>>> >> Kyoungho
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > ----------------------------------------------------
>>> > Sang-Min Park
>>> > Engineer
>>> > Eucalyptus Systems
>>> 
>> 
>> 
>> 
>> 
>> -- 
>> 
>> ----------------------------------------------------
>> Sang-Min Park
>> Engineer
>> Eucalyptus Systems
>> 
> 
> 
> 
> 
> -- 
> 
> ----------------------------------------------------
> Sang-Min Park
> Engineer
> Eucalyptus Systems
> 

Reply via email to