Can't ping gateway of tenant router....

are you running the quantum-ovs-agent on both the compute and the controller node?

if you are using tunnel mode, I would expect to see a tunnel port in your ovs-vsctl output.

Ya, I am using tunneling. You are right. I do not see a tunnel established. I'm at a loss. Not seeing anything useful in /var/log/quantum/openvswitch-agent.log on either the controller or compute node.

quantum 2842 1 1 14:55 ? 00:05:57 python /usr/bin/quantum-openvswitch-agent --config-file=/etc/quantum/quantum.conf --config-file=/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini --log-file=/var/log/quantum/openvswitch-agent.log
root 3852 6831 0 23:30 pts/2 00:00:00 grep --color=auto ovs

^Thats running on the controller

root@ComputeNode1:~# service quantum-plugin-openvswitch-agent start
quantum-plugin-openvswitch-agent start/running, process 26738

^Compute Node
______________________________
 [OVS]
# network_vlan_ranges =
tunnel_id_ranges = 1:1000
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 10.1.1.2
enable_tunneling = True
# [AGENT]
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf

^Output from /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini on (Compute Node)

# [OVS]
tenant_network_type = gre
# network_vlan_ranges =
tunnel_id_ranges = 1:1000
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 10.1.1.1
enable_tunneling = True
# [AGENT]
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf

^Output from /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini on (Controller)

Local IP was wrong, I changed it restarted services on both compute and controller, still not seeing it up. I'm at a loss. Getting close though.

Bridge br-int on control node should have patch-tun or something in br-int.
In addition, we should see br-tun bridge too on your control node.

we need to create br-tun manually
ovs-vsctl add-br br-tun

Alright, that didn't work. But that's ok. Before I go adding things again. I have a question. If I were to ping the gateway that is on the layer 3 agent. What is the actual path of interfaces both physical and logical that data will go through? Is the br-tun in both bridges on the ComputeNode and on the node running the layer 3 agent? I tried adding it and it didn't work. Restarted agents and it still didn't work. If someone can amend the diagram I have below to reflect the correct flow of traffic I would appreciate it.

ComputeNode Node running Layer3 agent
(vNic------->br-int------>eth1)-----GRE TUNNEL-----------(eth1-----br-int------qr-1549a07f-3a)

The interfaces on the left side are on the ComputeNode, and on the right side are the interfaces on the layer 3 agent.

I am facing the same problem here. I also use the gre and tunnel approach, but I have a controller node and a network node separately, the vm can ping neither the gateway nor external ip.

even if I get into the subnet, it's impossible to ping vms:

root@netnode:/etc/quantum# ip netns exec qrouter-a6298ee9-2857-4067-81a8-f050fea7e24d bash
root@netnode:/etc/quantum# ifconfig
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:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:784 (784.0 B) TX bytes:784 (784.0 B)

qg-3aa46fc9-6a Link encap:Ethernet HWaddr fa:16:3e:db:06:1f
          inet addr:192.168.3.163 Bcast:192.168.3.175 Mask:255.255.255.240
          inet6 addr: fe80::f816:3eff:fedb:61f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1511 errors:0 dropped:53 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:161443 (161.4 KB) TX bytes:1152 (1.1 KB)

qr-4d2e8b60-33 Link encap:Ethernet HWaddr fa:16:3e:f2:1c:48
          inet addr:10.0.20.1 Bcast:10.0.20.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fef2:1c48/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:308 (308.0 B) TX bytes:468 (468.0 B)

qr-cd43bdb6-1c Link encap:Ethernet HWaddr fa:16:3e:11:52:0b
          inet addr:10.0.10.1 Bcast:10.0.10.255 Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe11:520b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:308 (308.0 B) TX bytes:468 (468.0 B)

root@netnode:/etc/quantum# ping 10.0.20.3
PING 10.0.20.3 (10.0.20.3) 56(84) bytes of data.
From 10.0.20.1 icmp_seq=1 Destination Host Unreachable
From 10.0.20.1 icmp_seq=2 Destination Host Unreachable
From 10.0.20.1 icmp_seq=3 Destination Host Unreachable
From 10.0.20.1 icmp_seq=4 Destination Host Unreachable
From 10.0.20.1 icmp_seq=5 Destination Host Unreachable

i fixed my problem by removing a incorrect ip "10.0.0.3" from br-tun
root@node1:~# ovs-vsctl show
3b78ade3-870b-40d1-80cb-dc8be59a2b85
    Bridge br-tun
        Port "gre-2"
            Interface "gre-2"
                type: gre
                options: {in_key=flow, out_key=flow, remote_ip="10.0.0.3"}
        Port "gre-9"
            Interface "gre-9"
                type: gre
                options: {in_key=flow, out_key=flow, remote_ip="192.168.3.142"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}

the following command fixes the problem:
ovs-vsctl del-port br-tun gre-2

