← Back to team overview

openstack team mailing list archive

Grizzly Multinode, but Quantum not working

 

Hi all,

I followed the Grizzly Multinode howto (https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst), but could not make Quantum operational. I apologize in advance for the long email, but I was hoping that someone can help me with this setup.

To make it as easy as possible, my setup env is absolutely the same: I have the Controller, Compute and Network nodes, which are connected to each other as described. The only difference is "VM Internet Access" IP address. Instead of 192.168.100.0/24, my range is 192.168.0.0/16, and I gave 192.168.1.0/24 to OpenStack nodes. OS is Ubuntu Server 12.04 x86_64. Just to make it clear, my company's network is organized like this:

[Public IP: 212.200.x.x] <-> Router (gateway: 192.168.0.3) <-> [192.168.0.0/16] <-> [our workstations: 192.168.0.0/24]
							  			    [openstack nodes: 192.168.1.0/24]

Regarding nodes' configuration, I followed the same steps as howto suggested, changing only IP addresses where needed (ie, 10.10.10.51 -> 10.10.10.201, etc). Everything went fine and without errors, so I came to "5. Your first VM". Since I'm still struggling to understand Quantum's fundamentals, I am not sure whether I did something wrong from now on. For this first steps with OpenStack, my goal is to be able to create a VM and to give it IP address from 192.168.1.0/24 pool, so I can ssh to it from my workstation, for example. Of course, it would be nice to allow that VM access to the Internet (public access to that VM is not necessary for now).

So, I created the new tenant and network for it. The subnet for tenant network I created like this:

# quantum subnet-create --tenant-id $put_id_of_project_one net_proj_one 10.10.10.0/24

Next, I created the router and assigned it to the l3-agent and subnet. Then, I created ext_net and a subnet for the floating ips, like this:

# quantum subnet-create --tenant-id $put_id_of_admin_tenant --allocation-pool start=192.168.1.2,end=192.168.1.199 --gateway 192.168.0.3 ext_net 192.168.1.0/24 --enable_dhcp=False

Is this correct? Internal network should be 10.10.10.0/24 and external 192.168.1.0/24, so when I create an instance and associate the IP, lets say, 192.168.1.5, it should forward packets to 10.10.10.5..right?

Back to howto, I set the security rules like this (because in nova.conf I told it to use Quantum Sec.Groups, not Nova's): # quantum security-group-rule-create --protocol icmp --direction ingress default # quantum security-group-rule-create --protocol tcp --port-range-min 22 --port-range-max 22 --direction ingress default

Finally, I logged in Dashboard and created new instance, which was successful. But, there are several networking problems:

1. Instance Console Log: wget: can't connect to remote host (169.254.169.254): Network is unreachable 2. VM did not receive its private IP (10.10.10.x), so it is not pingable

So, I would appreciate it if you could tell me what could be the potential problems, just to point me in some directions. Feel free to ask for logs and configs, I will gladly provide those.

Thanks in advance.
Best regards,

--
Nikola Pajtic