hi, Ben thanks for your reply, and below is some feedback ________________________________________ From: Ben Pfaff [[email protected]] Sent: Monday, March 17, 2014 11:49 PM To: Wuhongning Cc: [email protected] Subject: Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider
On Mon, Mar 17, 2014 at 12:41:13PM +0000, Wuhongning wrote: >> if we have a hardware chip with rich networking feature, and want to >> expose as a enhanced flow switch. at the same time, we also want to >> keep the standard ovs, so what's the best practice to let them work >> together without bother each other? >Write a second ofproto provider, then configure ovs-vswitchd to use >both. how to "configure", can we do it on-the-fly? restart daemon process is acceptable, but any form of re-package(compile, link...) is difficulty. >> basically, we don't want to touch the original vswitchd daemon, so we > >will add another daemon, for example, eswd, and let eswd running with > >vswitchd separately. >Why do it that way? ovs-vswitchd is designed to handle multiple ofproto >providers at once. because we want to add the new ofproto "on-the-fly" in the production environment, that's to say, first we run native ovs, and after we have finished the new ofproto, just copy the ofproto software package to the directory, and change some .conf file, restart the vswitchd. if adding the new ofproto module needs the vswitchd to be re-packaged, we prefer to develop a separate vswd. also a separate process can prevent instability risk of our own ofproto, for some very critical traffic is on the native ovs dataplane. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
