Ask Your Question

guestly's profile - activity

2016-10-20 20:44:31 -0600 received badge  Famous Question (source)
2016-04-13 10:10:18 -0600 received badge  Notable Question (source)
2016-04-13 10:10:18 -0600 received badge  Popular Question (source)
2016-03-31 14:38:41 -0600 received badge  Famous Question (source)
2016-03-23 21:08:09 -0600 received badge  Popular Question (source)
2016-03-23 21:08:09 -0600 received badge  Famous Question (source)
2016-03-23 21:08:09 -0600 received badge  Notable Question (source)
2014-12-22 04:23:59 -0600 received badge  Notable Question (source)
2014-10-13 00:57:36 -0600 received badge  Popular Question (source)
2014-10-13 00:57:36 -0600 received badge  Notable Question (source)
2014-09-24 04:29:41 -0600 received badge  Popular Question (source)
2012-07-20 03:40:18 -0600 answered a question quantum/ovs not working after reboot of the host

I have a similar problem. But my version is new enough, and after reboot the host, the dnsmasq service is start also. But the problem still exist! Here is my problem link: https://answers.launchpad.net/quantum/+question/203474 (https://answers.launchpad.net/quantum...)

2012-07-10 01:13:12 -0600 answered a question Are there any handles of DB transaction of current version Quantum?

Thanks Salvatore Orlando, that solved my question.

2012-07-09 01:16:27 -0600 answered a question Are there any handles of DB transaction of current version Quantum?

Thanks Salvatore, Batch API create/delete as the bug report says is one aspect of the problem of integrity of data. But I mentioned in my question is just one API call. It may be involved serial DB APIs call, and I mean these DB APIs call should act atomicly.

2012-07-06 09:31:08 -0600 asked a question Are there any handles of DB transaction of current version Quantum?

Currently, run an instance for example, will write the DB several times, if there aren't DB transactions between these DB writings, there may be many problems after that. So are there any handlings or plans to use DB transaction to avoid such problems?

2012-07-06 01:07:11 -0600 answered a question Nova+Quantum+Openvswitch, two physical hosts, create VM, error

Thanks Somik Behera, that solved my question.

2012-07-06 01:06:40 -0600 answered a question Two networks, one is reachable, the other is not. Why?

Thanks Somik Behera, that solved my question.

2012-07-06 01:06:02 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Thanks mizumoto, that solved my question.

2012-07-06 01:00:47 -0600 answered a question A question about ovs-vlan-test

Thanks dan wendlandt, that solved my question.

2012-07-05 08:50:32 -0600 asked a question A question about ovs-vlan-test

What is ovs-vlan-test(ovs-test)'s purpose? What can it prove? The document says that there must be a host proved no problem with vlan as server, to test a host whether it has vlan problem as client. But how do I find this no problem host? Do both of ovs-vlan-test server and client can run on one single host to prove this host doesnot have vlan problem?

Another question, if there are two VMs in the same VLAN and they're on the same physical host, when I ping from VM1 to VM2, and I can be connected, does the ICMP packet go through the physical ethernet interface card or just go within the openvswitch not through the physical ethernet interface card?

2012-07-04 07:41:53 -0600 answered a question Suppose that Controller, Network and Compute node are at seperate physical host, is Quantum+OVS needed on Network node?

Thanks dan wendlandt, that solved my question.

2012-07-04 07:03:34 -0600 asked a question Suppose that Controller, Network and Compute node are at seperate physical host, is Quantum+OVS needed on Network node?

I made an evironment as Nova Controller + Nova Network + Nova Compute on one physical host, but if I need a distributed environment and want to make Nova Controller, Nova Network and Nova Compute seperate from each other. So Quantum+OVS must be installed on Nova Compute node, is it needed to be installed on Nova-network node or Nova-Controller node? Thanks.

2012-06-26 00:57:25 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

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).

2012-06-21 09:40:12 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

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.

