Config protocol is JSON rpc so that should work fine.
Was thinking about doing a python centralised server with the configuration 
stored in a sqlite database for exemple.


----- Message d'origine ----
De : Ben Pfaff <b...@nicira.com>
À : DarkBls <dark...@yahoo.com>
Cc : discuss@openvswitch.org
Envoyé le : Ven 22 Janvier 2010, 18 h 13 min 04 s
Objet : Re: [ovs-discuss] Re : Re :  GRE support

However, at least if you are writing your configuration server in C,
Open vSwitch has some fairly general-purpose libraries to speak the
configuration protocol (and I'm working on improving them further).

On Fri, Jan 22, 2010 at 09:10:16AM -0800, Martin Casado wrote:
The next branch supports the configuration protocol.  But yes, you
would have to write your own configuration server.


I see, so if I want to have a fully centralized datase configuration for all my 
OvS (hardware distributed) I must wait to have OpenFlow configuration protocol 
added, right ? (and code my own configuration server ?)




----- Message d'origine ----
De : Justin Pettit <jpet...@nicira.com>
? : DarkBls <dark...@yahoo.com>
Envoy? le : Ven 22 Janvier 2010, 10 h 20 min 51 s
Objet : Re: Re : [ovs-discuss] GRE support

The configuration database (ovsdb-server) runs locally on the
switch.  ovs-vswitchd connects to ovsdb-server over a JSON-RPC
unix domain socket.  Configuration changes made in the database
are immediately reflected in the switch.  In fact, programs such
as ovs-vsctl communicate over the same mechanism and won't return
until the changes have actually been implemented in ovs-vswitchd.

This JSON-RPC protocol will be the same one used by the OpenFlow configuration 
protocol.

--Justin


On Jan 22, 2010, at 12:49 AM, DarkBls wrote:

Thanks you for that.

For my own issue GRE tunnel would be very very interresting since 802.1ad is 
quite difficult to implement. Some switch doesn't support it in my 
infrastructure (BNT/Nortel) and I don't know what will be their behavior if 
they see double tagged frame. Further more, the linux drivers shoud support it 
too.

A centralized configuration database and GRE support would be quit a nice 
solution. Are the DB polled regulary to see if the configuration changed ? 
What's the trigger ?



----- Message d'origine ----
De : Justin Pettit <jpet...@nicira.com>
? : DarkBls <dark...@yahoo.com>
Cc : discuss@openvswitch.org
Envoy? le : Ven 22 Janvier 2010, 9 h 30 min 32 s
Objet : Re: [ovs-discuss] GRE support

Yes, if your kernel supports GRE tunnels and you create them externally with some program 
like "ip", you should be able to attach them as you would other system devices. 
 The support added to GRE does the following:

  - Ethernet over GRE was added to Linux 2.6.28, and it took a while before all 
the bugs were ironed out.  We've back-ported support and fixes all the way back 
to at least 2.6.18.

  - You can directly configure the GRE tunnels through OVS's configuration 
database.  This means that if you're using a remote configuration protocol like 
the one coming to OpenFlow (1.0.5?), you'll be able to remotely setup and 
configure your GRE tunnels.

We're also working on a few other improvements, such as support for PMTU.  The ones I 
listed above are what's immediately available in the "next" branch.

--Justin


On Jan 22, 2010, at 12:21 AM, DarkBls wrote:

Hi,

I know that GRE is already there in the unstable branch and will be "available" 
(documented) in the stable branch within a couple of month.

Can someone explain me what is the OvS support of GRE exactly ? Does'nt this 
already work ? :

Server A with OvS (#1)
   GRE tunnel to Server B displayed as gretapB
Server B with OvS (#2)
GRE tunnel to Server A displayed as gretapA

gretapA added ni OvS1 and gretapB added in OvS2

Thank you for your explaination




_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org



_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org


_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Reply via email to