it should be:
vNic->br-int->patch-tun ->patch-int ->gre gre -> patch-int->patch-tun->br-int->qr-1549a07f-3a

Ok, this is something with the agent on the compute node. To install the openvswitch plugin on the compute node is this the only package I'm installing ---"apt-get install -y quantum-plugin-openvswitch-agent", because when I installed other quantum packages I noticed a python-pyparsing package was installed. Do I need that to successfully install and run the openvswitch agent? For some reason when I do a "ps -ef | grep quantum" on the compute node I'm not seeing it running.....

you can try to run quantum-openvswitch-agent --config-file /etc/quantum.conf --config-file /etc/quantum/xxxx/ovs.ini --debug true and get the log to see what is happening.

Got it. Something was wrong with the ovs_quantum_plugin.ini file. There was a space before [OVS]. Thanks for that command.

Thanks yong sheng gong, that solved my question.

Sorry problem still exists. Good news is it looks like the arp is trying to go over the gre tunnel. The problem is, the gre endpoint is not responding to the arp request. So here's what I have

Controller - Private IP - eth1 - 10.1.1.1
Compute Node - Private IP - eth1 - 10.1.1.2

OVS Configuration - Controller
root@controller:~# ovs-vsctl show
195ff79e-e01a-4e93-84bc-868d8782f284
    Bridge br-ex
        Port "qg-2b9a29bb-4b"
            Interface "qg-2b9a29bb-4b"
                type: internal
        Port "eth2"
            Interface "eth2"
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap882a8e75-ee"
            tag: 1
            Interface "tap882a8e75-ee"
                type: internal
        Port "tap4265fa27-08"
            tag: 4095
            Interface "tap4265fa27-08"
                type: internal
        Port "eth1"
            Interface "eth1"
        Port br-int
            Interface br-int
                type: internal
        Port "qr-1549a07f-3a"
            tag: 4095
            Interface "qr-1549a07f-3a"
                type: internal
    ovs_version: "1.4.0+build0"

OVS Configuration - ComputeNode1
root@ComputeNode1:~# ovs-vsctl show
331fd29b-b70f-4f54-983a-d6749f8cf1ed
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qvo002cc4c6-47"
            tag: 1
            Interface "qvo002cc4c6-47"
        Port br-int
            Interface br-int
                type: internal
    Bridge br-tun
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {in_key=flow, out_key=flow, remote_ip="10.1.1.1"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    ovs_version: "1.4.0+build0"

When I ping from the vm private ip of 10.5.5.3 to the gateway I have setup that lives on the l3 agent on the controller. Eth1 on the compute node will arp for eth1s ip on the controller. But eth1 on the controller isn't responding. Refer to the output below. I am seeing a gre port configured on the compute node but I am not seeing one configured on the controller even though my ovs configuration is fine. Refer to the output on the very bottom. Agents are running on both controller and compute node. Any help would be appreciated.

root@controller:~# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
12:00:55.884644 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 46
12:00:56.880832 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 46
12:00:57.880824 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 46

[OVS]
tenant_network_type = gre
# network_vlan_ranges =
tunnel_id_ranges = 1:1000
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 10.1.1.1
enable_tunneling = True
[AGENT]
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf

Anyone have any thoughts on this one?

I am running ubuntu 12.04, and I followed this guide for installing folsom http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html

I got it. Final ovs configuration listed below. Thanks for the help.

Controller
_________________________________________
root@controller:~# ovs-vsctl show
195ff79e-e01a-4e93-84bc-868d8782f284
    Bridge br-ex
        Port "qg-2b9a29bb-4b"
            Interface "qg-2b9a29bb-4b"
                type: internal
        Port "eth2"
            Interface "eth2"
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {remote_ip="10.1.1.2"}
        Port "tap8320bbe5-23"
            tag: 2
            Interface "tap8320bbe5-23"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap882a8e75-ee"
            tag: 1
            Interface "tap882a8e75-ee"
                type: internal
        Port "tap4265fa27-08"
            tag: 4095
            Interface "tap4265fa27-08"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "qr-1549a07f-3a"
            tag: 4095
            Interface "qr-1549a07f-3a"
                type: internal
    ovs_version: "1.4.0+build0"

Compute Node
__________________________________________
root@ComputeNode1:~# ovs-vsctl show
331fd29b-b70f-4f54-983a-d6749f8cf1ed
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qvo235c2e1a-dd"
            tag: 1
            Interface "qvo235c2e1a-dd"
        Port "qvo002cc4c6-47"
            tag: 1
            Interface "qvo002cc4c6-47"
        Port "qvo984554c8-98"
            tag: 3
            Interface "qvo984554c8-98"
        Port br-int
            Interface br-int
                type: internal
    Bridge br-tun
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {in_key=flow, out_key=flow, remote_ip="10.1.1.1"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    ovs_version: "1.4.0+build0"

Thanks yong sheng gong, that solved my question.