2012-06-21 08:09:48 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

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?

2012-06-21 07:54:27 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

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?

2012-06-21 06:48:37 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

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

2012-06-21 04:42:58 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

"So in this viewpoint, nova configuration, iptables, or some other thing was wrong I think." I agree with this point of view. on the same hypervisor, the result is not connected, but on the different hypervisor, it is connected. I had reported this problem in bugs series, but I don't know who will tell us the result.

I will reinstall my environment and have a try. If this time the problem is not resolved, I think waiting for someone to analyze and resolve it is the best choice for us.

2012-06-21 03:58:03 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Yes, in my case, the packets' path is just like: cc201:192.168.153.2(tap)--->br-int-->(gw)192.168.153.1--->(gw)192.168.155.1--->br-int--->cc201:eth1---> ---->[tag:8]--sw--[tag:8]---> --->cc202:eth1--->br-int--->(tap)cc202:192.168.155.2

But, I mean 192.168.153.2 is under network 192.168.153.0/24, it is vlan6 not vlan8, why it has tag8(vlan8's tag) finally? I mean if openvswitch know icmp's source is a vlan6 VM, and its destination is a vlan8 VM, the ovs should prevent the vlan6 packets to access and drop it. Do I have the correct understanding?

2012-06-21 01:26:01 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

to mizumoto: "source IP address has changed (NAT or routing_source_ip of nova.conf?) "

I have something similar with you before. I think this because the nova-network add a rule like: -A nova-network-snat -s 192.168.151.0/24 -j SNAT --to-source 10.131.0.31

I delete this rule. And thus, the source address won't be changed.

This is one of the problems, but I think it is not critical.

The critical problem also is why the vlan tag wrong or another words why it is connected between different gw*s?

2012-06-21 01:16:19 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

"I checked adding iptable entry manually, it could block the packet among networks." Hmmm, I understand what you do. But should it be quantum's work? If we must add iptable entry to solve this problem manually, it will be a few entries when there are many networks! So I think there must somthing wrong with Quantum or Openvswitch. But I've never seen otherone reporting them:-(

But why I ping from networkA(on cc201) to networkB(also on cc201), the vlan can block the ping packets?

this morning, I checked the command iptables-save, and found these rules, do they have some relation with this problem?

-A nova-compute-local -d 192.168.153.2/32 -j nova-compute-inst-6 -A nova-compute-local -d 192.168.155.2/32 -j nova-compute-inst-22 -A nova-compute-local -d 192.168.155.3/32 -j nova-compute-inst-23 -A nova-compute-local -d 192.168.153.8/32 -j nova-compute-inst-26 -A nova-compute-local -d 192.168.153.9/32 -j nova-compute-inst-27 -A nova-compute-sg-fallback -j DROP -A nova-filter-top -j nova-compute-local -A nova-filter-top -j nova-network-local -A nova-filter-top -j nova-manage-local -A nova-filter-top -j nova-api-local -A nova-network-FORWARD -i br-int -j ACCEPT -A nova-network-FORWARD -o br-int -j ACCEPT -A nova-network-INPUT -i gw-e7863e30-1c -p udp -m udp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-e7863e30-1c -p tcp -m tcp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-e7863e30-1c -p udp -m udp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-e7863e30-1c -p tcp -m tcp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-87a6f352-35 -p udp -m udp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-87a6f352-35 -p tcp -m tcp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-87a6f352-35 -p udp -m udp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-87a6f352-35 -p tcp -m tcp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-3faffe59-5d -p udp -m udp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-3faffe59-5d -p tcp -m tcp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-3faffe59-5d -p udp -m udp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-3faffe59-5d -p tcp -m tcp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-6d53af57-d9 -p udp -m udp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-6d53af57-d9 -p tcp -m tcp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-6d53af57-d9 -p udp -m udp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-6d53af57-d9 -p tcp -m tcp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-9a2757f4-2d -p udp -m udp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-9a2757f4-2d -p tcp -m tcp --dport 67 -j ACCEPT -A nova-network-INPUT -i gw-9a2757f4-2d -p udp -m udp --dport 53 -j ACCEPT -A nova-network-INPUT -i gw-9a2757f4-2d -p tcp -m tcp --dport 53 -j ACCEPT

2012-06-20 12:37:56 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

And, "Among 2 nova-network communication is controlled by iptables. " May I ask how do you set your iptables configuration? And, "I changed security group setting to pass ICMP, each VM could communicate with other network." What does your security group setting look like?

2012-06-20 12:34:28 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

mizumoto: Thanks for your reply! From your paste, you created two networks (two vlans), one is 172.15.3.0, the other is 172.15.5.0. If vlan does works, these two networks should not be connected! In other words, if you log on 172.15.5.3 to ping 172.15.5.5, it is connected-----It is right! If you log on 172.15.5.3 to ping 172.15.3.3 or 172.15.3.2, both of the two result should be not connected! But your test result is similar with mine. I don't know why~~

2012-06-20 09:34:24 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Network 192.168.153.0/24 has vlan6; Network 192.168.155.0/24 has vlan8.

2012-06-20 09:31:01 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Yes, after that, I created moure VM. But I think it is not concern with the problem. Do you think so?

2012-06-20 08:34:40 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Thanks to mizumoto for your reply? But why I ping from 192.168.153.2(on cc201, vlan 6) to 192.168.155.2(on cc201, vlan 8), it is not connected? Is it because they are on the same physical host? If so, how can I make VLAN work? What should I do?

Because I the image I use is simple tty-linux, so the information may be not detail. If you need more informations, just tell me! Routing tables of VMs are as below: 1) on 192.168.153.2: $ route
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.153.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.153.1 0.0.0.0 UG 0 0 0 eth0

2)on 192.168.155.4: $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.155.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.155.1 0.0.0.0 UG 0 0 0 eth0

