X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=566e6cf69ce0c7560f28cda337c7b5add2e0a429;hb=142e1f5c7e3b607ccf82d3989477e93adc59c8b6;hp=a02ea53435982dc9d48a014c10b9b4f4d822d3dd;hpb=0b3e7a8b717b8c50c24244f7054079ede61742f2;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index a02ea534..566e6cf6 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -1,15 +1,20 @@ -

A database with this schema holds the configuration for one Open - vSwitch daemon. The root of the configuration for the daemon is - the table, which must have exactly one +

+ A database with this schema holds the configuration for one Open + vSwitch daemon. The top-level configuration for the daemon is the + table, which must have exactly one record. Records in other tables are significant only when they - can be reached directly or indirectly from the - table.

+ can be reached directly or indirectly from the table. Records that are not reachable from + the table are automatically deleted + from the database, except for records in a few distinguished + ``root set'' tables noted below. +

- Configuration for an Open vSwitch daemon. There must be exactly one record - in the table. + Configuration for an Open vSwitch daemon. There must be exactly + one record in the table. @@ -205,9 +210,9 @@

- The Open vSwitch version number, e.g. 1.1.0pre2. + The Open vSwitch version number, e.g. 1.1.0. If Open vSwitch was configured with a build number, then it is - also included, e.g. 1.1.0pre2+build4948. + also included, e.g. 1.1.0+build6579. @@ -244,7 +249,7 @@

The version of the system identified by , - e.g. 5.5.0-24648p on XenServer 5.5.0 build 24648. + e.g. 5.6.100-39265p on XenServer 5.6.100 build 39265.

System integrators are responsible for choosing and setting an @@ -273,21 +278,6 @@ connection should be configured. See the table for more information. - - -

- Remote database clients to which the Open vSwitch's database server - should connect or to which it should listen. Adding an OVSDB target - to this set is equivalent to adding it to with all of the default options. -

- -

- Use of this column is deprecated and may be removed sometime in the - future. New applications should use and set instead. -

-
@@ -508,22 +498,60 @@

A port that has more than one interface is a ``bonded port.'' Bonding - allows for load balancing and fail-over. Open vSwitch supports - ``source load balancing'' (SLB) and "active backup" bonding. SLB - bonding assigns flows to slaves based on source MAC address and output - VLAN, with periodic rebalancing as traffic patterns change. Active - backup bonding assigns all flows to one slave, failing over to a backup - slave when the active slave is disabled. Neither form of bonding - require 802.3ad or other special support from the upstream switch to - which the slave devices are connected.

+ allows for load balancing and fail-over. Some kinds of bonding will + work with any kind of upstream switch:

+ +
+
balance-slb
+
+ Balances flows among slaves based on source MAC address and output + VLAN, with periodic rebalancing as traffic patterns change. +
+ +
active-backup
+
+ Assigns all flows to one slave, failing over to a backup slave when + the active slave is disabled. +
+
+ +

+ The following modes require the upstream switch to support 802.3ad with + successful LACP negotiation. If LACP negotiation fails then + balance-slb style flow hashing is used as a fallback: +

+ +
+
balance-tcp
+
+ Balances flows among slaves based on L2, L3, and L4 protocol + information such as destination MAC address, IP address, and TCP + port. +
+
+ +
+
stable
+
+

Attempts to always assign a given flow to the same slave + consistently. In an effort to maintain stability, no load + balancing is done. Uses a similar hashing strategy to + balance-tcp, falling back to balance-slb + style hashing when LACP negotiations are unsuccessful.

+

Slave selection decisions are made based on LACP port ID when LACP + negotiations are successful, falling back to openflow port number + when unsuccessful. Thus, decisions are consistent across all + ovs-vswitchd instances with equivalent port IDs.

+
+

These columns apply only to bonded ports. Their values are otherwise ignored.

-

The type of bonding used for a bonded port. Currently supported - values are balance-slb and active-backup. - Defaults to SLB if unset.

+

The type of bonding used for a bonded port. Defaults to + balance-slb if unset. +

@@ -546,6 +574,18 @@ name of the port. Use only for compatibility with legacy software that requires this. + + +

Configures LACP on this port. LACP allows directly connected + switches to negotiate which links may be bonded. LACP may be enabled + on non-bonded ports for the benefit of any switches they may be + connected to. active ports are allowed to initiate LACP + negotiations. passive ports are allowed to participate + in LACP negotiations initiated by a remote switch, but not allowed to + initiate such negotiations themselves. If unset Open vSwitch will + choose a reasonable default.

