From patchwork Fri May 7 04:06:35 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ben Pfaff X-Patchwork-Id: 1475315 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=openvswitch.org (client-ip=2605:bc80:3010::133; helo=smtp2.osuosl.org; envelope-from=ovs-dev-bounces@openvswitch.org; receiver=) Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 4Fbxjk4pMXz9sXS for ; Fri, 7 May 2021 14:07:22 +1000 (AEST) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 54791402F3; Fri, 7 May 2021 04:07:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yomYoYJSCBzW; Fri, 7 May 2021 04:07:17 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [IPv6:2605:bc80:3010:104::8cd3:938]) by smtp2.osuosl.org (Postfix) with ESMTP id 7F692402F4; Fri, 7 May 2021 04:07:16 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 5D111C0022; Fri, 7 May 2021 04:07:16 +0000 (UTC) X-Original-To: dev@openvswitch.org Delivered-To: ovs-dev@lists.linuxfoundation.org Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id EF7D0C0001 for ; Fri, 7 May 2021 04:07:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id D9CE1402F2 for ; Fri, 7 May 2021 04:07:14 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qNZevz_IM7l for ; Fri, 7 May 2021 04:07:12 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by smtp2.osuosl.org (Postfix) with ESMTPS id 7C3E7402D3 for ; Fri, 7 May 2021 04:07:12 +0000 (UTC) X-Originating-IP: 75.54.222.30 Received: from sigfpe.attlocal.net (75-54-222-30.lightspeed.rdcyca.sbcglobal.net [75.54.222.30]) (Authenticated sender: blp@ovn.org) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id C2FD6C0004; Fri, 7 May 2021 04:07:09 +0000 (UTC) From: Ben Pfaff To: dev@openvswitch.org Date: Thu, 6 May 2021 21:06:35 -0700 Message-Id: <20210507040659.26830-4-blp@ovn.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210507040659.26830-1-blp@ovn.org> References: <20210507040659.26830-1-blp@ovn.org> MIME-Version: 1.0 Cc: Ben Pfaff Subject: [ovs-dev] [PATCH ovn v3 03/27] ovn-nbctl: Improve manpage. X-BeenThere: ovs-dev@openvswitch.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ovs-dev-bounces@openvswitch.org Sender: "dev" This rearranges the manpage into a more logical order, documents some options that weren't documented, adds some sections such as Environment and Exit Status that a manpage should have, puts the headings at reasonable levels instead of all at the top level, and adds a little more explanatory text in a few places. Signed-off-by: Ben Pfaff --- utilities/ovn-nbctl.8.xml | 670 ++++++++++++++++++++++---------------- 1 file changed, 392 insertions(+), 278 deletions(-) diff --git a/utilities/ovn-nbctl.8.xml b/utilities/ovn-nbctl.8.xml index 03d47dba5b72..39f9381fdaae 100644 --- a/utilities/ovn-nbctl.8.xml +++ b/utilities/ovn-nbctl.8.xml @@ -7,9 +7,327 @@

ovn-nbctl [options] command [arg...]

Description

-

This utility can be used to manage the OVN northbound database.

-

General Commands

+

+ The ovn-nbctl program configures the + OVN_Northbound database by providing a high-level interface + to its configuration database. See ovn-nb(5) for + comprehensive documentation of the database schema. +

+ +

+ ovn-nbctl connects to an ovsdb-server process + that maintains an OVN_Northbound configuration database. Using this + connection, it queries and possibly applies changes to the database, + depending on the supplied commands. +

+ +

+ ovn-nbctl can perform any number of commands in a single + run, implemented as a single atomic transaction against the database. +

+ +

+ The ovn-nbctl command line begins with global options (see + OPTIONS below for details). The global options are followed + by one or more commands. Each command should begin with -- + by itself as a command-line argument, to separate it from the following + commands. (The -- before the first command is optional.) + The command itself starts with command-specific options, if any, followed + by the command name and any arguments. +

+ +

Daemon Mode

+ +