3) cc201 ovs-vsctl:

ovs-vsctl show

974585a6-2b5b-4bea-be4a-3127f71007bf Bridge vlan-test-br Port vlan-test-br Interface vlan-test-br type: internal Bridge br-int Port "gw-87a6f352-35" tag: 4 Interface "gw-87a6f352-35" type: internal Port "gw-e7863e30-1c" tag: 6 Interface "gw-e7863e30-1c" type: internal Port "tap908304d1-d1" tag: 8 Interface "tap908304d1-d1" Port "gw-6d53af57-d9" tag: 8 Interface "gw-6d53af57-d9" type: internal Port "tap1585a714-10" tag: 6 Interface "tap1585a714-10" Port br-int Interface br-int type: internal Port "eth1" Interface "eth1" Port "gw-3faffe59-5d" tag: 5 Interface "gw-3faffe59-5d" type: internal Port "tap09ae4556-2b" tag: 8 Interface "tap09ae4556-2b" Port "tap77918099-5a" tag: 6 Interface "tap77918099-5a" Port "tap6011d326-33" tag: 6 Interface "tap6011d326-33" Port "gw-9a2757f4-2d" tag: 7 Interface "gw-9a2757f4-2d" type: internal ovs_version: "1.4.0+build0"

4) cc201 ifconfig:

ifconfig

br-int Link encap:Ethernet HWaddr 00:1b:21:c6:35:a6
inet6 addr: fe80::21b:21ff:fec6:35a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10524930 errors:0 dropped:0 overruns:0 frame:0 TX packets:9110 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:714364025 (714.3 MB) TX bytes:783412 (783.4 KB)

