diff options
| author | Ben Pfaff <blp@nicira.com> | 2010-04-20 10:43:42 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@nicira.com> | 2010-04-20 11:01:44 -0700 |
| commit | 76ce9432393df462e2030036021ea60096a734d4 (patch) | |
| tree | fa834f2b60e668ae49044d453dac261e3011c803 /utilities/ovs-vsctl.8.in | |
| parent | 79c9f2ee7883b52860c76c3730725f5731402874 (diff) | |
| download | openvswitch-76ce9432393df462e2030036021ea60096a734d4.tar.gz | |
Add support for multiple OpenFlow controllers on a single bridge.
With this commit, Open vSwitch permits a bridge to have any number of
OpenFlow controllers. When multiple controllers are configured, Open
vSwitch connects to all of them simultaneously. Details of configuration
are in the vswitch schema documentation.
OpenFlow 1.0 does not specify how multiple controllers coordinate in
interacting with a single switch, so more than one controller should be
specified only if the controllers are themselves designed to coordinate
with each other.
An upcoming commit will provide a simple means for coordination between
multiple controllers.
Feature #2495.
Diffstat (limited to 'utilities/ovs-vsctl.8.in')
| -rw-r--r-- | utilities/ovs-vsctl.8.in | 20 |
1 files changed, 11 insertions, 9 deletions
diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in index 84193e875..cd83d0a29 100644 --- a/utilities/ovs-vsctl.8.in +++ b/utilities/ovs-vsctl.8.in @@ -299,13 +299,14 @@ output. .SS "OpenFlow Controller Connectivity" . \fBovs\-vswitchd\fR can perform all configured bridging and switching -locally, or it can be configured to connect a given bridge to an -external OpenFlow controller, such as NOX. +locally, or it can be configured to connect a given bridge to one or +more external OpenFlow controllers, such as NOX. . -If a \fIbridge\fR argument is given, the settings apply only to the -specified bridge. Otherwise, they apply to the Open vSwitch instance, -and its configuration applies to any bridge that has not been explicitly -configured through a \fIbridge\fR argument. +For each of these commands, a \fIbridge\fR of \fBdefault\fR applies +the configuration as the default for any bridge that has not been +explicitly configured. Otherwise, \fIbridge\fR must name a bridge, +and the settings apply only to that bridge. (Omitting \fIbridge\fR +entirely usually has the same effect as specifying \fBdefault\fR.) . .IP "\fBget\-controller\fR [\fIbridge\fR]" Prints the configured controller target. @@ -313,9 +314,10 @@ Prints the configured controller target. .IP "\fBdel\-controller\fR [\fIbridge\fR]" Deletes the configured controller target. . -.IP "\fBset\-controller\fR [\fIbridge\fR] \fItarget\fR" -Sets the configured controller target. The \fItarget\fR may use any of -the following forms: +.IP "\fBset\-controller\fR [\fIbridge\fR] \fItarget\fR\&..." +Sets the configured controller target or targets. If more than one +\fItarget\fR is specified, then \fIbridge\fR may not be omitted. Each +\fItarget\fR may use any of the following forms: . .RS .so lib/vconn-active.man |