[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] openvswitch gre tunnel


  • To: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
  • From: C V <rayvittal-lists@xxxxxxxxx>
  • Date: Thu, 7 Oct 2010 09:51:05 -0700 (PDT)
  • Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 07 Oct 2010 09:52:39 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=tsFdJtXkIwziT2Q6sQdDXp1XlKpOZMUVM0AENxK0alqFQclxzQmCq97jmybVwlJkFGuvnpyWhI3Ld6ImBN8VsdvF0vLFN2NL0i/ERkpIVM1OXOzgB3KumZdnl//IX42TJDub41PdK+eNDOLlNGA1x2hRxaMgwSs8Cu3EbRVmstw=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

OK, something like this works (xapi1 is a host-only network created by xe 
network-create)
HOST1=192.168.152.22
HOST2=192.168.152.23
intf=$(ovs-vsctl create interface name=gre0 type=gre 
options:remote_ip=${HOST2}) 

port=$(ovs-vsctl create port name=gre0 interfaces=[${intf}] )
ovs-vsctl add bridge xapi1 ports ${port}
ifconfig xapi1 10.1.1.2/24
#repeat on HOST2
ifconfig xapi1 10.1.1.3/24
ping 10.1.1.2


----- Original Message ----
From: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
To: C V <rayvittal-lists@xxxxxxxxx>
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>; "xen-api@xxxxxxxxxxxxxxxxxxx" 
<xen-api@xxxxxxxxxxxxxxxxxxx>
Sent: Wed, October 6, 2010 2:02:20 AM
Subject: Re: [Xen-users] openvswitch gre tunnel

Hi CV,

The GRE tunnels require an openvswitch controller - do you have access to one? 
I 
believe the open-source 'nox' doesn't have the required functionality yet. 
Unfortunately in the current design, xapi doesn't have the abilities to 
configure the vswitches, and relies on the controller - so this particular 
feature is really only there to enable a controller to set up these tunnels, 
rather than a complete implementation.

If you just want to set up the tunnels manually, you can do so using the ovs 
commands on the hosts - the documentation is not great unfortunately, but as I 
understand, the ovs mailing list is a good source of info.

Sorry to not be of more help,

Jon

On 6 Oct 2010, at 02:34, C V wrote:

> I'm following the XCP proposal here: 
> http://wiki.xensource.com/xenwiki/Tunnelling
> I have two XCP hosts
> 
> So, I can create a tunnel on one host
> xe network-create  name-label='test crosshost private network'
> xe pif-list network-name-label=Pool-wide\ network\ associated\ with\ eth0
> xe tunnel-create pif-uuid=683232ad-d2ba-33bc-812f-3bf0e1bd8721 
> network-uuid=f3f59c0c-bbb7-d41b-bb9e-f9140e2bae96 
> 
> 
> 
> I can do the same on the other host. How do I now hook up the two tunnels?
> xe tunnel-param-add uuid= ?????
> 
> Thanks!
> --
> CV
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.