+ When it is invoked in the most ordinary way, ovn-nbctl + connects to an OVSDB server that hosts the northbound database, retrieves + a partial copy of the database that is complete enough to do its work, + sends a transaction request to the server, and receives and processes the + server's reply. In common interactive use, this is fine, but if the + database is large, the step in which ovn-nbctl retrieves a + partial copy of the database can take a long time, which yields poor + performance overall. +

+ +

+ To improve performance in such a case, ovn-nbctl offers a + "daemon mode," in which the user first starts ovn-nbctl + running in the background and afterward uses the daemon to execute + operations. Over several ovn-nbctl command invocations, + this performs better overall because it retrieves a copy of the database + only once at the beginning, not once per program run. +

+ +

+ Use the --detach option to start an ovn-nbctl + daemon. With this option, ovn-nbctl prints the name of a + control socket to stdout. The client should save this name in + environment variable OVN_NB_DAEMON. Under the Bourne shell + this might be done like this: +

+ + 
+      export OVN_NB_DAEMON=$(ovn-nbctl --pidfile --detach)
+
+ +

+ When OVN_NB_DAEMON is set, ovn-nbctl + automatically and transparently uses the daemon to execute its commands. +

+ +

+ When the daemon is no longer needed, kill it and unset the environment + variable, e.g.: +

+ + 
+      kill $(cat $OVN_RUNDIR/ovn-nbctl.pid)
+      unset OVN_NB_DAEMON
+
+ +

+ When using daemon mode, an alternative to the OVN_NB_DAEMON + environment variable is to specify a path for the Unix socket. When + starting the ovn-nbctl daemon, specify the -u option with a + full path to the location of the socket file. Here is an exmple: +

+ + 
+      ovn-nbctl --detach -u /tmp/mysock.ctl
+
+ +

+ Then to connect to the running daemon, use the -u option + with the full path to the socket created when the daemon was started: +

+ + 
+      ovn-nbctl -u /tmp/mysock.ctl show
+
+ +

+ Daemon mode is experimental. +

+ +

Daemon Commands

+ +

+ Daemon mode is internally implemented using the same mechanism used by + ovs-appctl. One may also use ovs-appctl + directly with the following commands: +

+ +
+
+ run [options] command + [arg...] [-- [options] + command [arg...] ...] +
+
+ Instructs the daemon process to run one or more ovn-nbctl + commands described above and reply with the results of running these + commands. Accepts the --no-wait, --wait, + --timeout, --dry-run, --oneline, + and the options described under Table Formatting Options + in addition to the the command-specific options. +
+ +
exit
+
Causes ovn-nbctl to gracefully terminate.
+
+ +

Options

+ +

+ The options listed below affect the behavior of ovn-nbctl as + a whole. Some individual commands also accept their own options, which + are given just before the command name. If the first command on the + command line has options, then those options must be separated from the + global options by --. +

+ +

+ ovn-nbctl also accepts options from the + OVN_NBCTL_OPTIONS environment variable, in the same format as + on the command line. Options from the command line override those in the + environment. +

+ +
+
--no-wait | --wait=none
+
--wait=sb
+
--wait=hv
+ +
+

+ These options control whether and how ovn-nbctl waits + for the OVN system to become up-to-date with changes made in an + ovn-nbctl invocation. +

+ +

+ By default, or if --no-wait or --wait=none, + ovn-nbctl exits immediately after confirming that + changes have been committed to the northbound database, without + waiting. +

+ +

+ With --wait=sb, before ovn-nbctl exits, it + waits for ovn-northd to bring the southbound database + up-to-date with the northbound database updates. +

+ +

+ With --wait=hv, before ovn-nbctl exits, it + additionally waits for all OVN chassis (hypervisors and gateways) to + become up-to-date with the northbound database updates. (This can + become an indefinite wait if any chassis is malfunctioning.) +

+ +

+ Ordinarily, --wait=sb or --wait=hv only + waits for changes by the current ovn-nbctl invocation to + take effect. This means that, if none of the commands supplied to + ovn-nbctl change the database, then the command does not + wait at all. Use the sync command to override this + behavior. +