+ + @@ -607,6 +647,18 @@
The number of milliseconds between successive attempts to poll each interface's MII. Only relevant on ports which use miimon to detect failures.
+
lacp-system-priority
+
The LACP system priority of this . In + LACP negotiations, link status decisions are made by the system + with the numerically lower priority. Must be a number between 1 + and 65535.
+
lacp-time
+
The LACP timing which should be used on this + . Possible values are fast and + slow. By default slow is used. When + configured to be fast more frequent LACP heartbeats + will be requested causing connectivity problems to be detected more + quickly.
 @@ -897,7 +949,7 @@ where GRE is not available. Note that only the tunneling component of the protocol is implemented. Due to the non-standard use of CAPWAP, UDP ports 58881 and 58882 are used as the source and - destinations ports respectivedly. Each tunnel must be uniquely + destination ports respectively. Each tunnel must be uniquely identified by the combination of remote_ip and local_ip. If two ports are defined that are the same except one includes local_ip and the other does not, @@ -999,8 +1051,10 @@

- The observed state of the physical network link; - i.e. whether a carrier is detected by the interface. + The observed state of the physical network link. This is ordinarily + the link's carrier status. If the interface's is + a bond configured for miimon monitoring, it is instead the network + link's miimon status.

@@ -1025,6 +1079,10 @@ and many kinds of virtual interfaces can be configured with higher MTUs.

+

+ This column will be empty for an interface that does not + have an MTU as, for example, some kinds of tunnels do not. +

@@ -1153,6 +1211,13 @@ Connectivity monitor configuration for this interface. + + Boolean value indicating LACP status for this interface. If true, this + interface has current LACP information about its LACP partner. This + information may be used to monitor the health of interfaces in a LACP + enabled port. This column will be empty if LACP is not enabled. + + Key-value pairs for use by external frameworks that integrate with Open vSwitch, rather than by Open vSwitch itself. System @@ -1194,8 +1259,14 @@ - Key-value pairs for rarely used interface features. Currently, - there are none defined. + Key-value pairs for rarely used interface features. +
+
lacp-port-priority
+
The LACP port priority of this . In + LACP negotiations s with numerically lower + priorities are preferred for aggregation. Must be a number between + 1 and 65535.
+
@@ -1344,7 +1415,7 @@ column="type"/> of linux-htb are:

min-rate
-
Minimum guaranteed bandwidth, in bit/s. Required.
+
Minimum guaranteed bandwidth, in bit/s.
max-rate
Maximum allowed bandwidth, in bit/s. Optional. If specified, the queue's rate will not be allowed to exceed the specified value, even @@ -1367,7 +1438,7 @@ column="type"/> of linux-hfsc are:

min-rate
-
Minimum guaranteed bandwidth, in bit/s. Required.
+
Minimum guaranteed bandwidth, in bit/s.
max-rate
Maximum allowed bandwidth, in bit/s. Optional. If specified, the queue's rate will not be allowed to exceed the specified value, even @@ -1433,22 +1504,6 @@ - - A set of MPIDs representing MPs to which this - has detected connectivity that are not in the - set. This should not - have connectivity to any MPs not listed in . - Thus, if this set is non-empty a fault is indicated. - - - - A set of MAIDs representing foreign Maintenance Associations (MAs) - which this has detected connectivity to. A - should not have connectivity to a Maintenance - Association other than its own. Thus, if this set is non-empty a fault - is indicated. - - Indicates a Connectivity Fault caused by a configuration error, a down remote MP, or unexpected connectivity to a remote MAID or remote MP. @@ -1489,6 +1544,12 @@ +

+ To be selected for mirroring, a given packet must enter or leave the + bridge through a selected port and it must also be in one of the + selected VLANs. +

+ If true, every packet arriving or departing on any port is selected for mirroring. @@ -1509,9 +1570,13 @@ +

+ These columns are mutually exclusive. Exactly one of them must be + nonempty. +

+ -

Output port for selected packets, if nonempty. Mutually exclusive - with .

+

Output port for selected packets, if nonempty.

Specifying a port for mirror output reserves that port exclusively for mirroring. No frames other than those selected for mirroring will be forwarded to the port, and any frames received on the port @@ -1520,8 +1585,7 @@ -

Output VLAN for selected packets, if nonempty. Mutually exclusive - with .

+

Output VLAN for selected packets, if nonempty.

The frames will be sent out all ports that trunk , as well as any ports with implicit VLAN . When a mirrored frame is sent out a @@ -1652,23 +1716,6 @@

