Ask Your Question
0

Also Nova+Quantum+Openvswitch VLAN Problem!

asked 2012-06-19 08:40:10 -0500

guestly gravatar image

My environment includes two physical hosts. One of them (domain name cc201) installed all of nova components and Glance, Quantum, Keystone, Horizon, Open-vSwitch as controller and network node; the other installed only nova-compute, Quantum, Open-vSwitch as compute node.

also I run quantum-agent, load 8021q module.etc Everything seems runs well. But I found a curious problem!

On cc201, I create networks 192.168.153.0/24(network3, its vlan ID is 6)、192.168.155.0/24(network5, its vlan ID is 8) I run nova-manage on host cc201 to create VMs. the VMs are: 192.168.153.2 (on host cc201) 192.168.153.4 (on host cc202) 192.168.153.5 (on host cc202) 192.168.153.6 (on host cc202) 192.168.155.2 (on host cc201) 192.168.155.3 (on host cc201) 192.168.155.4 (on host cc202)

I log on one of them to ping another of them and capture packets through eth1(eth1 interface the openvswitch port on both of my hosts cc201 and cc202, by using command ovs-vsctl add-port eth1 br-int), results are as below:

I run tcpdump -i eth1 -v -w to capture and save packets when I log on 192.168.153.2 (on cc201, in vlan6): ping 192.168.153.4 (on cc202, in vlan6): (result is they connected) on eth1 of cc201:I can see vlan 6 tag in ICMP request and reply, it is what I expected on eth1 of cc202:I can see vlan 6 tag in ICMP request and reply, it is what I expected

when I log on 192.168.153.2 (on cc201, in vlan 6): ping 192.168.155.2 (on cc201, in vlan8): (result is they are not connected) this result is also what I expect

But when I log on 192.168.153.2 (on cc201, in vlan 6) ping 192.168.155.4 (on cc202, in vlan 8): (result is they connected!!!) on eth1 of cc201: I cannot see vlan 6 tag in ICMP, instead, I can see vlan 8 tag in ICMP request and reply!!! on eth1 of cc202: I cannot see vlan 6 tag in ICMP, instead, I can see vlan 8 tag in ICMP request and reply!!! another words, it has the wrong vlan tag! (expect 6 but actually 8!)

so what happened ? Is this a known bug of quantum or openvswitch?

more details is as below: 1)nova config on cc201: nova.conf--http://paste.openstack.org/show/18588/ nova-compute.conf--http://paste.openstack.org/show/18589/ 2)nova config on cc202: nova.conf--http://paste.openstack.org/show/18590/ nova-compute.conf--http://paste.openstack.org/show/18591/ 3)other command results on cc201--http://paste.openstack.org/show/18592/ 4)other command results on cc202--http://paste.openstack.org/show/18593/

edit retag flag offensive close merge delete

28 answers

Sort by » oldest newest most voted
0

answered 2012-07-18 10:27:59 -0500

Hi Stackers-

I'm bringing up openstack with quantum and OVS.

Can any one guide me on bringing up VM with support of Quantum+OVS+VLan.

Thanking you


Trinath S

edit flag offensive delete link more
0

answered 2012-07-06 01:06:02 -0500

guestly gravatar image

Thanks mizumoto, that solved my question.

edit flag offensive delete link more
0

answered 2012-06-28 09:39:12 -0500

I think that should not effect (2nd one is meaningless) because all gw- interface located on actual nova-network (1st, configured) host.

mizumoto

edit flag offensive delete link more
0

answered 2012-06-26 00:57:25 -0500

guestly gravatar image

To mizumoto, I found that your configuration files are not the same at the parameter routing_source_ip(one is 0.0.0.0 and the other is a actual IP address).

edit flag offensive delete link more
0

answered 2012-06-21 09:40:12 -0500

guestly gravatar image

OK. Thanks. Next four days, I have vocation. I will update my information as soon as possible! I think it is normal that not connect via ssh/ping, if it connects, the problem will appear again.

edit flag offensive delete link more
0

answered 2012-06-21 08:48:00 -0500

I use dashboard to access each VNC console. But it's same situation that from controller of nova-network could not connect via ssh/ping to each VM with routing_source_ip set 0.0.0.0.

I think the problem is some mismatch between floating nat setting and iptables among multiple hypervisor. Could you test more with specific scenario and raise this as another problem even if you set correct nova network and floating related configuration?

I will send the conf file later.

mizumoto

edit flag offensive delete link more
0

answered 2012-06-21 08:09:48 -0500

guestly gravatar image

Plus, to mizumoto: May I ask what kind of method do you access each VM? I found that after adding the rule: routing_source_ip=0.0.0.0, I cannot ping the VM IP address on my physical host. So I access by virsh list virsh vncdisplay and use vnc tools to access VMs, I found the problem disappear!

What about your method to access VM?

edit flag offensive delete link more
0

answered 2012-06-21 07:54:27 -0500

guestly gravatar image

I've change my setting as yours: routing_source_ip=0.0.0.0 but this problem still exists.

Can you paste your nova.conf configuration?

edit flag offensive delete link more
0

answered 2012-06-21 06:48:37 -0500

guestly gravatar image

hi mizumoto, Thanks a lot for your consecutive reply! You mean in nova.conf you set routing_source_ip=0.0.0.0 ?

edit flag offensive delete link more
0

answered 2012-06-21 05:36:03 -0500

In my environment, the below routing_source_ip setting of nova.conf disabled the floating nat of iptables (nova-network-float-snat). This is you mentioned above.


nova.conf

--routing_source_ip=0.0.0.0

With changing this value, and restart nova-network will change snat of iptables. http://paste.openstack.org/show/18677/

Then, the network had separated in my environment. That is, the vm can communicate with other vm only in same network. So floating IP setting will change behaviour. I'm not sure which setting will be reasonable in this kind of environment, but I think you don't need reinstall for this.

mizumoto

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: 2012-06-19 08:40:10 -0500

Seen: 209 times

Last updated: Jul 18 '12