Ask Your Question
1

devstack instance not reachable on VirtualHost with NAT

asked 2014-02-04 23:16:02 -0500

sivasamyk gravatar image

updated 2014-02-06 17:25:43 -0500

smaffulli gravatar image

My devstack instance not reachable on Virtual Host with NAT

The instance is shown active in the Horizon dashboard, but not reachable. I am able to launch a console from dashboard.

As per the below console log of instance, no instance ID or IP address is assigned to the instance.

The floating IP assigned to the instance is 10.0.2.226. This IP is not reachable from the Ubuntu machine.

The instances are reachable when I start the Virtual Host with bridge configuration

Following is my configuration:

Host : Windows 7 Guest : Ubuntu 12.04 (using Virtual Box) with NAT networking with IP : 10.0.2.15

Devstack started in Ubuntu with following localrc file:

DATABASE_PASSWORD=mydevstack
RABBIT_PASSWORD=mydevstack
SERVICE_TOKEN=mydevstack
SERVICE_PASSWORD=mydevstack
ADMIN_PASSWORD=mydevstack
SCREEN_LOGDIR=$DEST/log/screen
VERBOSE=True
HOST_IP=10.0.2.15
FLAT_INTERFACE=eth0
FIXED_RANGE=192.168.0.1/24
FIXED_NETWORK_SIZE=256
FLOATING_RANGE=10.0.2.224/27

Console log of the instance:

Starting network... 
udhcpc (v1.18.5) started 
Sending discover... 
Sending select for 10.0.2.16... 
Lease of 10.0.2.16 obtained, lease time 86400 
deleting routers 
route: SIOCDELRT: No such process 
adding dns 10.220.0.12 
adding dns 10.100.98.21 
adding dns 10.220.0.11 
cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 1/30: up 10.25. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 2/30: up 14.59. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 3/30: up 17.59. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 4/30: up 21.66. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 5/30: up 24.66. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 6/30: up 28.75. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 7/30: up 31.76. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 8/30: up 35.87. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 9/30: up 38.88. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 10/30: up 43.00. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 11/30: up 47.10. request failed 
wget: can't connect to remote host (169.254.169.254): No route to host 
cloud-setup: failed 12 ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-05-07 03:30:23 -0500

Rajat gupta gravatar image

updated 2014-05-07 03:30:59 -0500

You need to create two network adapters : eth0 as Host-only adapter and make it as primary interface and eth1 as NAT so that NAT will be able to help you for connecting with the internet for downloading openstack packages and other inmportant stuff while eth0 will be used for accessing the VM from host machine.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-02-04 23:16:02 -0500

Seen: 1,144 times

Last updated: May 07 '14