- OpenVSwitch Installation Instructions
+ Open vSwitch Installation Instructions
This document describes how to build, install, and execute
-OpenVSwitch.
+Open vSwitch.
-OpenVSwitch implements an Ethernet switch with MAC learning that may
+Open vSwitch implements an Ethernet switch with MAC learning that may
be configured with any of the following features:
* NIC bonding with automatic fail-over and source MAC-based TX
Base Prerequisites
------------------
-Regardless of how it is built, OpenVSwitch has a common set of
+Regardless of how it is built, Open vSwitch has a common set of
prerequisites. To compile the userspace programs in the OpenFlow
reference distribution, you will need the following software:
with version 4.2 or 4.3.
- libssl, from OpenSSL (http://www.openssl.org/), is optional but
- recommended if you plan to connect the OpenVSwitch to an
+ recommended if you plan to connect the Open vSwitch to an
OpenFlow controller. libssl is required to establish
confidentiality and authenticity in the connections from an
- OpenVSwitch to an OpenFlow controller. To enable, configure
+ Open vSwitch to an OpenFlow controller. To enable, configure
with --enable-ssl=yes.
To compile the kernel module, you must also install the following:
infrastructure.
If you are working from a Git tree or snapshot (instead of from a
-distribution tarball), or if you modify the OpenVSwitch build system,
+distribution tarball), or if you modify the Open vSwitch build system,
you will also need the following software:
- Autoconf version 2.60 or later (http://www.gnu.org/software/autoconf).
Debian Prerequisites
--------------------
-To build Debian packages from the OpenVSwitch distribution, you will
+To build Debian packages from the Open vSwitch distribution, you will
need to install a number of Debian packages in addition to the base
prerequisites listed above. These additional prerequisites may be
found listed as "Build-Depends" in debian/control in the source tree.
Building Conventionally
=======================
-This section explains how to build and install the OpenVSwitch
+This section explains how to build and install the Open vSwitch
distribution in the ordinary way using "configure" and "make".
0. Check that you have installed all the prerequisites listed above in
Installation
============
-This section explains how to install OpenVSwitch in a network with one
+This section explains how to install Open vSwitch in a network with one
controller and one or more switches, each of which runs on a separate
machine. Before you begin, you must decide on one of two ways for
each switch to reach the controller over the network:
Testing the Virtual Switch
--------------------------
-The OpenVSwitch kernel module must be loaded, as described under
+The Open vSwitch kernel module must be loaded, as described under
"Building Conventionally", before it may be used.
0. The commands below must run as root, so log in as root, or use a
Secure operation over SSL
-------------------------
-The instructions above set up OpenVSwitch for operation over a
-plaintext TCP connection. Production use of OpenVSwitch should use
+The instructions above set up Open vSwitch for operation over a
+plaintext TCP connection. Production use of Open vSwitch should use
SSL[*] to ensure confidentiality and authenticity of traffic among
switches and controllers. The source must be configured with
--enable-ssl=yes to build with SSL support.
-To use SSL with OpenVSwitch, you must set up a public-key infrastructure
+To use SSL with Open vSwitch, you must set up a public-key infrastructure
(PKI) including a pair of certificate authorities (CAs), one for
controllers and one for switches. If you have an established PKI,
-OpenVSwitch can use it directly. Otherwise, refer to "Establishing a
+Open vSwitch can use it directly. Otherwise, refer to "Establishing a
Public Key Infrastructure" below.
To configure the controller to listen for SSL connections on port 6633
# secchan -v DATAPATH ssl:192.168.1.2 --private-key=sc-privkey.pem \
--certificate=sc-cert.pem --ca-cert=pki/controllerca/cacert.pem
-[*] To be specific, OpenVSwitch uses TLS version 1.0 or later (TLSv1), as
+[*] To be specific, Open vSwitch uses TLS version 1.0 or later (TLSv1), as
specified by RFC 2246, which is very similar to SSL version 3.0.
TLSv1 was released in January 1999, so all current software and
hardware should implement it.
Establishing a Public Key Infrastructure
----------------------------------------
-If you do not have a PKI, the ovs-pki script included with OpenVSwitch
+If you do not have a PKI, the ovs-pki script included with Open vSwitch
can help. To create an initial PKI structure, invoke it as:
% ovs-pki init
which will create and populate a new PKI directory. The default
-location for the PKI directory depends on how the OpenVSwitch tree was
+location for the PKI directory depends on how the Open vSwitch tree was
configured (to see the configured default, look for the --dir option
description in the output of "ovs-pki --help").
- OpenVSwitch <http://openvswitch.org>
+ Open vSwitch <http://openvswitch.org>
-What is OpenVSwitch?
---------------------
+What is Open vSwitch?
+---------------------
-OpenVSwitch is an Ethernet switch for virtual servers with the
+Open vSwitch is an Ethernet switch for virtual servers with the
following features:
* NIC bonding with automatic fail-over and source MAC-based TX
- ovs-ofctl, a utility for querying and controlling OpenFlow
switches and controllers.
- - vlog-appctl, a utility that can control OpenVSwitch daemons,
+ - vlog-appctl, a utility that can control Open vSwitch daemons,
adjusting their logging levels among other uses.
- ovs-pki, a utility for creating and managing the public-key
#include <linux/version.h>
/*
- * Sysfs attributes of bridge for OpenVSwitch
+ * Sysfs attributes of bridge for Open vSwitch
*
* This has been shamelessly copied from the kernel sources.
*/
/*
- * Sysfs attributes of bridge ports for OpenVSwitch
+ * Sysfs attributes of bridge ports for Open vSwitch
*
* This has been shamelessly copied from the kernel sources.
*/
int i;
int err;
- printk("OpenVSwitch Bridge Compatibility, built "__DATE__" "__TIME__"\n");
+ printk("Open vSwitch Bridge Compatibility, built "__DATE__" "__TIME__"\n");
rcu_read_lock();
for (i=0; i<ODP_MAX; i++) {
module_init(brc_init);
module_exit(brc_cleanup);
-MODULE_DESCRIPTION("OpenVSwitch bridge compatibility");
+MODULE_DESCRIPTION("Open vSwitch bridge compatibility");
MODULE_AUTHOR("Copyright (c) 2009 The Board of Trustees of The Leland Stanford Junior University");
MODULE_LICENSE("GPL");
{
int err;
- printk("OpenVSwitch %s, built "__DATE__" "__TIME__"\n", VERSION BUILDNR);
+ printk("Open vSwitch %s, built "__DATE__" "__TIME__"\n", VERSION BUILDNR);
err = flow_init();
if (err)
module_init(dp_init);
module_exit(dp_cleanup);
-MODULE_DESCRIPTION("OpenVSwitch switching datapath");
+MODULE_DESCRIPTION("Open vSwitch switching datapath");
MODULE_LICENSE("GPL");
* Development version.
- -- OpenVSwitch developers <ovs-dev@openvswitch.org> Mon, 19 Nov 2007 14:57:52 -0800
+ -- Open vSwitch developers <ovs-dev@openvswitch.org> Mon, 19 Nov 2007 14:57:52 -0800
Source: openvswitch
Section: net
Priority: extra
-Maintainer: OpenVSwitch developers <ovs-dev@openvswitch.org>
+Maintainer: Open vSwitch developers <ovs-dev@openvswitch.org>
Build-Depends: debhelper (>= 5), autoconf (>= 2.60), automake1.10, libssl-dev, pkg-config (>= 0.21), po-debconf, bzip2, openssl, libncurses5-dev, libpcre3-dev
Standards-Version: 3.7.3
Architecture: all
Depends: module-assistant, bzip2, debhelper (>= 5.0.37)
Suggests: openvswitch-switch
-Description: Source code for OpenVSwitch datapath Linux module
- This package provides the OpenVSwitch datapath module source code
+Description: Source code for Open vSwitch datapath Linux module
+ This package provides the Open vSwitch datapath module source code
that is needed by openvswitch-switch. The kernel module can be built
from it using module-assistant or make-kpkg. README.Debian in this
package provides further instructions.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-common
Architecture: any
Depends: ${shlibs:Depends}, openssl
-Description: OpenVSwitch common components
+Description: Open vSwitch common components
openvswitch-common provides components required by both openvswitch-switch
and openvswitch-controller.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-switch
Architecture: any
Suggests: openvswitch-datapath-module
Depends: ${shlibs:Depends}, ${misc:Depends}, openvswitch-common, dhcp3-client, module-init-tools, dmidecode, procps, debianutils
-Description: OpenVSwitch switch implementations
+Description: Open vSwitch switch implementations
openvswitch-switch provides the userspace components and utilities for
- the Openvswitch kernel-based switch.
+ the Open vSwitch kernel-based switch.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-switch-config
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, openvswitch-switch, libwww-perl, libdigest-sha1-perl
-Description: OpenVSwitch switch implementations
+Description: Open vSwitch switch implementations
openvswitch-switch-config provides a utility for interactively configuring
- the OpenVSwitch switch provided in the openvswitch-switch package.
+ the Open vSwitch switch provided in the openvswitch-switch package.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-switchui
Package: openvswitch-pki
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, openvswitch-common
-Description: OpenVSwitch public key infrastructure
+Description: Open vSwitch public key infrastructure
openvswitch-pki provides PKI (public key infrastructure) support for
- OpenVSwitch switches and controllers, reducing the risk of
- man-in-the-middle attacks on the Openvswitch network infrastructure.
+ Open vSwitch switches and controllers, reducing the risk of
+ man-in-the-middle attacks on the Open vSwitch network infrastructure.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-pki-server
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${perl:Depends}, openvswitch-pki, apache2
-Description: OpenVSwitch public key infrastructure (HTTP server support)
- openvswitch-pki-server provides HTTP access to the OpenVSwitch PKI (public
+Description: Open vSwitch public key infrastructure (HTTP server support)
+ openvswitch-pki-server provides HTTP access to the Open vSwitch PKI (public
key infrastructure) maintained on the local machine by the
openvswitch-pki package. This HTTP access is needed for secure and
convenient OpenFlow switch setup using the ovs-switch-setup program
in the openvswitch-switch package.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: openvswitch-controller
Architecture: any
Depends: ${shlibs:Depends}, openvswitch-common, openvswitch-pki
-Description: OpenVSwitch controller implementation
- The OpenVSwitch controller enables OpenFlow switches that connect to it
+Description: Open vSwitch controller implementation
+ The Open vSwitch controller enables OpenFlow switches that connect to it
to act as MAC-learning Ethernet switches.
.
- OpenVSwitch is a software-based Ethernet switch targeted at virtual
+ Open vSwitch is a software-based Ethernet switch targeted at virtual
servers.
Package: corekeeper
Package: openvswitch-dbg
Architecture: any
Depends: ${shlibs:Depends}
-Description: Debug symbols for OpenVSwitch packages
+Description: Debug symbols for Open vSwitch packages
This package contains the debug symbols for all the other openvswitch-*
packages. Install it to debug one of them or to examine a core dump
produced by one of them.
Architecture: any
Recommends: openvswitch-switch
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Monitor utility for OpenVSwitch switches
+Description: Monitor utility for Open vSwitch switches
The ovs-monitor utility included in this package monitors the secure
channel and datapath. If either become unresponsive, the switch is
rebooted.
Architecture: any
Recommends: openvswitch-switch
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Watchdog utility for OpenVSwitch switches
+Description: Watchdog utility for Open vSwitch switches
The ovs-wdt program included in this package manages the hardware
watchdog timer in switches based on the Portwell NAR-5520 hardware.
openvswitch-switchui (= ${source:Version}),
openvswitch-datapath-module (= ${source:Version}),
corekeeper, openvswitch-monitor, openvswitch-wdt
-Description: Metapackage for installing a Nicira OpenVSwitch switch
+Description: Metapackage for installing a Nicira Open vSwitch switch
Installing this package will install everything needed for a Nicira
- Portwell-based OpenVSwitch switch, including monitoring and the switch UI.
+ Portwell-based Open vSwitch switch, including monitoring and the switch UI.
Source: openvswitch
Section: net
Priority: extra
-Maintainer: OpenVSwitch developers <ovs-dev@openvswitch.org>
+Maintainer: Open vSwitch developers <ovs-dev@openvswitch.org>
Build-Depends: debhelper (>= 5.0.37)
Standards-Version: 3.7.3
Architecture: any
Recommends: kernel-image-_KVERS_, openvswitch-switch
Provides: openvswitch-datapath-module
-Description: OpenVSwitch Linux datapath kernel module
- This package contains the OpenVSwitch loadable datapath kernel modules for
+Description: Open vSwitch Linux datapath kernel module
+ This package contains the Open vSwitch loadable datapath kernel modules for
the kernel-image-_KVERS_ package.
.
If you compiled a custom kernel, you will most likely need to compile
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
-# Short-Description: OpenVSwitch controller
+# Short-Description: Open vSwitch controller
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
-OpenVSwitch for Debian
+Open vSwitch for Debian
----------------------
* How do I build this module the Debian way?
# This is a POSIX shell fragment -*- sh -*-
-# To configure the OpenVSwitch monitor package, modify the following.
+# To configure the Open vSwitch monitor package, modify the following.
# Afterward, the monitor will be configured automatically at boot time.
# It can be started immediately with
# /etc/init.d/openvswitch-monitor start
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
-# Short-Description: OpenVSwitch switch monitor
+# Short-Description: Open vSwitch switch monitor
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/ovs-monitor
NAME=openvswitch-monitor
-DESC="OpenVSwitch switch monitor"
+DESC="Open vSwitch switch monitor"
PIDFILE=/var/run/$NAME.pid
with "/etc/init.d/openvswitch-switch start".
* To use the Linux kernel-based switch implementation, you will need
- to build and install the OpenVSwitch kernel module. To do so, install
+ to build and install the Open vSwitch kernel module. To do so, install
the openvswitch-datapath-source package, then follow the instructions
given in /usr/share/doc/openvswitch-datapath-source/README.Debian
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
-# Short-Description: OpenVSwitch switch
+# Short-Description: Open vSwitch switch
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# The network devices that you select should not be configured with IP
# or IPv6 addresses, even if the switch contacts the controller over
# one of the selected network devices. This is because a running
-# OpenVSwitch switch takes over network devices at a low level: they
+# Open vSwitch switch takes over network devices at a low level: they
# become part of the switch and cannot be used for other purposes.
#NETDEVS=""
# * out-of-band: OpenFlow traffic uses a network separate from the
# data traffic that it controls. If this is the case, the control
# network must already be configured on a network device other than
-# one of those selected as an OpenVSwitch switch port in the previous
+# one of those selected as an Open vSwitch switch port in the previous
# question.
#
# Set MODE to 'discovery', 'in-band', or 'out-of-band' for these
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
-# Short-Description: OpenVSwitch switch monitor
+# Short-Description: Open vSwitch switch monitor
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/bin/ovs-switchui
NAME=openvswitch-switchui
-DESC="OpenVSwitch switch monitor"
+DESC="Open vSwitch switch monitor"
PIDFILE=/var/run/$NAME.pid
# This is a POSIX shell fragment -*- sh -*-
-# To configure the OpenVSwitch reliability packages, modify the following.
+# To configure the Open vSwitch reliability packages, modify the following.
# Afterward, the watchdog timer and oops handling will be configured
# automatically at boot time. It can be started immediately with
# /etc/init.d/openvswitch-wdt start
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
-# Short-Description: OpenVSwitch switch watchdog
+# Short-Description: Open vSwitch switch watchdog
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/ovs-wdt
NAME=openvswitch-wdt
-DESC="OpenVSwitch switch watchdog"
+DESC="Open vSwitch switch watchdog"
PIDFILE=/var/run/$NAME.pid
version('2.0');
capb('backup');
-title('OpenVSwitch Switch Setup');
+title('Open vSwitch Switch Setup');
my (%netdevs) = find_netdevs();
db_subst('netdevs', 'choices',
-.TH ovs-switch-setup 8 "June 2008" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs-switch-setup 8 "June 2008" "Open vSwitch" "Open vSwitch Manual"
.SH NAME
-ovs\-switch\-setup \- interactive setup for OpenVSwitch switch
+ovs\-switch\-setup \- interactive setup for Open vSwitch switch
.SH SYNOPSIS
.B ovs\-switch\-setup
.SH DESCRIPTION
The \fBovs\-switch\-setup\fR program is an interactive program that
-assists the system administrator in configuring an OpenVSwitch switch,
+assists the system administrator in configuring an Open vSwitch switch,
including the underlying public key infrastructure (PKI).
.SH OPTIONS
.SH FILES
.IP /etc/default/openvswitch-switch
-Main configuration file for OpenVSwitch switch.
+Main configuration file for Open vSwitch switch.
.IP /etc/openvswitch-switch/cacert.pem
Default location of CA certificate for OpenFlow controllers.
.IP /etc/openvswitch-switch/of0-cert.pem
-Default location of certificate for the OpenVSwitch switch's private key.
+Default location of certificate for the Open vSwitch switch's private key.
.IP /etc/openvswitch-switch/of0-privkey.pem
-Default location of the OpenVSwitch switch's private key. This file
+Default location of the Open vSwitch switch's private key. This file
should be readable only by \fBroot\fR.
.IP /etc/openvswitch-switch/of0-req.pem
-Default location of certificate request for the OpenVSwitch switch's
+Default location of certificate request for the Open vSwitch switch's
certificate. This file is not used after the signed certificate
(typically \fB/etc/openvswitch-switch/of0-cert.pem\fR, above) has been
obtained from the OpenFlow PKI server.
ovs_fatal(error, "Could not listen for unixctl connections");
}
- VLOG_INFO("OpenVSwitch version %s", VERSION BUILDNR);
+ VLOG_INFO("Open vSwitch version %s", VERSION BUILDNR);
VLOG_INFO("OpenFlow protocol version 0x%02x", OFP_VERSION);
/* Start OpenFlow processing. */
-.TH secchan 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH secchan 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN secchan
.SH NAME
static void
usage(void)
{
- printf("%s: standalone program for testing OpenVSwitch DHCP client.\n"
+ printf("%s: standalone program for testing Open vSwitch DHCP client.\n"
"usage: %s [OPTIONS] NETDEV\n"
"where NETDEV is a network device (e.g. eth0).\n"
"\nDHCP options:\n"
. ns
. IP "\\$1"
..
-.TH ovs\-appctl 8 "April 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-appctl 8 "April 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-appctl
.SH NAME
-ovs\-appctl \- utility for configuring running OpenVSwitch daemons
+ovs\-appctl \- utility for configuring running Open vSwitch daemons
.SH SYNOPSIS
\fBovs\-appctl\fR [\fB-h\fR | \fB--help\fR] [\fItarget\fR...] [\fIaction\fR...]
.SH DESCRIPTION
The \fBovs\-appctl\fR program connects to one or more running
-OpenVSwitch daemons (such as \fBvswitchd\fR(8)), as specified by the
+Open vSwitch daemons (such as \fBvswitchd\fR(8)), as specified by the
user, and sends them commands to query or modify their behavior.
Its primary purpose is currently to adjust daemons' logging levels.
for a \fBovs\-appctl\fR-controllable process. If \fIsocket\fR does not
begin with \fB/\fR, it is treated as relative to \fB@RUNDIR@\fR.
-Each OpenVSwitch daemon by default creates a socket named
+Each Open vSwitch daemon by default creates a socket named
\fB@RUNDIR@/\fIprogram\fB.\fIpid\fB.ctl\fR, where \fIprogram\fR is
the program's name (such as \fBvswitchd\fR) and \fIpid\fR is the
daemon's PID.
-.TH ovs-cfg-mod 8 "April 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs-cfg-mod 8 "April 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs-cfg-mod
.
.SH NAME
-.TH ovs\-controller 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-controller 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-controller
.SH NAME
-.TH ovs\-discover 8 "May 2008" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-discover 8 "May 2008" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-discover
.SH NAME
.SH BUGS
If the network devices specified on the command line have been added
-to an OpenVSwitch datapath with \fBovs\-dpctl add\-if\fR, then controller
+to an Open vSwitch datapath with \fBovs\-dpctl add\-if\fR, then controller
discovery will fail because \fBovs\-discover\fR will not be able to
see DHCP responses, even though tools such as \fBtcpdump\fR(8) and
\fBwireshark\fR(1) can see them on the wire. This is because of the
structure of the Linux kernel networking stack, which hands packets
first to programs that listen for all arriving packets, then to
-OpenVSwitch, then to programs that listen for a specific kind of packet.
-OpenVSwitch consumes all the packets handed to it, so tools like
+Open vSwitch, then to programs that listen for a specific kind of packet.
+Open vSwitch consumes all the packets handed to it, so tools like
\fBtcpdump\fR that look at all packets will see packets arriving on
-OpenVSwitch interfaces, but \fRovs\-discover\fR, which listens only for
+Open vSwitch interfaces, but \fRovs\-discover\fR, which listens only for
arriving IP packets, will not.
.SH "SEE ALSO"
-.TH ovs\-dpctl 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-dpctl 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-dpctl
.SH NAME
-ovs\-dpctl \- administer OpenVSwitch datapaths
+ovs\-dpctl \- administer Open vSwitch datapaths
.SH SYNOPSIS
.B ovs\-dpctl
.SH DESCRIPTION
-The \fBovs\-dpctl\fR program can create, modify, and delete OpenVSwitch
+The \fBovs\-dpctl\fR program can create, modify, and delete Open vSwitch
datapaths. A single machine may host up to 256 datapaths (numbered 0
to 255).
Prints to the console all flow entries in datapath \fIdp\fR's
flow table.
-This command is primarily useful for debugging OpenVSwitch. The flow
+This command is primarily useful for debugging Open vSwitch. The flow
table entries that it displays are not
OpenFlow flow entries. Instead, they are different and considerably
-simpler flows maintained by the OpenVSwitch kernel module.
+simpler flows maintained by the Open vSwitch kernel module.
.IP "\fBdel-flows \fIdp\fR"
Deletes all flow entries from datapath \fIdp\fR's flow table.
-This command is primarily useful for debugging OpenVSwitch. As
+This command is primarily useful for debugging Open vSwitch. As
discussed in \fBdump-flows\fR, these entries are
not OpenFlow flow entries. By deleting them, the process that set them
up may be confused about their disappearance.
all ports except those disabled by STP, and group 1 contains all
ports. Additional groups might be used in the future.
-This command is primarily useful for debugging OpenVSwitch. OpenFlow
+This command is primarily useful for debugging Open vSwitch. OpenFlow
does not have a concept of port groups.
.SH OPTIONS
.SH EXAMPLES
A typical \fBovs\-dpctl\fR command sequence for controlling an
-OpenVSwitch kernel module:
+Open vSwitch kernel module:
.TP
\fBovs\-dpctl add\-dp dp0\fR
static void
usage(void)
{
- printf("%s: OpenVSwitch datapath management utility\n"
+ printf("%s: Open vSwitch datapath management utility\n"
"usage: %s [OPTIONS] COMMAND [ARG...]\n"
" add-dp DP [IFACE...] add new datapath DP (with IFACEs)\n"
" del-dp DP delete local datapath DP\n"
-.TH ovs\-kill 8 "May 2008" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-kill 8 "May 2008" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-kill
.SH NAME
{
printf("%s: kills a program using a pidfile\n"
"usage: %s [OPTIONS] PIDFILE [PIDFILE...]\n"
- "where PIDFILE is a pidfile created by an OpenVSwitch daemon.\n"
+ "where PIDFILE is a pidfile created by an Open vSwitch daemon.\n"
"\nOptions:\n"
" -s, --signal=NUMBER|NAME signal to send (default: TERM)\n"
" -f, --force ignore errors\n"
-.TH ovs\-ofctl 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-ofctl 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN ovs\-ofctl
.SH NAME
print <<EOF;
$0, for parsing leak checker logs
usage: $0 [BINARY] < LOG
-where LOG is a file produced by an OpenVSwitch program's --check-leaks option
+where LOG is a file produced by an Open vSwitch program's --check-leaks option
and BINARY is the binary that wrote LOG.
EOF
exit 0;
-.TH ovs\-pki 8 "May 2008" "OpenVSwitch" "OpenVSwitch Manual"
+.TH ovs\-pki 8 "May 2008" "Open vSwitch" "Open vSwitch Manual"
.SH NAME
ovs\-pki \- OpenFlow public key infrastructure management utility
C = US
ST = CA
L = Palo Alto
-O = OpenVSwitch
+O = Open vSwitch
OU = @ca@
-CN = OpenVSwitch @ca@ CA Certificate
+CN = Open vSwitch @ca@ CA Certificate
[ ca ]
default_ca = the_ca
C = US
ST = CA
L = Palo Alto
-O = OpenVSwitch
-OU = OpenVSwitch certifier
-CN = OpenVSwitch certificate for $arg1
+O = Open vSwitch
+OU = Open vSwitch certifier
+CN = Open vSwitch certificate for $arg1
EOF
if test $keytype = rsa; then
newkey=rsa:$bits
-.TH brcompatd 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH brcompatd 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN brcompatd
.
.SH NAME
.BR ovs-appctl (8),
.BR vswitchd (8),
.BR vswitchd.conf (5),
-\fBINSTALL\fR in the OpenVSwitch distribution.
+\fBINSTALL\fR in the Open vSwitch distribution.
-.TH vswitchd 8 "March 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH vswitchd 8 "March 2009" "Open vSwitch" "Open vSwitch Manual"
.ds PN vswitchd
.
.SH NAME
\fBvswitchd.conf\fR(5).
.PP
At startup or upon receipt of a \fBSIGHUP\fR signal, \fBvswitchd\fR
-reads the configuration file. It sets up OpenVSwitch datapaths and then
+reads the configuration file. It sets up Open vSwitch datapaths and then
operates switching across each bridge described in its configuration
files. If a logfile was specified on the command line it will also
be opened or reopened.
.PP
Only a single instance of \fBvswitchd\fR is intended to run at a time.
A single \fBvswitchd\fR can manage any number of virtual switches, up
-to the maximum number of supported OpenVSwitch datapaths.
+to the maximum number of supported Open vSwitch datapaths.
.PP
-\fBvswitchd\fR does all the necessary management of OpenVSwitch datapaths
+\fBvswitchd\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 \fBvswitchd\fR, and their use
to modify datapaths when \fBvswitchd\fR is running can interfere with
its operation. (\fBovs\-dpctl\fR may still be useful for diagnostics.)
.PP
-An OpenVSwitch datapath kernel module must be loaded for \fBvswitchd\fR
+An Open vSwitch datapath kernel module must be loaded for \fBvswitchd\fR
to be useful. Please refer to the \fBINSTALL\fR file included in the
-OpenVSwitch distribution for instructions on how to build and load
-the OpenVSwitch kernel module.
+Open vSwitch distribution for instructions on how to build and load
+the Open vSwitch kernel module.
.PP
.SH OPTIONS
.IP "\fB--fake-proc-net\fR"
.
.SH "BUGS"
.
-Only OpenVSwitch kernel-based datapaths are currently supported. In the
+Only Open vSwitch kernel-based datapaths are currently supported. In the
future, this restriction may be lifted.
.PP
Only Linux 2.6.\fIx\fR is currently supported.
.BR ovs-appctl (8),
.BR vswitchd.conf (5),
.BR brcompatd (8),
-\fBINSTALL\fR in the OpenVSwitch distribution.
+\fBINSTALL\fR in the Open vSwitch distribution.
. RE
. PP
..
-.TH vswitchd.conf 5 "April 2009" "OpenVSwitch" "OpenVSwitch Manual"
+.TH vswitchd.conf 5 "April 2009" "Open vSwitch" "Open vSwitch Manual"
.
.SH NAME
vswitchd.conf \- configuration file for \fBvswitchd\fR
projects / openvswitch / commitdiff