Closed (outdated)
Project:
Cloud
Version:
6.x-1.01
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2011 at 11:11 UTC
Updated:
8 Aug 2018 at 21:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yas@disymus
Here is the example settings if you install Cloud module onto the same OpenStack nova machine:
Comment #2
disymus commentedAfter configuring as mentioned above it says "The variables are not correctly configured". When we dsm($myclient->data) in aws/modules/aws_ec2/aws_ec2_lib_elastic_ips_db.inc, we got the following output
<?xml version="1.0"?> <Response><Errors><Error><Code>NoFloatingIpsDefined</Code><Message>Zero floating ips exist.</Message></Error></Errors><RequestID>T9DJQ7YTWJ3E8OFQQ9DX</RequestID></Response>Just the nova/contrib/nova.sh run doesn't work out of the box. How can we fix this?
Comment #3
yas@disymus
Sorry I gave you the wrong info (I corrected the above info).
Please note the following:
Access Key: admin:admin
AWS Secret Key: admin
User ID: 42
Refer a .novarc file
Comment #4
disymus commentedYeah, i did try the above changes but i still get the "NoFloatingIpsDefined" error. Also i tried putting 192.168.10.0 in place of 127.0.0.1 also but in vain. Hereby i attach the novarc file & the log file of running 'nova/contrib/nova.sh run'.
Comment #5
yas@disymus
1) Are you successful to install nova?
2) Can you manually launch an instance from nova by command line?
3) Which version of nova are you using? --- We are only testing Bexar, not Cactus. Try Baxer.
4) Search google with the keyword 'NoFloatingIpsDefined' --- as a result, https://code.launchpad.net/~jtran/nova/lp794651/+merge/63943
Comment #6
disymus commentedThank you very much. I will switch to bexar now. Would be better if cloud/modules/iaas/modules/openstack/README.txt is updated with
bzr branch lp:nova/bexarThanks
Disymus
Comment #7
yas@disymus
Thank you for your suggestion, I will include that in the next update. FYI, I also confirmed to run:
bzr branch lp:nova/cactusComment #8
disymus commentedWhile trying to run a instance i get the following error
* There was a problem while launching the instance. An unknown error has occurred. Please try your request again.
* Failed to launch instance.
error value during dsm($myclient) in aws/modules/aws_ec2/aws_ec2_lib_instances_db.inc says "Bad Request" and code is "400". Value of request was
GET /services/Cloud/?Action=RunInstances&ImageId=ami-7055b519&MinCount=1&MaxCount=1&InstanceType=m1.small&Version=2011-02-28&KeyName=Siva&SecurityGroup.2=&AWSAccessKeyId=admin%3Aadmin&SignatureVersion=1&SignatureMethod=HmacSHA1&Timestamp=2011-08-04T09%3A41%3A50Z&Signature=sawI2Pd8MfwrEQDD80ACzKY%2FoSg%3D HTTP/1.0 Host: localhost:8773 User-Agent: Drupal (+http://drupal.org/)and response was
<?xml version="1.0"?> <Response><Errors><Error><Code>UnknownError</Code><Message>An unknown error has occurred. Please try your request again.</Message></Error></Errors><RequestID>B43WVLYLUNGIUCFG9NF3</RequestID></Response>Also do we need to download iso images seperately and add it manually to nova? What is the requirement to add a SSH key pair name?
Comment #9
yas@disymus
Could you launch an instance of OpenStack on console (command line tool like eucatool) ? What is the version of OpenStack? As long as I used a script / command "/home/ubuntu/nova/contrib/nova.sh install", it is working. The script also installs minimal images such as kernel, ramdisk, and root filesystem. In Clanavi, as long as we can make server template, it should be able to launch instance(s). I don't know the SSH key pair name requirement on OpenStack nova. The default key is okay to launch.
Comment #10
yas