eth0 Link encap:Ethernet HWaddr d0:67:e5:23:96:d4
inet addr:10.131.0.31 Bcast:10.131.255.255 Mask:255.252.0.0 inet6 addr: fe80::d267:e5ff:fe23:96d4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3473405 errors:0 dropped:0 overruns:0 frame:0 TX packets:2372097 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:694315585 (694.3 MB) TX bytes:1224320432 (1.2 GB) Interrupt:43 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 00:1b:21:c6:35:a6
inet6 addr: fe80::21b:21ff:fec6:35a6/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:10906571 errors:0 dropped:0 overruns:0 frame:0 TX packets:99047 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:814630415 (814.6 MB) TX ...
(more)

2012-06-20 08:34:37 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

Thanks to mizumoto for your reply? But why I ping from 192.168.153.2(on cc201, vlan 6) to 192.168.155.2(on cc201, vlan 8), it is not connected? Is it because they are on the same physical host? If so, how can I make VLAN work? What should I do?

Because I the image I use is simple tty-linux, so the information may be not detail. If you need more informations, just tell me! Routing tables of VMs are as below: 1) on 192.168.153.2: $ route
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.153.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.153.1 0.0.0.0 UG 0 0 0 eth0

2)on 192.168.155.4: $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.155.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.155.1 0.0.0.0 UG 0 0 0 eth0

3) cc201 ovs-vsctl:

ovs-vsctl show

974585a6-2b5b-4bea-be4a-3127f71007bf Bridge vlan-test-br Port vlan-test-br Interface vlan-test-br type: internal Bridge br-int Port "gw-87a6f352-35" tag: 4 Interface "gw-87a6f352-35" type: internal Port "gw-e7863e30-1c" tag: 6 Interface "gw-e7863e30-1c" type: internal Port "tap908304d1-d1" tag: 8 Interface "tap908304d1-d1" Port "gw-6d53af57-d9" tag: 8 Interface "gw-6d53af57-d9" type: internal Port "tap1585a714-10" tag: 6 Interface "tap1585a714-10" Port br-int Interface br-int type: internal Port "eth1" Interface "eth1" Port "gw-3faffe59-5d" tag: 5 Interface "gw-3faffe59-5d" type: internal Port "tap09ae4556-2b" tag: 8 Interface "tap09ae4556-2b" Port "tap77918099-5a" tag: 6 Interface "tap77918099-5a" Port "tap6011d326-33" tag: 6 Interface "tap6011d326-33" Port "gw-9a2757f4-2d" tag: 7 Interface "gw-9a2757f4-2d" type: internal ovs_version: "1.4.0+build0"

4) cc201 ifconfig:

ifconfig

br-int Link encap:Ethernet HWaddr 00:1b:21:c6:35:a6
inet6 addr: fe80::21b:21ff:fec6:35a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10524930 errors:0 dropped:0 overruns:0 frame:0 TX packets:9110 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:714364025 (714.3 MB) TX bytes:783412 (783.4 KB)

eth0 Link encap:Ethernet HWaddr d0:67:e5:23:96:d4
inet addr:10.131.0.31 Bcast:10.131.255.255 Mask:255.252.0.0 inet6 addr: fe80::d267:e5ff:fe23:96d4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3473405 errors:0 dropped:0 overruns:0 frame:0 TX packets:2372097 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:694315585 (694.3 MB) TX bytes:1224320432 (1.2 GB) Interrupt:43 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 00:1b:21:c6:35:a6
inet6 addr: fe80::21b:21ff:fec6:35a6/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:10906571 errors:0 dropped:0 overruns:0 frame:0 TX packets:99047 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:814630415 (814.6 MB) TX ...
(more)

2012-06-19 09:25:59 -0600 answered a question Also Nova+Quantum+Openvswitch VLAN Problem!

output of the second capture of packets (ping from 192.168.153.2 in vlan 6 on cc201 to 192.168.155.4 in vlan 8 on cc202):

