This is an odd bug for sure.. I think its reasonable to expect aeolus users to try and use two ec2 accounts for a region. account #1 for us-east-1 account #2 for us-east-1 On a aeolus server that has been configured w/ aeolus-configure there may be additional steps one would have to take to get this to work.. When you start an additional deltacloud daemon w/ /etc/init.d/deltacloud-ec2-us-east-1 stopped you will get the following.. [root@hp-dl180g6-01 ~]# /usr/bin/deltacloudd -i ec2 -e production -p 3007 --provider us-east-1 Starting Deltacloud API :: ec2 :: us-east-1 :: http://localhost:3007/api >> Thin web server (v1.2.5 codename This Is Not A Web Server) >> Debugging ON >> Maximum connections set to 1024 >> Listening on localhost:3007, CTRL+C to stop /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:105: warning: already initialized constant HEX /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:107: warning: already initialized constant TO_REMEMBER /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:108: warning: already initialized constant ASCII /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/errors.rb:128: warning: already initialized constant DEFAULT_CLOSE_ON_4XX_PROBABILITY /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/parsers.rb:47: warning: already initialized constant DEFAULT_XML_LIBRARY /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:66: warning: already initialized constant AMAZON_PROBLEMS /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:86: warning: already initialized constant DEFAULT_SIGNATURE_VERSION 127.0.0.1 - - [19/Jul/2011 11:22:20] "GET /api HTTP/1.1" 200 1439 0.1346 127.0.0.1 - - [19/Jul/2011 11:22:20] "GET /api HTTP/1.1" 200 1439 0.0169 I'm sure you can get this to work, but it doesnt initially. Another option is to run the additional ec2 deltacloud daemon on anther host.
probably not supported.. closing
perm close