Ask Your Question
0

networking problems in running instances

asked 2011-05-09 18:32:11 -0500

diego-lalo gravatar image

Hi everyone, it's me again :) This time I have issues with networking of the instances. I'm running openstack in a two node configuration, there are three instances running in a node and one in the other node, here is the output of euca-describe-instances:

euca-describe-instances -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud RESERVATION r-qgwxc38z proj1 default INSTANCE i-00000002 ami-00000003 192.168.0.2 192.168.0.2 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:04Z nova RESERVATION r-0w1f16dn proj1 default INSTANCE i-00000004 ami-00000003 192.168.0.4 192.168.0.4 running None (proj1, eucalyptus) 0 m1.tiny 2011-05-09T17:57:28Z nova RESERVATION r-20qqjtse proj1 default INSTANCE i-00000003 ami-00000003 192.168.0.3 192.168.0.3 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:18Z nova

here is the nova.conf of the cloud controller:

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --network_size=88 --network_manager=nova.network.manager.FlatManager --routing_source_ip=192.168.1.208 --FAKE_subdomain=ec2 --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

here is the nova.conf of the compute node:

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --network_size=18 --network_manager=nova.network.manager.FlatManager --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

here is the ifconfig output of the cloud controller:

br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1304169 errors:0 dropped:0 overruns:0 frame:0 TX packets:1881333 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:426295659 (426.2 MB) TX bytes:2294268253 (2.2 GB)

eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1313062 errors:0 dropped:0 overruns:0 frame:0 TX packets:1885918 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:446334788 (446.3 MB) TX bytes:2294658231 (2.2 GB) Interrupt:42 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255 ...
(more)

edit retag flag offensive close merge delete

20 answers

Sort by ยป oldest newest most voted
0

answered 2011-05-12 20:42:23 -0500

diego-lalo gravatar image

I reconfigured the cloud and the problem has gone, ty for your help Vish :)

edit flag offensive delete link more
0

answered 2011-05-12 17:25:32 -0500

diego-lalo gravatar image
  I tried to do what you said: ip link set promisc on dev br100 on the compute node but br100 only appears when some instance is launched on that node but it doesn't exist right now. I also set the flag --flat_interface on both nodes.

Cheers Diego

edit flag offensive delete link more
0

answered 2011-05-11 17:12:07 -0500

vishvananda gravatar image

There are definitely some issues with the setup. First of all, flat manager requires quite a bit of manual setup. You will probably have a much easier time using FlatDHCPManager

Fixed range should match the networks you have set up, and you probably need to set the dhcp start address --fixed_range=192.168.0.0/24 --flat_network_dhcp_start=192.168.0.2

You may need to recreate your networks after making these changes.

Vish

On May 9, 2011, at 11:35 AM, Diego Lalo wrote:

New question #156783 on OpenStack Compute (nova): https://answers.launchpad.net/nova/+q...

Hi everyone, it's me again :) This time I have issues with networking of the instances. I'm running openstack in a two node configuration, there are three instances running in a node and one in the other node, here is the output of euca-describe-instances:

euca-describe-instances -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud RESERVATION r-qgwxc38z proj1 default INSTANCE i-00000002 ami-00000003 192.168.0.2 192.168.0.2 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:04Z nova RESERVATION r-0w1f16dn proj1 default INSTANCE i-00000004 ami-00000003 192.168.0.4 192.168.0.4 running None (proj1, eucalyptus) 0 m1.tiny 2011-05-09T17:57:28Z nova RESERVATION r-20qqjtse proj1 default INSTANCE i-00000003 ami-00000003 192.168.0.3 192.168.0.3 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:18Z nova

here is the nova.conf of the cloud controller:

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --network_size=88 --network_manager=nova.network.manager.FlatManager --routing_source_ip=192.168.1.208 --FAKE_subdomain=ec2 --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

here is the nova.conf of the compute node:

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --network_size=18 --network_manager=nova.network.manager.FlatManager --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

here is the ifconfig output of the cloud controller:

br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1304169 errors:0 dropped:0 overruns:0 frame:0 TX packets:1881333 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ...

(more)
edit flag offensive delete link more
0

answered 2011-05-12 20:41:29 -0500

vishvananda gravatar image

The promisc on is supposed to fix the public internet problem. you might want to make sure you set --my_ip=192.168.1.100 # (or whatever the ip is for each server) sometimes it can't discover the key properly. Afterwards you may have to flush all of the iptables rules on both hosts and restart the services and rerun instances.

Vish

On May 12, 2011, at 12:16 PM, Diego Lalo wrote:

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

Status: Answered => Open

Diego Lalo is still having a problem: The console output is fine, you are right I can't access the instance from within the compute node but I can access it through the cloud controller :) The only problem that remains is that the instance doesn't have internet, I tried to do a yum update from within the instance and nothing happened, I also tried to do a ping www.free.fr and didn't work:

-bash-3.2# ping www.free.fr PING www.free.fr (212.27.48.10) 56(84) bytes of data.

this is the only line that appears in the instance console

Thanks a lot for the help you are giving to me Vish!! Diego


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-05-10 10:46:47 -0500

Maybe U should input authorize command, - for ping