in_port(7),eth(src=fa:16:3e:1a:95:5b,dst=fa:16:3e:7f:6e:64),eth_type(0x0800),ipv4(src=192.168.153.2,dst=192.168.155.4,proto=1,tos=0,ttl=64,frag=no),icmp(type=8,code=0), packets:20, bytes:1960, used:0.192s, actions:6 in_port(1),eth(src=24:b6:57:f3:56:0b,dst=01:00:0c:cc:cc:cd),eth_type(0x8100),vlan(vid=26,pcp=7),encap(), packets:4549, bytes:291136, used:1.396s, actions:0 in_port(1),eth(src=54:52:48:00:08:13,dst=33:33:ff:00:08:13),eth_type(0x86dd),ipv6(src=fe80::5652:48ff:fe00:813,dst=ff02::1:ff00:813,label=0,proto=58,tclass=0,hlimit=1,frag=no),icmpv6(type=131,code=0), packets:0, bytes:0, used:never, actions:0 in_port(19),eth(src=fa:16:3e:22:d7:40,dst=fa:16:3e:1b:cf:e2),eth_type(0x0800),ipv4(src=192.168.153.2,dst=192.168.155.4,proto=1,tos=0,ttl=63,frag=no),icmp(type=8,code=0), packets:20, bytes:1960, used:0.192s, actions:push_vlan(vid=8,pcp=0),1

It says that operation push_vlan put the packets with tag 8 not tag 6!! I suppose it is the reason why two VMs from different vlan can ping connected!

But why???

2012-06-19 08:40:10 -0600 asked a question Also Nova+Quantum+Openvswitch VLAN Problem!

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/

2012-06-19 07:39:55 -0600 answered a question When I start a VM, why it has "two" processes related with it?

Thanks dan wendlandt, that solved my question.

2012-06-19 01:01:14 -0600 answered a question When I start a VM, why it has "two" processes related with it?

Thanks Dan! But furthermore, what is the purpose of doing this? Does this situation only appear in nova or in any cases? When requests of DHCP client for IP address arrive, which process replies them, the parent or the child?

2012-06-18 08:05:56 -0600 asked a question When I start a VM, why it has "two" processes related with it?

I start sever VMs by Nova+Quantum+Openvswitch environment, here is result of execute command ps -ef:

ps -ef | grep dnsmasq

nobody 10008 1 0 Jun15 ? 00:00:13 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 10009 10008 0 Jun15 ? 00:00:05 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 22662 1891 0 15:42 pts/12 00:00:00 grep --color=auto dnsmasq nobody 27412 1 0 Jun15 ? 00:00:11 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27413 27412 0 Jun15 ? 00:00:01 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro nobody 27825 1 0 Jun15 ? 00:00:12 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27826 27825 0 Jun15 ? 00:00:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro

for each gw*, it has a process of dnsmasq(i.e. pid=10008) and the other process(i.e.pid=10009 and ppid=10008), why?

2012-05-18 02:07:15 -0600 answered a question Nova+Quantum+Openvswitch, two physical hosts, create VM, error

I replace the nova.conf file with https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf (https://lists.launchpad.net/openstack...) mentioned, and now nova-compute server doesn't work on my second physical host essex-2! nova-compute.log:

2012-05-18 09:53:37 CRITICAL nova [-] Unable to read from monitor: Connection reset by peer 2012-05-18 09:53:37 TRACE nova Traceback (most recent call last): 2012-05-18 09:53:37 TRACE nova File "/usr/bin/nova-compute", line 49, in <module> 2012-05-18 09:53:37 TRACE nova service.wait() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/service.py", line 413, in wait 2012-05-18 09:53:37 TRACE nova _launcher.wait() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/service.py", line 131, in wait 2012-05-18 09:53:37 TRACE nova service.wait() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait 2012-05-18 09:53:37 TRACE nova return self._exit_event.wait() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait 2012-05-18 09:53:37 TRACE nova return hubs.get_hub().switch() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch 2012-05-18 09:53:37 TRACE nova return self.greenlet.switch() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main 2012-05-18 09:53:37 TRACE nova result = function(args, *kwargs) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/service.py", line 101, in run_server 2012-05-18 09:53:37 TRACE nova server.start() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/service.py", line 162, in start 2012-05-18 09:53:37 TRACE nova self.manager.init_host() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 247, in init_host 2012-05-18 09:53:37 TRACE nova self.reboot_instance(context, instance['uuid']) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped 2012-05-18 09:53:37 TRACE nova return f(args, *kw) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 153, in decorated_function 2012-05-18 09:53:37 TRACE nova function(self, context, instance_uuid, args, *kwargs) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 177, in decorated_function 2012-05-18 09:53:37 TRACE nova sys.exc_info()) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-05-18 09:53:37 TRACE nova self.gen.next() 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 171, in decorated_function 2012-05-18 09:53:37 TRACE nova return function(self, context, instance_uuid, args, *kwargs) 2012-05-18 09:53:37 TRACE nova File "/usr/lib/python2.7/dist-packages ... (more)