+
+ +
--db database
+
+ The OVSDB database remote to contact. If the OVN_NB_DB + environment variable is set, its value is used as the default. + Otherwise, the default is unix:@RUNDIR@/ovnnb_db.sock, but + this default is unlikely to be useful outside of single-machine OVN + test environments. +
+ +
--leader-only
+
--no-leader-only
+
+ By default, or with --leader-only, when the database + server is a clustered database, ovn-nbctl will avoid + servers other than the cluster leader. This ensures that any data that + ovn-nbctl reads and reports is up-to-date. With + --no-leader-only, ovn-nbctl will use any + server in the cluster, which means that for read-only transactions it + can report and act on stale data (transactions that modify the database + are always serialized even with --no-leader-only). Refer + to Understanding Cluster Consistency in + ovsdb(7) for more information. +
+ +
--shuffle-remotes
+
--no-shuffle-remotes
+
+ By default, or with --shuffle-remotes, when there are + multiple remotes specified in the OVSDB connection string specified by + --db or the OVN_NB_DB environment variable, the + order of the remotes will be shuffled before the client tries to + connect. The remotes will be shuffled only once to a new order before + the first connection attempt. The following retries, if any, will + follow the same new order. The default behavior is to make sure + clients of a clustered database can distribute evenly to all memembers + of the cluster. With --no-shuffle-remotes, + ovn-nbctl will use the original order specified in the + connection string to connect. This allows user to specify the + preferred order, which is particularly useful for testing. +
+ +
--no-syslog
+
+

+ By default, ovn-nbctl logs its arguments and the details + of any changes that it makes to the system log. This option disables + this logging. +

+ +

+ This option is equivalent to + --verbose=nbctl:syslog:warn. +

+
+ +
--oneline
+
+ Modifies the output format so that the output for each command is + printed on a single line. New-line characters that would otherwise + separate lines are printed as \fB\\n\fR, and any instances of \fB\\\fR + that would otherwise appear in the output are doubled. Prints a blank + line for each command that has no output. This option does not affect + the formatting of output from the list or + find commands; see Table Formatting Options + below. +
+ +
--dry-run
+
+ Prevents ovn-nbctl from actually modifying the database. +
+ +
-t secs
+
--timeout=secs
+
+ By default, or with a secs of 0, + ovn-nbctl waits forever for a response from the database. + This option limits runtime to approximately secs seconds. + If the timeout expires, ovn-nbctl will exit with a + SIGALRM signal. (A timeout would normally happen only if + the database cannot be contacted, or if the system is overloaded.) +
+ +
--print-wait-time
+
+ When --wait is specified, the option + --print-wait-time can be used to print the time spent on + waiting, depending on the value specified in --wait + option. If --wait=sb is specified, it prints "ovn-northd + delay before processing", which is the time between the Northbound DB + update by the command and the moment when ovn-northd + starts processing the update, and "ovn-northd completion", which is the + time between the Northbound DB update and the moment when + ovn-northd completes the Southbound DB updating + successfully. If --wait=hv is specified, in addition to + the above information, it also prints "ovn-controller(s) completion", + which is the time between the Northbound DB update and the moment when + the slowest hypervisor finishes processing the update. +
+
+ +

Daemon Options

+ + +

Logging options

+ + +

Table Formatting Options

+ These options control the format of output from the list and + find commands. + + +

PKI Options

+

+ PKI configuration is required to use SSL for the connection to the + database. +

+ + + +

Other Options

+ + + +

Commands

+ +

+ The following sections describe the commands that ovn-nbctl + supports. +

+ +

General Commands

init
@@ -28,7 +346,7 @@
-

Logical Switch Commands

+

Logical Switch Commands

ls-add
@@ -74,7 +392,7 @@
-

ACL Commands

+

ACL Commands

These commands operates on ACL objects for a given entity. The entity can be either a logical switch or a port group. @@ -127,7 +445,7 @@ -

