Thanks for the reply. 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.
Any other guidance is greatly appreciated. Thanks again for the help, -A -----Original Message----- From: Justin Pettit [mailto:[email protected]] Sent: Tuesday, December 22, 2015 3:23 PM To: Toth, Andrew <[email protected]> Cc: [email protected] Subject: Re: [ovs-discuss] OVS with Distributed Data Plane > On Dec 22, 2015, at 12:49 PM, Toth, Andrew <[email protected]> wrote: > > Hey All, > > I am currently working on a project that requires an open source virtual > network function with distributed data planes associated with a single > control plane. Does OVS currently have this capability?. Have you looked at OVN? http://networkheresy.com/2015/01/13/ovn-bringing-native-virtual-networking-to-ovs/ There will be experimental support for it in OVS 2.5. There have been a few blog posts about using it, which you can find with a bit of searching. --Justin _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
