[dropping CC to Mike, who probably lost interest a while ago] On Wed, Oct 12, 2011 at 02:42:48PM -0700, Justin Pettit wrote: > On Oct 12, 2011, at 11:36 AM, Ben Pfaff wrote: > > > Could you at the same time add text about primary and service > > controllers and their different purposes? You can crib it (probably > > abbreviated) from vswitch.xml. > > > How about the following? > > ovs-vswitchd can perform all configured bridging and switching locally, > or it can be configured to communicate with one or more external > Open??? > Flow controllers. The switch is typically configured to connect to a > primary controller that takes charge of the bridge's flow table to > implement a network policy. Alternatively, the switch can be > config??? > ured to listen to connections from service controllers. Service > con??? > trollers are typically used for occasional support and maintenance, > e.g. with ovs-ofctl.
I like it except that service controllers and primary controllers aren't mutually exclusive. Maybe delete "Alternatively" and add "also" somewhere in that sentence? _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