2012-05-18 01:21:51 -0600 answered a question Nova+Quantum+Openvswitch, two physical hosts, create VM, error

I just follow this https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf (https://lists.launchpad.net/openstack...) instructions, but has that result :-(

2012-05-17 08:41:18 -0600 asked a question Nova+Quantum+Openvswitch, two physical hosts, create VM, error

I have two physical hosts, to create Nova+Quantum+Openvswitch. Both of the two hosts are installed all nova services. cc202 is the controller node and cc201 is the compute node. cc202:

nova-manage service list

2012-05-17 16:01:51 DEBUG nova.utils [req-9c491041-a017-4b74-97eb-57325ceb3963 None None] backend <module 'nova.db.sqlalchemy.api'="" from="" '="" usr="" lib="" python2.7="" dist-packages="" nova="" db="" sqlalchemy="" api.pyc'=""> from (pid=5151) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Binary Host Zone Status State Updated_At nova-compute cc202 nova enabled :-) 2012-05-17 08:01:32 nova-network cc202 nova enabled :-) 2012-05-17 08:01:47 nova-scheduler cc202 nova enabled :-) 2012-05-17 08:01:47 nova-consoleauth cc202 nova enabled :-) 2012-05-17 08:01:47 nova-scheduler cc201 nova enabled :-) 2012-05-17 08:01:47 nova-compute cc201 nova enabled :-) 2012-05-17 08:01:50 nova-network cc201 nova enabled :-) 2012-05-17 08:01:47

cc201:

nova-manage service list

2012-05-17 16:02:25 DEBUG nova.utils [req-fd82780f-1ca1-4ca3-9d01-e4c9a14998b4 None None] backend <module 'nova.db.sqlalchemy.api'="" from="" '="" usr="" lib="" python2.7="" dist-packages="" nova="" db="" sqlalchemy="" api.pyc'=""> from (pid=27584) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Binary Host Zone Status State Updated_At nova-compute cc202 nova enabled :-) 2012-05-17 08:02:15 nova-network cc202 nova enabled :-) 2012-05-17 08:02:17 nova-scheduler cc202 nova enabled :-) 2012-05-17 08:02:17 nova-consoleauth cc202 nova enabled :-) 2012-05-17 08:02:17 nova-scheduler cc201 nova enabled :-) 2012-05-17 08:02:17 nova-compute cc201 nova enabled :-) 2012-05-17 08:02:24 nova-network cc201 nova enabled :-) 2012-05-17 08:02:17

is that normal? all services except nova-consoleauth had been double created! And when I created VM on cc202, It wasn't successful.

2012-05-17 05:49:36 -0600 answered a question Two networks, one is reachable, the other is not. Why?

To Somik Behera, Thanks for your reply. To Dan, still waiting for your reply.~

2012-05-17 01:34:38 -0600 answered a question Two networks, one is reachable, the other is not. Why?

To Dan, Yes, I log in this VM, and ifconfig it, it has two vNIC, eth0 and eth1, and both of them has correct IP address.

