Running with two nics for this should be fine for tunneling as ip routing would handle which nic the packets should go out. From what you pasted I see that one HV has a gre tunnel setup to 10.10.10.1 <-- Who is that host? Can you attach your /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini on your nodes.
I suspect the issue is a configuration issue in the [OVS] section. You'll need something along the lines of this in that section: [OVS] local_ip = <ip address of HV> enable_tunneling = True tunnel_id_ranges = 1:1000 tenant_network_type = gre On Fri, Feb 22, 2013 at 9:54 AM, Guilherme Russi <luisguilherme...@gmail.com > wrote: > Hello Aaron, > > Sorry about attaching the infos, about the quantum agent, is it the > quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at > the controller and the compute nodes: > > service quantum-plugin-openvswitch-agent start > start: Job is already running: quantum-plugin-openvswitch-agent > > Is there another thing i should do? I'm running my controller node and > the network node at the same machine with 2 NICs, maybe can be a problem > how i am making my network config? > > Thanks again. > > Guilherme. > > > 2013/2/22 Aaron Rosen <aro...@nicira.com> > >> Hi Guilherme, >> >> (next time please paste these in the email rather than attaching, thx). >> >> From the text in the attachment (show below). It seems like you are not >> running the quantum-openvswitch-agent on your network node as there is no >> GRE tunnel from that to your compute node. Once you have >> quantum-openvswitch-agent running on all your machines you should be able >> to run ovs-dpctl looking under br-tun and see a tunnel between each host. >> >> Aaron >> >> CONTROLLER + NETWORK NODE: >> system@br-tun: >> lookups: hit:0 missed:0 lost:0 >> flows: 0 >> port 0: br-tun (internal) >> port 1: patch-int (patch: peer=patch-tun) >> system@br-int: >> lookups: hit:0 missed:0 lost:0 >> flows: 0 >> port 0: br-int (internal) >> port 1: tap817d2f70-a0 (internal) >> port 2: qr-ea64e9aa-31 (internal) >> port 3: patch-tun (patch: peer=patch-int) >> system@br-ex: >> lookups: hit:0 missed:0 lost:0 >> flows: 0 >> port 0: br-ex (internal) >> port 2: qg-95fe3fa1-d1 (internal) >> >> >> COMPUTE NODES >> >> COMPUTE NODE 01: >> ovs-dpctl show >> system@br-int: >> lookups: hit:380 missed:7590 lost:0 >> flows: 0 >> port 0: br-int (internal) >> port 2: patch-tun (patch: peer=patch-int) >> port 3: qvo981ae82e-d4 >> port 6: qvoc9df3a96-5f >> port 7: qvoc153ac28-ae >> port 8: qvo722a5d05-e4 >> system@br-tun: >> lookups: hit:381 missed:7589 lost:0 >> flows: 0 >> port 0: br-tun (internal) >> port 1: patch-int (patch: peer=patch-tun) >> port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1) >> >> >> On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi < >> luisguilherme...@gmail.com> wrote: >> >>> So guys, any idea about what am i missing? >>> >>> Thanks. >>> >>> >>> >>> >>> 2013/2/22 Guilherme Russi <luisguilherme...@gmail.com> >>> >>>> Hello Aaron, >>>> >>>> Here are the outputs. >>>> >>>> >>>> Thanks. >>>> >>>> Guilherme. >>>> >>>> >>>> 2013/2/21 Aaron Rosen <aro...@nicira.com> >>>> >>>>> The output to the following would be a good start: >>>>> >>>>> quantum net-list >>>>> quantum port-list >>>>> ovs-dpctl show (on all nodes) >>>>> >>>>> Also make sure the quantum-dhcp-agent is running on your network node. >>>>> >>>>> Aaron >>>>> >>>>> On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi < >>>>> luisguilherme...@gmail.com> wrote: >>>>> >>>>>> Sorry about that, I'm using Folsom release with quantum, I'm >>>>>> installing the controller node and the network node in the same physical >>>>>> machine, I'm following this tutorial: >>>>>> >>>>>> >>>>>> http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html >>>>>> >>>>>> Which config files do you need? >>>>>> >>>>>> Thanks. >>>>>> >>>>>> Guilherme. >>>>>> >>>>>> >>>>>> 2013/2/21 Aaron Rosen <aro...@nicira.com> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> You'll have to provide more information than this for anyone to help >>>>>>> you: i.e are you using quantum or nova-network, if your using quantum >>>>>>> which >>>>>>> plugin, config files etc. >>>>>>> >>>>>>> Aaron >>>>>>> >>>>>>> On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi < >>>>>>> luisguilherme...@gmail.com> wrote: >>>>>>> >>>>>>>> Hello guys, >>>>>>>> >>>>>>>> I'm getting problem in my VMs' creation, they don't get IP, the >>>>>>>> log piece shows: >>>>>>>> >>>>>>>> >>>>>>>> Starting network... >>>>>>>> udhcpc (v1.18.5) started >>>>>>>> Sending discover... >>>>>>>> Sending discover... >>>>>>>> Sending discover... >>>>>>>> No lease, failing >>>>>>>> WARN: /etc/rc3.d/S40-network failed >>>>>>>> >>>>>>>> >>>>>>>> Do you have any idea how I can solve it? >>>>>>>> >>>>>>>> Thank you so much. >>>>>>>> >>>>>>>> Guilherme. >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Mailing list: https://launchpad.net/~openstack >>>>>>>> Post to : openstack@lists.launchpad.net >>>>>>>> Unsubscribe : https://launchpad.net/~openstack >>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
