[Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Haitao Jiang
I just set up a multi-node Grizzly release 2013.2 with 1 controller
node, 1 network node and 1 compute node. I use GRE tunneling.

I create one VM on the compute node and was not able to ssh to it using netns.

One thing I noticed is that on my compute node, I do not have br-int
and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
to create the GRE tunnels manually or they should be set up
automatically by Quantum? Any idea or suggestion to make it work?

Thanks in advance!

-- Compute node 
-- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
tunnel_id_ranges=1:1000
integration_bridge=br-int
tunneling_bridge=br-tun
tenant_network_type=gre
enable_tunneling=True
local_ip = 

# brctl show
bridge name bridge id   STP enabled interfaces
qbr5a9800b9-26  8000.5242b197c3d3   no  qvb5a9800b9-26
tap5a9800b9-26
virbr0  8000.525400198a10   yes virbr0-nic

# ovs-vsctl show
1d554b19-2a2b-493d-a123-0efb0aabc7d1
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
Bridge br-int
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "qvo5a9800b9-26"
tag: 1
Interface "qvo5a9800b9-26"
ovs_version: "1.10.0"

 network node ---
# brctl show
bridge name bridge id   STP enabled interfaces

# ovs-vsctl show
b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
Bridge br-int
Port br-int
Interface br-int
type: internal
Port "tap9536e146-c2"
Interface "tap9536e146-c2"
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "1.10.0"

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Chandler Li
Hi Haitao,

There should be GRE full mesh links being created in br-tun while you
created a VM successfully in Quantum ovs plugin GRE mode, just like:

Bridge br-tun
Port "gre-x"
Interface "gre-x"
type: gre
options: {in_key=flow, out_key=flow,
remote_ip="xx.xx.xx.xx"}

Maybe you can check if there any error in log file
(/var/log/quantum/openvswitch-agent.log in compute node and network node),
perhaps you have wrong setting in quantum.conf (rabbit_host or others)

Chandler


2013/7/10 Haitao Jiang 

> I just set up a multi-node Grizzly release 2013.2 with 1 controller
> node, 1 network node and 1 compute node. I use GRE tunneling.
>
> I create one VM on the compute node and was not able to ssh to it using
> netns.
>
> One thing I noticed is that on my compute node, I do not have br-int
> and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
> to create the GRE tunnels manually or they should be set up
> automatically by Quantum? Any idea or suggestion to make it work?
>
> Thanks in advance!
>
> -- Compute node 
> -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
> tunnel_id_ranges=1:1000
> integration_bridge=br-int
> tunneling_bridge=br-tun
> tenant_network_type=gre
> enable_tunneling=True
> local_ip = 
>
> # brctl show
> bridge name bridge id   STP enabled interfaces
> qbr5a9800b9-26  8000.5242b197c3d3   no
>  qvb5a9800b9-26
> tap5a9800b9-26
> virbr0  8000.525400198a10   yes virbr0-nic
>
> # ovs-vsctl show
> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
> Bridge br-tun
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port br-tun
> Interface br-tun
> type: internal
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port "qvo5a9800b9-26"
> tag: 1
> Interface "qvo5a9800b9-26"
> ovs_version: "1.10.0"
>
>  network node ---
> # brctl show
> bridge name bridge id   STP enabled interfaces
>
> # ovs-vsctl show
> b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port "tap9536e146-c2"
> Interface "tap9536e146-c2"
> Bridge br-ex
> Port br-ex
> Interface br-ex
> type: internal
> ovs_version: "1.10.0"
>
> ___
> 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


Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Aaron Rosen
I'd check the quantum openvswitch agent log files. I'd guess the reason
this isn't working is because your kernel isn't using the openvswitch
kernel module that has tunnel support.

Aaron


On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang  wrote:

> I just set up a multi-node Grizzly release 2013.2 with 1 controller
> node, 1 network node and 1 compute node. I use GRE tunneling.
>
> I create one VM on the compute node and was not able to ssh to it using
> netns.
>
> One thing I noticed is that on my compute node, I do not have br-int
> and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
> to create the GRE tunnels manually or they should be set up
> automatically by Quantum? Any idea or suggestion to make it work?
>
> Thanks in advance!
>
> -- Compute node 
> -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
> tunnel_id_ranges=1:1000
> integration_bridge=br-int
> tunneling_bridge=br-tun
> tenant_network_type=gre
> enable_tunneling=True
> local_ip = 
>
> # brctl show
> bridge name bridge id   STP enabled interfaces
> qbr5a9800b9-26  8000.5242b197c3d3   no
>  qvb5a9800b9-26
> tap5a9800b9-26
> virbr0  8000.525400198a10   yes virbr0-nic
>
> # ovs-vsctl show
> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
> Bridge br-tun
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port br-tun
> Interface br-tun
> type: internal
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port "qvo5a9800b9-26"
> tag: 1
> Interface "qvo5a9800b9-26"
> ovs_version: "1.10.0"
>
>  network node ---
> # brctl show
> bridge name bridge id   STP enabled interfaces
>
> # ovs-vsctl show
> b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port "tap9536e146-c2"
> Interface "tap9536e146-c2"
> Bridge br-ex
> Port br-ex
> Interface br-ex
> type: internal
> ovs_version: "1.10.0"
>
> ___
> 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


Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Haitao Jiang
Aaron & Chandler

Thanks a lot for the help. I should have mentioned that the host OS is
CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
found that it may not have gre tunneling support. Is there anyone who
has successfully set up gre with RDO's kernel or it is just can not be
done and I should use the VLAN.

As Aaron suspected, there are errprs in the OVS agent log:

system@ovs-system: failed to add gre-3 as port: Address family not
supported by protocol

More details below

Any pointer will be highly appreciated!

Haitao
==
Here are some outputs on my compute node (.46, .42 is the control node
and .44 is the network node):


# ovs-vsctl show
1d554b19-2a2b-493d-a123-0efb0aabc7d1
Bridge br-int
Port br-int
Interface br-int
type: internal
Port "qvo8108425f-ef"
tag: 1
Interface "qvo8108425f-ef"
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Port "gre-3"
Interface "gre-3"
type: gre
options: {in_key=flow, out_key=flow, remote_ip="10.18.250.44"}
Port "gre-4"
Interface "gre-4"
type: gre
options: {in_key=flow, out_key=flow, remote_ip="10.18.250.42"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
ovs_version: "1.10.0"

# ovs-ofctl dump-ports br-tun
OFPST_PORT reply (xid=0x2): 2 ports
  port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
   tx pkts=0, bytes=0, drop=0, errs=0, coll=0
  port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
   tx pkts=140, bytes=9800, drop=0, errs=0, coll=0

# uname -r
2.6.32-358.111.1.openstack.el6.x86_64

# modinfo openvswitch
filename:
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
version:1.10.0
license:GPL
description:Open vSwitch switching datapath
srcversion: 480D55A9BB0E8B000E32010
depends:
vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
modversions
parm:   vlan_tso:Enable TSO for VLAN packets (int)

# tail ovs-vswitchd.log
2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
patch-tun on port 1
2013-07-09T23:28:18Z|5|bridge|INFO|bridge br-tun: added interface
patch-int on port 1
2013-07-09T23:28:18Z|6|dpif|WARN|system@ovs-system: failed to add
gre-3 as port: Address family not supported by protocol
2013-07-09T23:28:18Z|7|dpif|WARN|system@ovs-system: failed to add
gre-4 as port: Address family not supported by protocol
2013-07-09T23:28:18Z|8|bridge|INFO|bridge br-int: using datapath
ID dacb49a63448
2013-07-09T23:28:18Z|9|connmgr|INFO|br-int: added service
controller "punix:/var/run/openvswitch/br-int.mgmt"
2013-07-09T23:28:18Z|00010|bridge|INFO|bridge br-tun: using datapath
ID 9a14eee01941
2013-07-09T23:28:18Z|00011|connmgr|INFO|br-tun: added service
controller "punix:/var/run/openvswitch/br-tun.mgmt"
2013-07-09T23:28:18Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
2013-07-09T23:28:28Z|00013|memory|INFO|7848 kB peak resident set size
after 10.0 seconds
2013-07-09T23:28:28Z|00014|memory|INFO|ports:5 rules:11
2013-07-09T23:28:28Z|00015|ofproto|INFO|br-int: 2 flow_mods in the 4 s
starting 10 s ago (1 adds, 1 deletes)
2013-07-09T23:28:28Z|00016|ofproto|INFO|br-tun: 5 flow_mods in the 3 s
starting 10 s ago (5 adds)
2013-07-09T23:53:25Z|00017|netdev|WARN|failed to set flags for network
device patch-int: Operation not supported

On Tue, Jul 9, 2013 at 8:59 PM, Aaron Rosen  wrote:
> I'd check the quantum openvswitch agent log files. I'd guess the reason this
> isn't working is because your kernel isn't using the openvswitch kernel
> module that has tunnel support.
>
> Aaron
>
>
> On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang  wrote:
>>
>> I just set up a multi-node Grizzly release 2013.2 with 1 controller
>> node, 1 network node and 1 compute node. I use GRE tunneling.
>>
>> I create one VM on the compute node and was not able to ssh to it using
>> netns.
>>
>> One thing I noticed is that on my compute node, I do not have br-int
>> and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
>> to create the GRE tunnels manually or they should be set up
>> automatically by Quantum? Any idea or suggestion to make it work?
>>
>> Thanks in advance!
>>
>> -- Compute node 
>> -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
>> tunnel_id_ranges=1:1000
>> integration_bridge=br-int
>> tunneling_bridge=br-tun
>> t

Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Aaron Rosen
You should be able to compile openvswitch from source here :
http://openvswitch.org/download/ and then you'll get tunnel support.

Aaron


On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang  wrote:

> Aaron & Chandler
>
> Thanks a lot for the help. I should have mentioned that the host OS is
> CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
> found that it may not have gre tunneling support. Is there anyone who
> has successfully set up gre with RDO's kernel or it is just can not be
> done and I should use the VLAN.
>
> As Aaron suspected, there are errprs in the OVS agent log:
>
> system@ovs-system: failed to add gre-3 as port: Address family not
> supported by protocol
>
> More details below
>
> Any pointer will be highly appreciated!
>
> Haitao
> ==
> Here are some outputs on my compute node (.46, .42 is the control node
> and .44 is the network node):
>
>
> # ovs-vsctl show
> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port "qvo8108425f-ef"
> tag: 1
> Interface "qvo8108425f-ef"
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Bridge br-tun
> Port br-tun
> Interface br-tun
> type: internal
> Port "gre-3"
> Interface "gre-3"
> type: gre
> options: {in_key=flow, out_key=flow,
> remote_ip="10.18.250.44"}
> Port "gre-4"
> Interface "gre-4"
> type: gre
> options: {in_key=flow, out_key=flow,
> remote_ip="10.18.250.42"}
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> ovs_version: "1.10.0"
>
> # ovs-ofctl dump-ports br-tun
> OFPST_PORT reply (xid=0x2): 2 ports
>   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
>tx pkts=0, bytes=0, drop=0, errs=0, coll=0
>   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
>tx pkts=140, bytes=9800, drop=0, errs=0, coll=0
>
> # uname -r
> 2.6.32-358.111.1.openstack.el6.x86_64
>
> # modinfo openvswitch
> filename:
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> version:1.10.0
> license:GPL
> description:Open vSwitch switching datapath
> srcversion: 480D55A9BB0E8B000E32010
> depends:
> vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
> modversions
> parm:   vlan_tso:Enable TSO for VLAN packets (int)
>
> # tail ovs-vswitchd.log
>
> 2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
> connecting...
>
> 2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
> connected
> 2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
> patch-tun on port 1
> 2013-07-09T23:28:18Z|5|bridge|INFO|bridge br-tun: added interface
> patch-int on port 1
> 2013-07-09T23:28:18Z|6|dpif|WARN|system@ovs-system: failed to add
> gre-3 as port: Address family not supported by protocol
> 2013-07-09T23:28:18Z|7|dpif|WARN|system@ovs-system: failed to add
> gre-4 as port: Address family not supported by protocol
> 2013-07-09T23:28:18Z|8|bridge|INFO|bridge br-int: using datapath
> ID dacb49a63448
> 2013-07-09T23:28:18Z|9|connmgr|INFO|br-int: added service
> controller "punix:/var/run/openvswitch/br-int.mgmt"
> 2013-07-09T23:28:18Z|00010|bridge|INFO|bridge br-tun: using datapath
> ID 9a14eee01941
> 2013-07-09T23:28:18Z|00011|connmgr|INFO|br-tun: added service
> controller "punix:/var/run/openvswitch/br-tun.mgmt"
> 2013-07-09T23:28:18Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
> 2013-07-09T23:28:28Z|00013|memory|INFO|7848 kB peak resident set size
> after 10.0 seconds
> 2013-07-09T23:28:28Z|00014|memory|INFO|ports:5 rules:11
> 2013-07-09T23:28:28Z|00015|ofproto|INFO|br-int: 2 flow_mods in the 4 s
> starting 10 s ago (1 adds, 1 deletes)
> 2013-07-09T23:28:28Z|00016|ofproto|INFO|br-tun: 5 flow_mods in the 3 s
> starting 10 s ago (5 adds)
> 2013-07-09T23:53:25Z|00017|netdev|WARN|failed to set flags for network
> device patch-int: Operation not supported
>
> On Tue, Jul 9, 2013 at 8:59 PM, Aaron Rosen  wrote:
> > I'd check the quantum openvswitch agent log files. I'd guess the reason
> this
> > isn't working is because your kernel isn't using the openvswitch kernel
> > module that has tunnel support.
> >
> > Aaron
> >
> >
> > On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang 
> wrote:
> >>
> >> I just set up a multi-node Grizzly release 2013.2 with 1 controller
> >> node, 1 network node and 1 compute node. I use GRE tunneling.
> >>
> >> I create one VM on the compute node and was not able to ssh to it using
> >> netns.
> >>
> >> One thing I noticed is that on my compute

Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-10 Thread Haitao Jiang
Aaron

I followed instructions in
http://n40lab.wordpress.com/2013/06/03/centos-6-4-openvswitch-installation/
on my compute node as a test. Restarted OVS, but still see the same
error in the ovs-vswitchd.log. This is what I have

kmod-openvswitch.x86_64  1.10.0-1.el6
 @/kmod-openvswitch-1.10.0-1.el6.x86_64
openstack-quantum-openvswitch.noarch2013.1.2-1.el6
@openstack-grizzly
openvswitch.x86_641.10.0-1.el6
  @openstack-grizzly

filename:
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
version:1.10.0
license:GPL
description:Open vSwitch switching datapath
srcversion: 480D55A9BB0E8B000E32010
depends:
vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
modversions
parm:   vlan_tso:Enable TSO for VLAN packets (int)

# find / -name openvswitch.ko | xargs ls -l
-rw-r--r-- 1 ovswitch ovswitch 4948350 Jul  9 21:41
/home/ovswitch/rpmbuild/BUILD/openvswitch-1.10.0/_default/datapath/linux/openvswitch.ko
-rw-r--r-- 1 root root 4948350 Jul  9 21:41
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
-rwxr--r-- 1 root root   77936 Jun 12 20:19
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
-rwxr--r-- 1 root root   72912 Jun 12 04:36
/lib/modules/2.6.32-358.11.1.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
lrwxrwxrwx 1 root root  83 Jul  9 21:42
/lib/modules/2.6.32-358.11.1.el6.x86_64/weak-updates/openvswitch/openvswitch.ko
-> 
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko

anything else I need to check? Does above looks right to you?

Thanks

Haitao

On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen  wrote:
> You should be able to compile openvswitch from source here :
> http://openvswitch.org/download/ and then you'll get tunnel support.
>
> Aaron
>
>
> On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang  wrote:
>>
>> Aaron & Chandler
>>
>> Thanks a lot for the help. I should have mentioned that the host OS is
>> CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
>> found that it may not have gre tunneling support. Is there anyone who
>> has successfully set up gre with RDO's kernel or it is just can not be
>> done and I should use the VLAN.
>>
>> As Aaron suspected, there are errprs in the OVS agent log:
>>
>> system@ovs-system: failed to add gre-3 as port: Address family not
>> supported by protocol
>>
>> More details below
>>
>> Any pointer will be highly appreciated!
>>
>> Haitao
>> ==
>> Here are some outputs on my compute node (.46, .42 is the control node
>> and .44 is the network node):
>>
>>
>> # ovs-vsctl show
>> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
>> Bridge br-int
>> Port br-int
>> Interface br-int
>> type: internal
>> Port "qvo8108425f-ef"
>> tag: 1
>> Interface "qvo8108425f-ef"
>> Port patch-tun
>> Interface patch-tun
>> type: patch
>> options: {peer=patch-int}
>> Bridge br-tun
>> Port br-tun
>> Interface br-tun
>> type: internal
>> Port "gre-3"
>> Interface "gre-3"
>> type: gre
>> options: {in_key=flow, out_key=flow,
>> remote_ip="10.18.250.44"}
>> Port "gre-4"
>> Interface "gre-4"
>> type: gre
>> options: {in_key=flow, out_key=flow,
>> remote_ip="10.18.250.42"}
>> Port patch-int
>> Interface patch-int
>> type: patch
>> options: {peer=patch-tun}
>> ovs_version: "1.10.0"
>>
>> # ovs-ofctl dump-ports br-tun
>> OFPST_PORT reply (xid=0x2): 2 ports
>>   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
>>tx pkts=0, bytes=0, drop=0, errs=0, coll=0
>>   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
>>tx pkts=140, bytes=9800, drop=0, errs=0, coll=0
>>
>> # uname -r
>> 2.6.32-358.111.1.openstack.el6.x86_64
>>
>> # modinfo openvswitch
>> filename:
>>
>> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
>> version:1.10.0
>> license:GPL
>> description:Open vSwitch switching datapath
>> srcversion: 480D55A9BB0E8B000E32010
>> depends:
>> vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
>> modversions
>> parm:   vlan_tso:Enable TSO for VLAN packets (int)
>>
>> # tail ovs-vswitchd.log
>>
>> 2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connecting...
>>
>> 2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connected
>> 2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
>> patch-tun on port 1
>> 2013-07-09T23:28:18

Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-10 Thread Aaron Rosen
You should follow the instructions here:
http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=INSTALL;h=5589fe7dd7203308bbec27a562cb9899d218577a;hb=a4fff9cc390b69bde1257b414212505a72c4b450


On Wed, Jul 10, 2013 at 10:27 AM, Haitao Jiang wrote:

> Aaron
>
> I followed instructions in
> http://n40lab.wordpress.com/2013/06/03/centos-6-4-openvswitch-installation/
> on my compute node as a test. Restarted OVS, but still see the same
> error in the ovs-vswitchd.log. This is what I have
>
> kmod-openvswitch.x86_64  1.10.0-1.el6
>  @/kmod-openvswitch-1.10.0-1.el6.x86_64
> openstack-quantum-openvswitch.noarch2013.1.2-1.el6
> @openstack-grizzly
> openvswitch.x86_641.10.0-1.el6
>   @openstack-grizzly
>
> filename:
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> version:1.10.0
> license:GPL
> description:Open vSwitch switching datapath
> srcversion: 480D55A9BB0E8B000E32010
> depends:
> vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
> modversions
> parm:   vlan_tso:Enable TSO for VLAN packets (int)
>
> # find / -name openvswitch.ko | xargs ls -l
> -rw-r--r-- 1 ovswitch ovswitch 4948350 Jul  9 21:41
>
> /home/ovswitch/rpmbuild/BUILD/openvswitch-1.10.0/_default/datapath/linux/openvswitch.ko
> -rw-r--r-- 1 root root 4948350 Jul  9 21:41
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> -rwxr--r-- 1 root root   77936 Jun 12 20:19
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> -rwxr--r-- 1 root root   72912 Jun 12 04:36
>
> /lib/modules/2.6.32-358.11.1.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> lrwxrwxrwx 1 root root  83 Jul  9 21:42
>
> /lib/modules/2.6.32-358.11.1.el6.x86_64/weak-updates/openvswitch/openvswitch.ko
> ->
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
>
> anything else I need to check? Does above looks right to you?
>
> Thanks
>
> Haitao
>
> On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen  wrote:
> > You should be able to compile openvswitch from source here :
> > http://openvswitch.org/download/ and then you'll get tunnel support.
> >
> > Aaron
> >
> >
> > On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang 
> wrote:
> >>
> >> Aaron & Chandler
> >>
> >> Thanks a lot for the help. I should have mentioned that the host OS is
> >> CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
> >> found that it may not have gre tunneling support. Is there anyone who
> >> has successfully set up gre with RDO's kernel or it is just can not be
> >> done and I should use the VLAN.
> >>
> >> As Aaron suspected, there are errprs in the OVS agent log:
> >>
> >> system@ovs-system: failed to add gre-3 as port: Address family not
> >> supported by protocol
> >>
> >> More details below
> >>
> >> Any pointer will be highly appreciated!
> >>
> >> Haitao
> >> ==
> >> Here are some outputs on my compute node (.46, .42 is the control node
> >> and .44 is the network node):
> >>
> >>
> >> # ovs-vsctl show
> >> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
> >> Bridge br-int
> >> Port br-int
> >> Interface br-int
> >> type: internal
> >> Port "qvo8108425f-ef"
> >> tag: 1
> >> Interface "qvo8108425f-ef"
> >> Port patch-tun
> >> Interface patch-tun
> >> type: patch
> >> options: {peer=patch-int}
> >> Bridge br-tun
> >> Port br-tun
> >> Interface br-tun
> >> type: internal
> >> Port "gre-3"
> >> Interface "gre-3"
> >> type: gre
> >> options: {in_key=flow, out_key=flow,
> >> remote_ip="10.18.250.44"}
> >> Port "gre-4"
> >> Interface "gre-4"
> >> type: gre
> >> options: {in_key=flow, out_key=flow,
> >> remote_ip="10.18.250.42"}
> >> Port patch-int
> >> Interface patch-int
> >> type: patch
> >> options: {peer=patch-tun}
> >> ovs_version: "1.10.0"
> >>
> >> # ovs-ofctl dump-ports br-tun
> >> OFPST_PORT reply (xid=0x2): 2 ports
> >>   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0,
> crc=0
> >>tx pkts=0, bytes=0, drop=0, errs=0, coll=0
> >>   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
> >>tx pkts=140, bytes=9800, drop=0, errs=0, coll=0
> >>
> >> # uname -r
> >> 2.6.32-358.111.1.openstack.el6.x86_64
> >>
> >> # modinfo openvswitch
> >> filename:
> >>
> >>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> >> version:1.10.0
> >> license:GPL
> >> description:Open vSwitch switching datapath
> >> srcversion: 48