локальный контроллер Open Virtual Network (Open Virtual Network local controller)
Конфигурация (Configuration)
ovn-controller retrieves most of its configuration information
from the local Open vSwitch's ovsdb-server instance. The default
location is db.sock in the local Open vSwitch's "run" directory.
It may be overridden by specifying the ovs-database argument as
an OVSDB active or passive connection method, as described in
ovsdb(7).
ovn-controller assumes it gets configuration information from the
following keys in the Open_vSwitch table of the local OVS
instance:
external_ids:system-id
The chassis name to use in the Chassis table.
external_ids:hostname
The hostname to use in the Chassis table.
external_ids:ovn-bridge
The integration bridge to which logical ports are
attached. The default is br-int. If this bridge
does not exist when ovn-controller starts, it will
be created automatically with the default
configuration suggested in ovn-architecture(7).
external_ids:ovn-bridge-datapath-type
This configuration is optional. If set, then the
datapath type of the integration bridge will be set
to the configured value. If this option is not set,
then ovn-controller will not modify the existing
datapath-type of the integration bridge.
external_ids:ovn-remote
The OVN database that this system should connect to
for its configuration, in one of the same forms
documented above for the ovs-database.
external_ids:ovn-remote-probe-interval
The inactivity probe interval of the connection to
the OVN database, in milliseconds. If the value is
zero, it disables the connection keepalive feature.
If the value is nonzero, then it will be forced to
a value of at least 1000 ms.
external_ids:ovn-openflow-probe-interval
The inactivity probe interval of the OpenFlow
connection to the OpenvSwitch integration bridge,
in seconds. If the value is zero, it disables the
connection keepalive feature.
If the value is nonzero, then it will be forced to
a value of at least 5s.
external_ids:ovn-encap-type
The encapsulation type that a chassis should use to
connect to this node. Multiple encapsulation types
may be specified with a comma-separated list. Each
listed encapsulation type will be paired with
ovn-encap-ip.
Supported tunnel types for connecting hypervisors
are geneve and stt. Gateways may use geneve, vxlan,
or stt.
Due to the limited amount of metadata in vxlan, the
capabilities and performance of connected gateways
will be reduced versus other tunnel formats.
external_ids:ovn-encap-ip
The IP address that a chassis should use to connect
to this node using encapsulation types specified by
external_ids:ovn-encap-type.
external_ids:ovn-bridge-mappings
A list of key-value pairs that map a physical
network name to a local ovs bridge that provides
connectivity to that network. An example value
mapping two physical network names to two ovs
bridges would be:
physnet1:br-eth0,physnet2:br-eth1.
external_ids:ovn-encap-csum
ovn-encap-csum indicates that encapsulation
checksums can be transmitted and received with
reasonable performance. It is a hint to senders
transmitting data to this chassis that they should
use checksums to protect OVN metadata. Set to true
to enable or false to disable. Depending on the
capabilities of the network interface card,
enabling encapsulation checksum may incur
performance loss. In such cases, encapsulation
checksums can be disabled.
external_ids:ovn-cms-options
A list of options that will be consumed by the CMS
Plugin and which specific to this particular
chassis. An example would be:
cms_option1,cms_option2:foo.
external_ids:ovn-transport-zones
The transport zone(s) that this chassis belongs to.
Transport zones is a way to group different chassis
so that tunnels are only formed between members of
the same group(s). Multiple transport zones may be
specified with a comma-separated list. For example:
tz1,tz2,tz3.
If not set, the Chassis will be considered part of
a default transport zone.
external_ids:ovn-chassis-mac-mappings
A list of key-value pairs that map a chassis
specific mac to a physical network name. An example
value mapping two chassis macs to two physical
network names would be:
physnet1:aa:bb:cc:dd:ee:ff,physnet2:a1:b2:c3:d4:e5:f6.
These are the macs that ovn-controller will replace
a router port mac with, if packet is going from a
distributed router port on vlan type logical
switch.
ovn-controller reads the following values from the Open_vSwitch
database of the local OVS instance:
datapath-type from Bridge table
This value is read from local OVS integration
bridge row of Bridge table and populated in
external_ids:datapath-type of the Chassis table in
the OVN_Southbound database.
iface-types from Open_vSwitch table
This value is populated in external_ids:iface-types
of the Chassis table in the OVN_Southbound
database.
private_key, certificate, ca_cert, and bootstrap_ca_cert
from SSL table
These values provide the SSL configuration used for
connecting to the OVN southbound database server
when an SSL connection type is configured via
external_ids:ovn-remote. Note that this SSL
configuration can also be provided via command-line
options, the configuration in the database takes
precedence if both are present.
