openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #18710
Re: Quantum + OpenVSwitch + GRE Tunneling with RHEL 6.3
Thanks for your response.
BTW, is it possible to make the quantum + OpenVSwitch + VLAN type workable
on my RHEL6.3? I am trying this in my environment, but my VM can not get IP
address without any error in the quantum or compute log files.
--------------------------------------------------
Best regard,
David Geng ( 耿建华 )
ITIL Certified
ITCAM/ITM Installer
One SAPM
IBM SmartCloud Provisioning / Common Cloud Stack
Openstack
e-mail: gengjh@xxxxxxxxxx
Notes ID: Jian Hua Geng/China/IBM@IBMCN
Tel: 8610-82453091
Fax: 8610-82453303
Addr: Ring Bldg, 28 Zhongguancun SW park, No.8, Dong Bei Wang West Road,
Haidian District, Beijing, PRC 100193
地址:北京市海淀区东北旺西路8号中关村软件园28号楼环宇大厦 邮编:100193
--------------------------------------------------
Shake Chen
<shake.chen@gmail
.com> To
Jian Hua Geng/China/IBM@IBMCN,
11/19/2012 03:04 cc
PM openstack@xxxxxxxxxxxxxxxxxxx
Subject
Re: [Openstack] Quantum +
OpenVSwitch + GRE Tunneling with
RHEL 6.3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068365
That's right, the Open vSwitch FAQ says:
Q: What features are not available in the Open vSwitch kernel datapath
that ships as part of the upstream Linux kernel?
A: The kernel module in upstream Linux 3.3 and later does not include
the following features:
- Bridge compatibility, that is, support for the ovs-brcompatd
daemon that (if you enable it) lets "brctl" and other Linux
bridge tools transparently work with Open vSwitch instead.
We do not expect bridge compatibility to ever be available in
upstream Linux. If you need bridge compatibility, use the
kernel module from the Open vSwitch distribution instead of the
upstream Linux kernel module.
- Tunnel virtual ports, that is, interfaces with type "gre",
"ipsec_gre", "capwap". It is possible to create tunnels in
Linux and attach them to Open vSwitch as system devices.
However, they cannot be dynamically created through the OVSDB
protocol or set the tunnel ids as a flow action.
Work is in progress in adding these features to the upstream
Linux version of the Open vSwitch kernel module. For now, if
you need these features, use the kernel module from the Open
vSwitch distribution instead of the upstream Linux kernel
module.
- Patch virtual ports, that is, interfaces with type "patch".
You can use Linux "veth" devices as a substitute.
We don't have any plans to add patch ports upstream.
On Mon, Nov 19, 2012 at 1:40 PM, Jian Hua Geng <gengjh@xxxxxxxxxx> wrote:
Hi ShaKe,
Do you mean the latest OpenVSwitch for RHEL 6.3 does not support GRE
module or something else?
--------------------------------------------------
Best regard,
David Geng
--------------------------------------------------
Inactive hide details for Shake Chen ---11/19/2012 01:33:30 PM---Shake
Chen <shake.chen@xxxxxxxxx>Shake Chen ---11/19/2012 01:33:30 PM---Shake
Chen <shake.chen@xxxxxxxxx>
Shake Chen <
shake.chen@xxxxxxxx
m>
To
11/19/2012 01:33 PM
Jian Hua
Geng/China/IBM@IBMCN,
cc
openstack@xxxxxxxxxxxxxxxxxx
t
Subject
Re: [Openstack] Quantum +
OpenVSwitch + GRE Tunneling
with RHEL 6.3
seem the newest kernel not support GRE module.
On Mon, Nov 19, 2012 at 12:59 PM, Jian Hua Geng <gengjh@xxxxxxxxxx>
wrote:
Can anyone help to confirm that the GRE Tunneling can be used with
Quantum on my RHEL6.3?
My Redhat kernel version is 2.6.32-279.el6.x86_64, and the
OpenVSwitch version is 1.4.2. From the wiki page(
http://wiki.openstack.org/ConfigureOpenvswitch) , I find some
modules are still not available in RHEL.
If I want to use the GRE Tunneling, need I upgrade my linux kernel
or OpenVSwitch?
Thanks!
--------------------------------------------------
Best regard,
David Geng
--------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Shake Chen
--
Shake Chen
[attachment "pic28024.gif" deleted by Jian Hua Geng/China/IBM]
References