[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] OVS with Distributed Data Plane
From:       Andrew.Toth () stratus ! com (Toth, Andrew)
Date:       2015-12-28 12:37:40
Message-ID: BLUPR08MB357E9BFCBC111B060999F87F1FB0 () BLUPR08MB357 ! namprd08 ! prod ! outlook ! com
[Download RAW message or body]

Not as far as I can tell. My understanding is that OVS is built to support multiple data path types but not have the CE on one system and the FE on another. 

-----Original Message-----
From: Ben Pfaff [mailto:blp at ovn.org] 
Sent: Wednesday, December 23, 2015 4:27 PM
To: Toth, Andrew <Andrew.Toth at stratus.com>
Cc: 'Justin Pettit' <jpettit at ovn.org>; discuss at openvswitch.org
Subject: Re: [ovs-discuss] OVS with Distributed Data Plane

On Tue, Dec 22, 2015 at 09:01:10PM +0000, Toth, Andrew wrote:
> Regrettably OVN will not fit our situation. In the NFV world today, 
> there is a push to separate the fast path data plane processing from 
> the slower path configuration control processing. The common 
> understanding is to put the data path processing on its own processor 
> as a separate process (possibly multiple data plane processes on 
> multiple processors) with cached data (flows in the emc in the case of
> OVS) and communicate back to the control plane data store when the 
> required information is not in the cache. For our current project we 
> need an open source VNF that is decomposed in this way. I just want to 
> ensure that this separation is not already being done by the OVS 
> community before we go through the task of separating OVS into these 
> two components for our scenario.

Isn't OVS already built this way?

[prev in list] [next in list] [prev in thread] [next in thread]