The specified TCP port (default: 6633) on the host at the given ip, which must be expressed as an IP address (not a DNS name).
-
discover
-
-

Enables controller discovery.

-

In controller discovery mode, Open vSwitch broadcasts a DHCP - request with vendor class identifier OpenFlow across - all of the bridge's network devices. It will accept any valid - DHCP reply that has the same vendor class identifier and includes - a vendor-specific option with code 1 whose contents are a string - specifying the location of the controller in the same format as - .

-

The DHCP reply may also, optionally, include a vendor-specific - option with code 2 whose contents are a string specifying the URI - to the base of the OpenFlow PKI - (e.g. http://192.168.0.1/openflow/pki). This URI is - used only for bootstrapping the OpenFlow PKI at initial switch - setup; ovs-vswitchd does not use it at all.

-

The following connection methods are currently supported for service @@ -1728,10 +1775,7 @@

-

If not specified, the default is implementation-specific. If - is discover, the connection mode - is always treated as in-band regardless of the actual - setting.

+

If not specified, the default is implementation-specific.

 @@ -1748,7 +1792,8 @@ number of seconds, it will send a probe. If a response is not received for the same additional amount of time, Open vSwitch assumes the connection has been broken and attempts to reconnect. - Default is implementation-specific. + Default is implementation-specific. A value of 0 disables + inactivity probes. @@ -1781,33 +1826,9 @@ - -

These values are considered only when - is discover.

- - - A POSIX - extended regular expression against which the discovered controller - location is validated. The regular expression is implicitly - anchored at the beginning of the controller location string, as - if it begins with ^. If not specified, the default - is implementation-specific. - - - - Whether to update /etc/resolv.conf when the - controller is discovered. If not specified, the default - is implementation-specific. Open vSwitch will only modify - /etc/resolv.conf if the DHCP response that it receives - specifies one or more DNS servers. - - -

These values are considered only in in-band control mode (see - ) and only when - is not discover. (For controller discovery, the network - configuration obtained via DHCP is used instead.)

+ ).

When multiple controllers are configured on a single bridge, there should be only one set of unique values in these columns. If different @@ -1857,15 +1878,11 @@

other
Allows the controller access to all OpenFlow features.
-
-
master
Equivalent to other, except that there may be at most one master controller at a time. When a controller configures itself as master, any existing master is demoted to the slaverole.
-
-
slave
Allows the controller read-only access to OpenFlow features. Attempts to modify the flow table will be rejected with an @@ -1882,19 +1899,23 @@
A human-readable description of the last error on the connection to the controller; i.e. strerror(errno). This key will exist only if an error has occurred.
-
-
state
The state of the connection to the controller. Possible values - are: VOID, BACKOFF, - CONNECTING, ACTIVE, and - IDLE.
-
-
-
time_in_state
-
Seconds since connecting to (if currently connected) or - disconnecting from (if currently disconnected) this - controller.
+ are: VOID (connection is disabled), + BACKOFF (attempting to reconnect at an increasing + period), CONNECTING (attempting to connect), + ACTIVE (connected, remote host responsive), and + IDLE (remote host idle, sending keep-alive). These + values may change in the future. They are provided only for human + consumption. +
sec_since_connect
+
The amount of time since this controller last successfully + connected to the switch (in seconds). Value is empty if controller + has never successfully connected.
+
sec_since_disconnect
+
The amount of time since this controller last disconnected from + the switch (in seconds). Value is empty if controller has never + disconnected.
 @@ -2025,6 +2046,7 @@ will send a probe. If a response is not received for the same additional amount of time, Open vSwitch assumes the connection has been broken and attempts to reconnect. Default is implementation-specific. + A value of 0 disables inactivity probes. @@ -2057,15 +2079,23 @@
The state of the connection to the manager. Possible values are: VOID (connection is disabled), BACKOFF (attempting to reconnect at an increasing - period), CONNECT_IN_PROGRESS (attempting to connect), + period), CONNECTING (attempting to connect), ACTIVE (connected, remote host responsive), and - IDLE (remote host unresponsive, disconnecting). These + IDLE (remote host idle, sending keep-alive). These values may change in the future. They are provided only for human consumption.
-
time_in_state
-
Milliseconds since the state key changed.
+
sec_since_connect
+
The amount of time since this manager last successfully connected + to the database (in seconds). Value is empty if manager has never + successfully connected.
+
+
+
sec_since_disconnect
+
The amount of time since this manager last disconnected from the + database (in seconds). Value is empty if manager has never + disconnected.