Logical Switch QoS Rule Commands

+

Logical Switch QoS Rule Commands

[--may-exist] qos-add switch direction priority match [dscp=dscp] [rate=rate [burst=burst]]
@@ -181,7 +499,7 @@
-

Meter Commands

+

Meter Commands

meter-add name action rate unit [burst]
@@ -234,7 +552,7 @@
-

Logical Switch Port Commands

+

Logical Switch Port Commands

[--may-exist] lsp-add switch port
@@ -490,7 +808,7 @@
-

Forwarding Group Commands

+

Forwarding Group Commands

[--liveness]fwd-group-add group switch vip vmac ports
@@ -528,7 +846,7 @@ be listed.
-

Logical Router Commands

+

Logical Router Commands

lr-add
@@ -574,7 +892,7 @@
-

Logical Router Port Commands

+

Logical Router Port Commands

[--may-exist] lrp-add router port mac network... [peer=peer]
@@ -654,7 +972,7 @@
-

Logical Router Static Route Commands

+

Logical Router Static Route Commands

[--may-exist] [--policy=POLICY] @@ -745,7 +1063,7 @@
-

Logical Router Policy Commands

+

Logical Router Policy Commands

[--may-exist]lr-policy-add @@ -817,7 +1135,7 @@
-

NAT Commands

+

NAT Commands

[--may-exist] [--stateless]lr-nat-add router type external_ip logical_ip [logical_port external_mac]
@@ -914,7 +1232,7 @@
-

Load Balancer Commands

+

Load Balancer Commands

[--may-exist | --add-duplicate | --reject | --event] lb-add lb vip ips [protocol]
@@ -1038,7 +1356,7 @@
-

DHCP Options commands

+

DHCP Options commands

dhcp-options-create cidr [key=value]
@@ -1068,7 +1386,7 @@
-

Port Group commands

+

Port Group commands

pg-add group [port]...
@@ -1090,7 +1408,7 @@
-

HA Chassis Group commands

+

HA Chassis Group commands

ha-chassis-group-add group
@@ -1131,38 +1449,7 @@
-

Database Commands

-

These commands query and modify the contents of ovsdb tables. - They are a slight abstraction of the ovsdb interface and - as such they operate at a lower level than other ovn-nbctl commands.

-

Identifying Tables, Records, and Columns

-

Each of these commands has a table parameter to identify a table - within the database. Many of them also take a record parameter - that identifies a particular record within a table. The record - parameter may be the UUID for a record, which may be abbreviated to its - first 4 (or more) hex digits, as long as that is unique. Many tables offer - additional ways to identify records. Some commands also take - column parameters that identify a particular field within the - records in a table.

- -

- For a list of tables and their columns, see ovn-nb(5) or - see the table listing from the --help option. -

- -

- Record names must be specified in full and with correct capitalization, - except that UUIDs may be abbreviated to their first 4 (or more) hex - digits, as long as that is unique within the table. Names of tables and - columns are not case-sensitive, and - and _ are - treated interchangeably. Unique abbreviations of table and column names - are acceptable, e.g. d or dhcp is sufficient - to identify the DHCP_Options table. -

- - - -

Synchronization Commands

+

Synchronization Commands

sync
@@ -1178,7 +1465,15 @@
-

Remote Connectivity Commands

+

Remote Connectivity Commands

+

+ These commands manipulate the connections column in the + NB_Global table and rows in the Connection + table. When ovsdb-server is configured to use the + connections column for OVSDB connections, this allows the + administrator to use ovn-nbctl to configure database + connections. +

get-connection
@@ -1198,7 +1493,7 @@
-

SSL Configuration Commands

+

SSL Configuration Commands

get-ssl
@@ -1218,258 +1513,77 @@
-

Daemon Mode

- -