2012-05-17 01:32:36 -0600 answered a question Two networks, one is reachable, the other is not. Why?

To Somik Behera (somikbehera) , Since you have created both of these networks as "shared"/public networks, any VM on any network can ping the gateways, which is what you are seeing.

how do you see both of these networks are public networks?

I use nova DHCP to create IP address.

2012-05-17 01:29:50 -0600 answered a question Two networks, one is reachable, the other is not. Why?

I have similar problem with another problem: I also have this problem. I founded that my iptables has a new rule after I created a network 192.168.208.0/24 and a VM 8.8.8.6/192.168.208.2, and I can ping 8.8.8.6 but cannot 192.168.208.2 :

-A nova-manage-snat -s 192.168.208.0/24 -j SNAT --to-source 10.131.0.244

when I delete this rule, I can ping 192.168.208.2, and when I create a new network and new VM, this rule was replaced by the new network.

As below, are my iptables rules BEFORE CREATING NETWORK, AFTER CREATING NETWORK and AFTER CREATING VM:

BEFORE CREATING NETWORK:

Generated by iptables-save v1.4.12 on Wed May 16 14:51:31 2012

*mangle :PREROUTING ACCEPT [245736:216294003] :INPUT ACCEPT [57864:32422084] :FORWARD ACCEPT [184175:182659303] :OUTPUT ACCEPT [53384:31506313] :POSTROUTING ACCEPT [237564:214167256] -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill COMMIT

Completed on Wed May 16 14:51:31 2012

Generated by iptables-save v1.4.12 on Wed May 16 14:51:31 2012

*nat :PREROUTING ACCEPT [135:35818] :INPUT ACCEPT [54:10054] :OUTPUT ACCEPT [22:1351] :POSTROUTING ACCEPT [22:1351] :nova-api-OUTPUT - [0:0] :nova-api-POSTROUTING - [0:0] :nova-api-PREROUTING - [0:0] :nova-api-float-snat - [0:0] :nova-api-snat - [0:0] :nova-compute-OUTPUT - [0:0] :nova-compute-POSTROUTING - [0:0] :nova-compute-PREROUTING - [0:0] :nova-compute-float-snat - [0:0] :nova-compute-snat - [0:0] :nova-manage-OUTPUT - [0:0] :nova-manage-POSTROUTING - [0:0] :nova-manage-PREROUTING - [0:0] :nova-manage-float-snat - [0:0] :nova-manage-snat - [0:0] :nova-network-OUTPUT - [0:0] :nova-network-POSTROUTING - [0:0] :nova-network-PREROUTING - [0:0] :nova-network-float-snat - [0:0] :nova-network-snat - [0:0] :nova-postrouting-bottom - [0:0] -A PREROUTING -j nova-compute-PREROUTING -A PREROUTING -j nova-network-PREROUTING -A PREROUTING -j nova-manage-PREROUTING -A PREROUTING -j nova-api-PREROUTING -A OUTPUT -j nova-compute-OUTPUT -A OUTPUT -j nova-network-OUTPUT -A OUTPUT -j nova-manage-OUTPUT -A OUTPUT -j nova-api-OUTPUT -A POSTROUTING -j nova-compute-POSTROUTING -A POSTROUTING -j nova-network-POSTROUTING -A POSTROUTING -j nova-manage-POSTROUTING -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE -A POSTROUTING -j nova-api-POSTROUTING -A POSTROUTING -j nova-postrouting-bottom -A nova-api-snat -j nova-api-float-snat -A nova-compute-snat -j nova-compute-float-snat -A nova-manage-snat -j nova-manage-float-snat -A nova-manage-snat -s 192.168.207.0/24 -j SNAT --to-source 10.131.0.244 -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 10.131.0.244/32 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 10.128.0.0/24 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 192.168.200.0/24 -m conntrack ! --ctstate DNAT -j ACCEPT -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.131.0.244:8775 -A nova-network-snat -j nova-network-float-snat -A nova-network-snat -s 192.168.200.0/24 -j SNAT --to-source 10.131.0.244 ... (more)

