X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=vswitchd%2Fvswitch.xml;h=b74c55c8c7bea197cca76b13d36d82980befb687;hb=72c3b44800c5b25d5399b05e1bc6aece44414f49;hp=328cf354c283c546f29c3943cdc806c6c5029a96;hpb=289df16d29e963aef8c9df590300add4ab722ac9;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 328cf354..b74c55c8 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.
@@ -632,6 +637,13 @@
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.
@@ -922,7 +934,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,
@@ -1024,8 +1036,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.
@@ -1379,7 +1393,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
@@ -1402,7 +1416,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
@@ -1468,22 +1482,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.
@@ -1687,23 +1685,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
@@ -1763,10 +1744,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.
@@ -1816,33 +1794,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
@@ -1892,15 +1846,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 slave
role.
-
-
slave
- Allows the controller read-only access to OpenFlow features.
Attempts to modify the flow table will be rejected with an
@@ -1917,19 +1867,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.
@@ -2092,15 +2046,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.