euca-authorize -P icmp -t -1:-1 default

  • for ssh

    ecua-authorize -P tcp -p 22 default

edit flag offensive delete link more
0

answered 2011-05-10 12:56:51 -0500

diego-lalo gravatar image

I executed the commands you said jaes but I still can't access the instance via SSH, I rebooted the instance but nothing happened, ty for your answer :)

Cheers Diego

edit flag offensive delete link more
0

answered 2011-05-11 18:25:18 -0500

diego-lalo gravatar image
      Thanks for your answer Vish, I did what you said, I deleted the network using nova-manage, I recreated it using nova-manage network create 192.168.0.0/24 1 255 and finally I restarted all the nova-services on both nodes but I still can't access the instance, if I access the instance using virt-manager and execute ifconfig the IP I see was 192.168.1.233 and not 192.168.0.2, here is the output of euca2ools commands:

[root@lore 160]# euca-run-instances ami-00000003 -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud --kernel aki-00000001 --ramdisk ari-00000002 -t m1.tiny RESERVATION r-2j0vsybx proj1 default INSTANCE i-00000008 ami-00000003 scheduling None (proj1, None) 2011-05-11T18:06:19Z None None [root@lore 160]# euca-describe-instances -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud RESERVATION r-2j0vsybx proj1 default INSTANCE i-00000008 ami-00000003 192.168.0.2 192.168.0.2 running None (proj1, eucalyptus) 0 m1.tiny 2011-05-11T18:06:19Z nova

Cheers Diego

edit flag offensive delete link more
0

answered 2011-05-11 18:40:35 -0500

vishvananda gravatar image

192.168.0.0/24 1 255 that should be 256 not 255 (there are 256 addresses in a /24)

The issue that you are having is that you have another dhcp server responding to dhcp requests for that network. You may have an easier time using the 10.x range instead of the 192.168 range. Otherwise you will need to make sure that your other dhcp server isn't handing out ips, which may be a little to complicated to tackle.

You also should probably killall dnsmasq and restart nova-network to make sure that there aren't any lingering dhcp servers on the network host.

Vish

edit flag offensive delete link more
0

answered 2011-05-11 19:28:22 -0500

diego-lalo gravatar image

I tried what you said, I modified nova.conf in both machines with the following info:

CLOUD CONTROLLER br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1768290 errors:0 dropped:0 overruns:0 frame:0 TX packets:889712 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:477168390 (477.1 MB) TX bytes:99689011 (99.6 MB)

eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1769340 errors:0 dropped:0 overruns:0 frame:0 TX packets:890126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:501999740 (501.9 MB) TX bytes:99716935 (99.7 MB) Interrupt:42 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7259945 errors:0 dropped:0 overruns:0 frame:0 TX packets:7259945 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5251451354 (5.2 GB) TX bytes:5251451354 (5.2 GB)

virbr0 Link encap:Ethernet HWaddr de:18:35:e5:fa:1c
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

COMPUTE NODE

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --flat_network_dhcp_start=10.0.0.2 --network_size=88 --network_manager=nova.network.manager.FlatManager --routing_source_ip=192.168.1.208 --FAKE_subdomain=ec2 --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --flat_network_dhcp_start=10.0.0.2 --network_size=18 --network_manager=nova.network.manager.FlatManager --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

br100 Link encap:Ethernet HWaddr 00:24:8c ... (more)

edit flag offensive delete link more
0

answered 2011-05-11 19:40:19 -0500

vishvananda gravatar image

A) network_size should be a power of two so use 256 instead of 255 B) You still need to switch to FlatDHCPManager C) The bridges will be created automatically by FlatDHCP so you can move the ip back to eth0 and delete the br100

Vish

On May 11, 2011, at 12:31 PM, Diego Lalo wrote:

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

Status: Answered => Open

Diego Lalo is still having a problem: I tried what you said, I modified nova.conf in both machines with the following info:

CLOUD CONTROLLER br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1768290 errors:0 dropped:0 overruns:0 frame:0 TX packets:889712 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:477168390 (477.1 MB) TX bytes:99689011 (99.6 MB)

eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1769340 errors:0 dropped:0 overruns:0 frame:0 TX packets:890126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:501999740 (501.9 MB) TX bytes:99716935 (99.7 MB) Interrupt:42 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7259945 errors:0 dropped:0 overruns:0 frame:0 TX packets:7259945 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5251451354 (5.2 GB) TX bytes:5251451354 (5.2 GB)

virbr0 Link encap:Ethernet HWaddr de:18:35:e5:fa:1c
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

COMPUTE NODE

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host=192.168.1.208 --rabbit_host=192.168.1.208 --cc_host=192.168.1.208 --ec2_url=http://192.168.1.208:8773/services/Cloud --fixed_range=10.0.0.0/12 --flat_network_dhcp_start=10.0.0.2 --network_size=88 --network_manager=nova.network.manager.FlatManager --routing_source_ip=192.168.1.208 --FAKE_subdomain=ec2 --image_service=nova.image.glance.GlanceImageService --glance_host=192.168.1.208 --glance_port=9292 --sql_connection=mysql://root:nova@192.168.1.208/nova

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path ...

(more)
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-05-09 18:32:11 -0500

Seen: 260 times

Last updated: May 12 '11