2012-05-17 01:22:00 -0600 answered a question Quantum OVS multiple networks

I also have this problem. I founded that my iptables has a new rule after I created a network 192.168.208.0/24 and a VM 8.8.8.6/192.168.208.2, and I can ping 8.8.8.6 but cannot 192.168.208.2 :

-A nova-manage-snat -s 192.168.208.0/24 -j SNAT --to-source 10.131.0.244

when I delete this rule, I can ping 192.168.208.2, and when I create a new network and new VM, this rule was replaced by the new network.

As below, are my iptables rules BEFORE CREATING NETWORK, AFTER CREATING NETWORK and AFTER CREATING VM:

BEFORE CREATING NETWORK:

Generated by iptables-save v1.4.12 on Wed May 16 14:51:31 2012

*mangle :PREROUTING ACCEPT [245736:216294003] :INPUT ACCEPT [57864:32422084] :FORWARD ACCEPT [184175:182659303] :OUTPUT ACCEPT [53384:31506313] :POSTROUTING ACCEPT [237564:214167256] -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill COMMIT

Completed on Wed May 16 14:51:31 2012

Generated by iptables-save v1.4.12 on Wed May 16 14:51:31 2012

*nat :PREROUTING ACCEPT [135:35818] :INPUT ACCEPT [54:10054] :OUTPUT ACCEPT [22:1351] :POSTROUTING ACCEPT [22:1351] :nova-api-OUTPUT - [0:0] :nova-api-POSTROUTING - [0:0] :nova-api-PREROUTING - [0:0] :nova-api-float-snat - [0:0] :nova-api-snat - [0:0] :nova-compute-OUTPUT - [0:0] :nova-compute-POSTROUTING - [0:0] :nova-compute-PREROUTING - [0:0] :nova-compute-float-snat - [0:0] :nova-compute-snat - [0:0] :nova-manage-OUTPUT - [0:0] :nova-manage-POSTROUTING - [0:0] :nova-manage-PREROUTING - [0:0] :nova-manage-float-snat - [0:0] :nova-manage-snat - [0:0] :nova-network-OUTPUT - [0:0] :nova-network-POSTROUTING - [0:0] :nova-network-PREROUTING - [0:0] :nova-network-float-snat - [0:0] :nova-network-snat - [0:0] :nova-postrouting-bottom - [0:0] -A PREROUTING -j nova-compute-PREROUTING -A PREROUTING -j nova-network-PREROUTING -A PREROUTING -j nova-manage-PREROUTING -A PREROUTING -j nova-api-PREROUTING -A OUTPUT -j nova-compute-OUTPUT -A OUTPUT -j nova-network-OUTPUT -A OUTPUT -j nova-manage-OUTPUT -A OUTPUT -j nova-api-OUTPUT -A POSTROUTING -j nova-compute-POSTROUTING -A POSTROUTING -j nova-network-POSTROUTING -A POSTROUTING -j nova-manage-POSTROUTING -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE -A POSTROUTING -j nova-api-POSTROUTING -A POSTROUTING -j nova-postrouting-bottom -A nova-api-snat -j nova-api-float-snat -A nova-compute-snat -j nova-compute-float-snat -A nova-manage-snat -j nova-manage-float-snat -A nova-manage-snat -s 192.168.207.0/24 -j SNAT --to-source 10.131.0.244 -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 10.131.0.244/32 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 10.128.0.0/24 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.200.0/24 -d 192.168.200.0/24 -m conntrack ! --ctstate DNAT -j ACCEPT -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.131.0.244:8775 -A nova-network-snat -j nova-network-float-snat -A nova-network-snat -s 192.168.200.0/24 -j SNAT --to-source 10.131.0.244 -A nova-network-snat -s 8.8.8.0 ... (more)