Ask Your Question
0

Accessing the Instance using FloatingIP

asked 2011-01-24 07:30:36 -0500

naangilsunder gravatar image

Hi All, I Installed and Configured Nova using Single Machine Installation (Ubuntu 10.10). Everything went fine,Able to Launch Instance successfully ,am able to ping the Running instance using PrivateIP(10.0.0.8), but not able to Ping the instance using floating IP

The Output of

euca-describe-groups

GROUP federation default default PERMISSION federation default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS icmp -1 -1 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS tcp 3389 3389 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS tcp 1433 1433 FROM CIDR 0.0.0.0/0

euca-describe-instances

RESERVATION r-yr1ph2uf federation INSTANCE i-00000011 ami-u24fq0f9 192.168.1.99 10.0.0.8 running mykey (federation, cnnc) 0 m1.small 2011-01-22 13:48:42.396240 nova

pls help...

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2011-02-02 18:56:35 -0500

vishvananda gravatar image

You can't hit the floating ip from the machine that is running nova-network. Floating ips use natting, and packets from localhost don't go through the nat tables. You need to be on another host on the same network.

On Feb 2, 2011, at 10:32 AM, naangilsunder wrote:

Question #142636 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+q...

Description changed to: Hi All, I Installed and Configured Nova using Single Machine Installation (Ubuntu 10.10). Everything went fine,Able to Launch Instance successfully ,am able to ping the Running instance using PrivateIP(10.0.0.8), but not able to Ping the instance using floating IP

The Output of

euca-describe-groups

GROUP federation default default PERMISSION federation default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS icmp -1 -1 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS tcp 3389 3389 FROM CIDR 0.0.0.0/0 PERMISSION federation default ALLOWS tcp 1433 1433 FROM CIDR 0.0.0.0/0

euca-describe-instances

RESERVATION r-yr1ph2uf federation INSTANCE i-00000011 ami-u24fq0f9 192.168.1.99 10.0.0.8 running mykey (federation, cnnc) 0 m1.small 2011-01-22 13:48:42.396240 nova

pls help...


You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).

edit flag offensive delete link more
0

answered 2011-03-25 07:25:11 -0500

naangilsunder gravatar image

hi Vish,

Thanks for your replay, I followed the below launchpad link it helped me in resolving the issue.

https://answers.launchpad.net/nova/+question/145820 (https://answers.launchpad.net/nova/+q...)

as Everett Toews said in the link, I switched to FlatDHCPManager networking mode and followed the configuration as he mentioned in the link and it worked for me ... :)

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: 2011-01-24 07:30:36 -0500

Seen: 32 times

Last updated: Mar 25 '11