- When it is invoked in the most ordinary way, ovn-nbctl - connects to an OVSDB server that hosts the northbound database, retrieves - a partial copy of the database that is complete enough to do its work, - sends a transaction request to the server, and receives and processes the - server's reply. In common interactive use, this is fine, but if the - database is large, the step in which ovn-nbctl retrieves a - partial copy of the database can take a long time, which yields poor - performance overall. -

- -

- To improve performance in such a case, ovn-nbctl offers a - "daemon mode," in which the user first starts ovn-nbctl - running in the background and afterward uses the daemon to execute - operations. Over several ovn-nbctl command invocations, - this performs better overall because it retrieves a copy of the database - only once at the beginning, not once per program run. -

- +

Database Commands

- Use the --detach option to start an ovn-nbctl - daemon. With this option, ovn-nbctl prints the name of a - control socket to stdout. The client should save this name in - environment variable OVN_NB_DAEMON. Under the Bourne shell - this might be done like this: + These commands query and modify the contents of ovsdb + tables. They are a slight abstraction of the ovsdb + interface and as such they operate at a lower level than other + ovn-nbctl commands.

- 
-      export OVN_NB_DAEMON=$(ovn-nbctl --pidfile --detach)
-
- -

- When OVN_NB_DAEMON is set, ovn-nbctl - automatically and transparently uses the daemon to execute its commands. -

+

Identifying Tables, Records, and Columns

- When the daemon is no longer needed, kill it and unset the environment - variable, e.g.: + Each of these commands has a table parameter to identify a + table within the database. Many of them also take a record + parameter that identifies a particular record within a table. The + record parameter may be the UUID for a record, which may be + abbreviated to its first 4 (or more) hex digits, as long as that is + unique. Many tables offer additional ways to identify records. Some + commands also take column parameters that identify a + particular field within the records in a table.

- 
-      kill $(cat $OVN_RUNDIR/ovn-nbctl.pid)
-      unset OVN_NB_DAEMON
-
-

- When using daemon mode, an alternative to the OVN_NB_DAEMON environment - variable is to specify a path for the Unix socket. When starting the - ovn-nbctl daemon, specify the -u option with a full path to - the location of the socket file. Here is an exmple: + For a list of tables and their columns, see ovn-nb(5) or + see the table listing from the --help option.

- 
-      ovn-nbctl --detach -u /tmp/mysock.ctl
-
-

- Then to connect to the running daemon, use the -u option - with the full path to the socket created when the daemon was started: -

- - 
-      ovn-nbctl -u /tmp/mysock.ctl show
-
- -

- Daemon mode is experimental. + Record names must be specified in full and with correct capitalization, + except that UUIDs may be abbreviated to their first 4 (or more) hex + digits, as long as that is unique within the table. Names of tables and + columns are not case-sensitive, and - and _ are + treated interchangeably. Unique abbreviations of table and column names + are acceptable, e.g. d or dhcp is sufficient + to identify the DHCP_Options table.

-

Daemon Commands

+ -

- Daemon mode is internally implemented using the same mechanism used by - ovs-appctl. One may also use ovs-appctl - directly with the following commands: -

+

Environment

-
- run [options] command - [arg...] [-- [options] - command [arg...] ...] -
+
OVN_NB_DAEMON
- Instructs the daemon process to run one or more ovn-nbctl - commands described above and reply with the results of running these - commands. Accepts the --no-wait, --wait, - --timeout, --dry-run, --oneline, - and the options described under Table Formatting Options - in addition to the the command-specific options. + If set, this should name the Unix domain socket for an + ovn-nbctl server process. See Daemon Mode, + above, for more information.
-
exit
-
Causes ovn-nbctl to gracefully terminate.
-
- -

Options

- -
-
--no-wait | --wait=none
-
--wait=sb
-
--wait=hv
- +
OVN_NBCTL_OPTIONS
-

- These options control whether and how ovn-nbctl waits - for the OVN system to become up-to-date with changes made in an - ovn-nbctl invocation. -

- -

- By default, or if --no-wait or --wait=none, - ovn-nbctl exits immediately after confirming that - changes have been committed to the northbound database, without - waiting. -

