search

bilelmsekni / OpenStack-Folsom-Install-guide

A full installation guide for OpenStack Folsom with Quantum
161 stars 136 forks source link

Openstack instanance not getting the IP "Folsom cluster on Ubuntu 10.12" #78

Closed cgirda closed 11 years ago

cgirda commented 11 years ago 
  First of all thank you so much for putting all this together. I followed the following documentation on setting up a 3 node cluster with 2 x nic. My VMz/instance are not getting any IP.

Folsom + Quantum on GRE with 2 NICs is available through GRE/2NICs branch: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

                Looking at the diagnostics.  I see there is no connection between the bridges, between my network and compute node. Hence I am not getting the dhcp offer from my network node.

Network-Node:

bridge name bridge id STP enabled interfaces br-ex 0000.00237d28f814 no eth2
br-int 0000.e6ecd960864d no tapf0241b37-64 br-tun 0000.5680c46e5748 no

netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.24.253 0.0.0.0 UG 0 0 0 eth0 10.0.24.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 tapf0241b37-64

Compute Node:

brctl show

bridge name bridge id STP enabled interfaces br-int 0000.aed7f6580d45 no qvo3609cc1d-00 qvoac592d01-a3 qbr3609cc1d-00 8000.be822f621717 no qvb3609cc1d-00 vnet1 qbrac592d01-a3 8000.c2983a7652b6 no qvbac592d01-a3

netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.23.253 0.0.0.0 UG 0 0 0 eth0 10.0.23.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1

Just wondering if there is any set of IP table rules to be added ?

Thank you Chakri

bilelmsekni commented 11 years ago

Hello,

No there is no iptable rules to add. Network node should be able to communicate with the control node using the management network and the VM conf network. Please check if the Quantum components on both nodes are able to talk to each other using their log.

for instance, if the metadata server in the l3_agent.ini is set to x.x.x.x. You must be able to ping that x.x.x.x from the network node using the right interface.

regards, Bilel

----- Mail original -----

De: "Chakri Girda" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Envoyé: Mardi 19 Février 2013 23:34:39 Objet: {Disarmed} [OpenStack-Folsom-Install-guide] Openstack instanance not getting the IP "Folsom cluster on Ubuntu 10.12" (#78)

First of all thank you so much for putting all this together. I followed the following documentation on setting up a 3 node cluster with 2 x nic. My VMz/instance are not getting any IP. Folsom + Quantum on GRE with 2 NICs is available through GRE/2NICs branch: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Looking at the diagnostics. I see there is no connection between the bridges, between my network and compute node. Hence I am not getting the dhcp offer from my network node. Network-Node: bridge name bridge id STP enabled interfaces br-ex 0000.00237d28f814 no eth2

br-int 0000.e6ecd960864d no tapf0241b37-64 br-tun 0000.5680c46e5748 no

netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.24.253 0.0.0.0 UG 0 0 0 eth0 10.0.24.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 tapf0241b37-64 Compute Node: brctl show

bridge name bridge id STP enabled interfaces br-int 0000.aed7f6580d45 no qvo3609cc1d-00 qvoac592d01-a3 qbr3609cc1d-00 8000.be822f621717 no qvb3609cc1d-00 vnet1 qbrac592d01-a3 8000.c2983a7652b6 no qvbac592d01-a3 netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.23.253 0.0.0.0 UG 0 0 0 eth0 10.0.23.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 Just wondering if there is any set of IP table rules to be added ? Thank you Chakri — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/I1T5EjfDb5OWgQ2B_759LUuEgQ6lOZZUxe40bk-l8_JRfGK69McwUSFHG8-UpJuy.gif

cgirda commented 11 years ago

Bilel, Thank you for the response. I verified that to be true. My metadata_IP is the external interface " 10.0.24.121" on the network-node.

auth_url = http://100.10.10.51:35357/v2.0 auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = service_pass metadata_ip = 10.0.24.121 metadata_port = 8775 use_namespaces = False

Verified with the curl test. 

  curl http://10.0.24.121:35357/v2.0/endpoints -H 'x-auth-token: ADMIN'

The thing that I don't understand is.

1> As per the document, I created br-int on both network and compute node but I don't see them ported to any physical interface, are they supposed to be ?

2> The 3 nodes , networks are shown. Tell me if I am doing something wrong on eth2 side.

Controller Node : eth0 ( 10.0.24.121 ) eth1 ( 100.10.10.51 ) Network Node : eth0 ( 10.0.24.122 ) , eth1 ( 100.10.10.52 ) , eth2 ( 0.0.0.0 - promisc mode ) Compute Node : eth1 ( 100.10.10.53 )

eth1 are physically connected to a separate switch. Verified for ping and ssh. eth0 are connected to our internet. Verified for ping and ssh. eth2 on the Network-Node DOES NOT have any physical network connections. This is the one I port the br-ex to

br-ex is used for accessing internet.

ovs-vsctl add-br br-ex ovs-vsctl br-set-external-id br-ex bridge-id br-ex ovs-vsctl add-port br-ex eth2

Thank you Chakri

cgirda commented 11 years ago

Bilel, I was able to move one step ahead by installing "quantum-plugin-linuxbridge-agent" on both network and compute nodes and fixing a typo in my quantum.conf file with the rabbit_host entries. Now the vm gets an IP assigned. Here is my next issue.

(1) The vm has IP 192.168.30.3 and gw 192.168.30.1 (2) The Network Node has a tap interface "doesn't not show up in ifconfig" unless I manually bring it up. Has an IP "192.168.30.2"

(3) On my controller node. route add -net 192.168.30.0/24 gw 10.0.24.244

 * So I can ping 192.168.30.1 & ssh to 192.168.30.2 "Network node tap interface"

Getting closer yet missing something small.

Thank you Chakri

cgirda commented 11 years ago

Bilel, Getting closer.

(1) Installed "quantum-plugin-linuxbridge-agent" and configured the ini file. (2) Rebooted all three nodes. (3) Had to manually bring the br-int interface on network node.

Now

Still cannot

So the problem is

Thank you Chakri

sandeep-raman commented 11 years ago

Hello Chakri,

This sounds similar to the problem I posted - https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/issues/75.

What I have also found is though the vm instance says it is active and has an ip, in reality it does not boot to the OS at all. I verified this by using virtmanager and investigating.

Please check if the symptoms/footprint matches the post.

Regards, Sandeep.

cgirda commented 11 years ago

Sandeep, Thank you for the reference. So finally there seems to be no solution yet, correct ?

Thank you Chakri

sandeep-raman commented 11 years ago

Correct - no solution yet.

cgirda commented 11 years ago

Sandeep, Just out of curiosity so what do you ended up in doing ?

I am debating on what next to bring up a working cluster at my work ?

Thank you Chakri

sandeep-raman commented 11 years ago

I figured out the instance does not boot into the OS which is a first step to fix. You may want to verify the same. I'm continuing to investigate this.

cgirda commented 11 years ago

Sandeep, 

        Little confused on what your saying. The instance boots to OS, I can console login. It gets a IP assigned via dhcp running on the network node. Can you clarify ? 
           So in a gist, "Openstack Folsom IS NOT READY for multi-cluster with Quantam Networking" . What a waste of time for us.

Chakri

dguitarbite commented 11 years ago

Hi sorry for late reply ... the problem is that L3 agent alone is crippled and requires L2 agent. I asked the same question on OpenStack Docs ... here is the link - http://docs.openstack.org/folsom/openstack-network/admin/content/app_demo.html .I have to test this but I'm quite sure as the person answering to my question is an expert on quantum. If someone has tried this please do tell me if it works.