Stephen Hemminger shemminger@vyatta.com
Takayuki HAMA t-hama@cb.jp.nec.com
Teemu Koponen koponen@nicira.com
+Vishal Swarankar vishal.swarnkar@gmail.com
kk yap yapkke@stanford.edu
Thanks to all Open vSwitch contributors. If you are not listed above
Open vSwitch also provides an OpenFlow implementation and tools for
those interested in OpenFlow but not additional Open vSwitch features:
- * ovs-openflowd, a program that implements a simple OpenFlow
- switch (without the special features provided by ovs-vswitchd)
- using the same kernel module as ovs-vswitchd.
+ * ovs-openflowd, an alternative to ovs-vswitchd that implements a
+ simple OpenFlow switch, without the special features provided by
+ ovs-vswitchd.
* ovs-controller, a simple OpenFlow controller.
flow-based datapath. \fBovs\-openflowd\fR connects to one or more
OpenFlow controllers over TCP or SSL.
.PP
+For a more powerful alternative to \fBovs\-openflowd\fR, see
+\fBovs\-vswitchd\fR(8). Do not run both daemons at the same time.
+.PP
The mandatory \fIdatapath\fR argument argument specifies the local datapath
to relay. It takes one of the following forms:
.
A single \fBovs\-vswitchd\fR can manage any number of switch instances, up
to the maximum number of supported Open vSwitch datapaths.
.PP
+\fBovs\-vswitchd\fR provides all the features of \fBovs-openflowd\fR,
+and more. Do not run both daemons at the same time.
+.PP
\fBovs\-vswitchd\fR does all the necessary management of Open vSwitch datapaths
itself. Thus, external tools, such \fBovs\-dpctl\fR(8), are not needed for
managing datapaths in conjunction with \fBovs\-vswitchd\fR, and their use