- -

- With --wait=sb, before ovn-nbctl exits, it - waits for ovn-northd to bring the southbound database - up-to-date with the northbound database updates. -

- -

- With --wait=hv, before ovn-nbctl exits, it - additionally waits for all OVN chassis (hypervisors and gateways) to - become up-to-date with the northbound database updates. (This can - become an indefinite wait if any chassis is malfunctioning.) -

- -

- Ordinarily, --wait=sb or --wait=hv only - waits for changes by the current ovn-nbctl invocation to - take effect. This means that, if none of the commands supplied to - ovn-nbctl change the database, then the command does not - wait at all. Use the sync command to override this - behavior. -

+ If set, a set of options for ovn-nbctl to apply + automatically, in the same form as on the command line.
-
--print-wait-time
-
- When --wait is specified, the option - --print-wait-time can be used to print the time spent on - waiting, depending on the value specified in --wait option. - If --wait=sb is specified, it prints "ovn-northd delay - before processing", which is the time between the Northbound DB update by - the command and the moment when ovn-northd starts - processing the update, and "ovn-northd completion", which is the time - between the Northbound DB update and the moment when - ovn-northd completes the Southbound DB updating - successfully. If --wait=hv is specified, in addition to the - above information, it also prints "ovn-controller(s) completion", which - is the time between the Northbound DB update and the moment when the - slowest hypervisor finishes processing the update. -
- -
--db database
-
- The OVSDB database remote to contact. If the OVN_NB_DB - environment variable is set, its value is used as the default. - Otherwise, the default is unix:@RUNDIR@/ovnnb_db.sock, but this - default is unlikely to be useful outside of single-machine OVN test - environments. -
- -
--leader-only
-
--no-leader-only
-
- By default, or with --leader-only, when the database server - is a clustered database, ovn-nbctl will avoid servers other - than the cluster leader. This ensures that any data that - ovn-nbctl reads and reports is up-to-date. With - --no-leader-only, ovn-nbctl will use any server - in the cluster, which means that for read-only transactions it can report - and act on stale data (transactions that modify the database are always - serialized even with --no-leader-only). Refer to - Understanding Cluster Consistency in ovsdb(7) - for more information. -
- -
--shuffle-remotes
-
--no-shuffle-remotes
-
- By default, or with --shuffle-remotes, when there are - multiple remotes specified in the OVSDB connection string specified by - --db or the OVN_NB_DB environment variable, - the order of the remotes will be shuffled before the client tries to - connect. The remotes will be shuffled only once to a new order before - the first connection attempt. The following retries, if any, will - follow the same new order. The default behavior is to make sure - clients of a clustered database can distribute evenly to all memembers - of the cluster. With --no-shuffle-remotes, - ovn-nbctl will use the original order specified in the - connection string to connect. This allows user to specify the - preferred order, which is particularly useful for testing. -
- -
OVN_NBCTL_OPTIONS
-
-

- User can set one or more OVN_NBCTL_OPTIONS options in - environment variable. Under the Bourne shell this might be - done like this: -

- - 
-          OVN_NBCTL_OPTIONS="--db=unix:nb1.ovsdb --no-leader-only"
-
- -

- When OVN_NBCTL_OPTIONS is set, ovn-nbctl - automatically and transparently uses the environment variable to - execute its commands. However user can still over-ride environment - options by passing different in cli. -

- -

- When the environment variable is no longer needed, unset it, e.g.: -

- - 
-          unset OVN_NBCTL_OPTIONS
-
-
+
OVN_NB_DB
+
+ If set, the default database to contact when the --db + option is not used. +
-

Daemon Options

- - -

Logging options

- - -

Table Formatting Options

- These options control the format of output from the list and - find commands. - - -

PKI Options

-

- PKI configuration is required to use SSL for the connection to the - database. -

- - +

Exit Status

+
+
0
+
Successful program execution.
-

Other Options

+
1
+
Usage, syntax, or network error.
+
- +

See Also

+ ovn-nb(5).