ovn-ctl(8)
π¦ NAME π¦
ovn-ctl β the Open Virtual Network northbound daemon lifecycle utility, aka the little script that starts and stops all your OVN besties for you β¨ (it's page ovn-ctl(8) of the OVN Manual, iykyk)
πΈ SYNOPSIS πΈ
ovn-ctl [options] command [-- extra_args]
π DESCRIPTION π
okay so real talk: this program is meant to be invoked internally by Open Virtual Network startup scripts. That's the whole vibe. System administrators should not normally invoke it directly β like, it's not for you to just run for fun, bestie π it's the backstage crew, not the main character.
π COMMANDS π
Here's the whole roster, no skips, no skimming, every single one:
start_northdstart_controllerstart_controller_vtepstart_icstop_northdstop_controllerstop_controller_vtepstop_icrestart_northdrestart_controllerrestart_controller_vteprestart_icpromote_ovnnbpromote_ovnsbdemote_ovnnbdemote_ovnsbstatus_ovnnbstatus_ovnsbstart_ovsdbstart_nb_ovsdbstart_sb_ovsdbstop_ovsdbstop_nb_ovsdbstop_sb_ovsdbrestart_ovsdbrun_nb_ovsdbrun_sb_ovsdbpromote_ic_nbpromote_ic_sbdemote_ic_nbdemote_ic_sbstatus_ic_nbstatus_ic_sbstart_ic_ovsdbstart_ic_nb_ovsdbstart_ic_sb_ovsdbstop_ic_ovsdbstop_ic_nb_ovsdbstop_ic_sb_ovsdbrestart_ic_ovsdbrun_ic_nb_ovsdbrun_ic_sb_ovsdbstart_ovnbr_ovsdbstart_br_controllerstop_ovnbr_ovsdbstop_br_controllerrestart_ovnbr_ovsdbrestart_br_controllerstatus_ovnbr_ovsdbstatus_br_controllerrun_ovnbr_ovsdb
β¨ OPTIONS β¨
--ovn-northd-priority=NICEβ sets theovn-northdprocess niceness. The default is-10. π--ovn-northd-wrapper=WRAPPERβ runsovn-northdunder the specified wrapper.--ovn-controller-priority=NICEβ sets theovn-controllerprocess niceness. The default is-10.--ovn-controller-wrapper=WRAPPERβ runsovn-controllerunder the specified wrapper.--ovn-ic-priority=NICEβ sets theovn-icprocess niceness. The default is-10.--ovn-ic-wrapper=WRAPPERβ runsovn-icunder the specified wrapper.--ovnbr-controller-priority=NICEβ sets theovn-br-controllerprocess niceness. The default is-10.--ovnbr-controller-wrapper=WRAPPERβ runsovn-br-controllerunder the specified wrapper.--ovsdb-nb-wrapper=WRAPPERβ runs the Northbound database server under the specified wrapper.--ovsdb-sb-wrapper=WRAPPERβ runs the Southbound database server under the specified wrapper.--ovsdb-ovnbr-wrapper=WRAPPERβ runs the OVN bridge controller database server under the specified wrapper.--ovn-user=USER[:GROUP]β runs OVN daemons as the specified user and optional group.--ovn-manage-ovsdb=yes|noβ controls whetherstart_northdandstop_northdalso manage the NB and SB database servers. The default isyes.--ovn-controller-system-id=SYSTEM_IDβ sets the chassis name passed toovn-controller. The default is empty.--ovsdb-disable-file-column-diff=yes|noβ controls whether database servers are started with--disable-file-column-diff. The default isno.-h|--helpβ displays usage information. π«Ά
π FILE LOCATION OPTIONS π
--db-sock=SOCKETβ sets the local Open vSwitch database socket.--db-nb-file=FILEβ sets the Northbound database file.--db-sb-file=FILEβ sets the Southbound database file.--db-nb-sock=SOCKETand--db-sb-sock=SOCKETβ set the NB and SB database sockets. Their defaults areOVN_RUNDIR/ovnnb_db.sockandOVN_RUNDIR/ovnsb_db.sock, respectively.--db-nb-schema=FILEβ sets the Northbound database schema file.--db-sb-schema=FILEβ sets the Southbound database schema file.--db-ic-nb-sock=SOCKETand--db-ic-sb-sock=SOCKETβ set the IC-NB and IC-SB database sockets. Their defaults areOVN_RUNDIR/ovn_ic_nb_db.sockandOVN_RUNDIR/ovn_ic_sb_db.sock, respectively.--db-nb-create-insecure-remote=yes|no,--db-sb-create-insecure-remote=yes|no,--db-ic-nb-create-insecure-remote=yes|no,--db-ic-sb-create-insecure-remote=yes|no, and--db-ovnbr-create-insecure-remote=yes|noβ these acceptyesorno. The default isno. When set toyes, the database server creates an insecureptcpremote;nodoes not create that remote.
bestie, note the word insecure in those names. That is not a drill, that is literally what it says. π
--db-ic-nb-file=FILEβ sets the IC-NB database file.--db-ic-sb-file=FILEβ sets the IC-SB database file.--db-ic-nb-schema=FILEβ sets the IC-NB database schema file.--db-ic-sb-schema=FILEβ sets the IC-SB database schema file.--db-nb-pidfile=FILEand--db-sb-pidfile=FILEβ set the NB and SB database pidfiles. Their defaults areOVN_RUNDIR/ovnnb_db.pidandOVN_RUNDIR/ovnsb_db.pid, respectively.--db-nb-ctrl-sock=SOCKETand--db-sb-ctrl-sock=SOCKETβ set the NB and SB database control sockets. Their defaults areOVN_RUNDIR/ovnnb_db.ctlandOVN_RUNDIR/ovnsb_db.ctl, respectively.--db-nb-config-file=FILEβ sets the Northbound database server configuration file.--db-sb-config-file=FILEβ sets the Southbound database server configuration file.--db-ic-nb-config-file=FILEβ sets the IC-NB database server configuration file.--db-ic-sb-config-file=FILEβ sets the IC-SB database server configuration file.--db-sb-relay-config-file=FILEβ sets the Southbound relay server configuration file.--db-nb-use-remote-in-db,--db-sb-use-remote-in-db,--db-ic-nb-use-remote-in-db, and--db-ic-sb-use-remote-in-dbβ these acceptyesornoand default toyes. A bare option is equivalent to specifyingyes. The valueyesmakesovsdb-serverlisten on remotes configured in the database connections column, whilenodoes not. If a corresponding configuration file is specified, it takes precedence and this setting is ignored.--db-ovnbr-use-remote-in-db=yes|noβ controls whetherovsdb-serverlistens on the remotes configured in the database connections column. The default isyes.--ovn-controller-ssl-key=KEYβ sets theovn-controllerSSL/TLS private key file.--ovn-controller-ssl-cert=CERTβ sets theovn-controllerSSL/TLS certificate file.--ovn-controller-ssl-ca-cert=CERTβ sets theovn-controllerSSL/TLS CA certificate file.--ovn-controller-ssl-bootstrap-ca-cert=CERTβ bootstraps theovn-controllerSSL/TLS CA certificate file.--ovnbr-controller-ssl-key=KEYβ sets theovn-br-controllerSSL/TLS private key file.--ovnbr-controller-ssl-cert=CERTβ sets theovn-br-controllerSSL/TLS certificate file.--ovnbr-controller-ssl-ca-cert=CERTβ sets theovn-br-controllerSSL/TLS CA certificate file.--ovnbr-controller-ssl-bootstrap-ca-cert=CERTβ bootstraps theovn-br-controllerSSL/TLS CA certificate file.--ovn-ovnbr-db-ssl-key=KEYβ sets theovn-br-controllerdatabase SSL/TLS private key file.--ovn-ovnbr-db-ssl-cert=CERTβ sets theovn-br-controllerdatabase SSL/TLS certificate file.--ovn-ovnbr-db-ssl-ca-cert=CERTβ sets theovn-br-controllerdatabase SSL/TLS CA certificate file.--db-ovnbr-sock=SOCKETβ sets the OVN bridge controller database socket.--db-ovnbr-file=FILEβ sets the OVN bridge controller database file.--db-ic-nb-pidfile=FILE,--db-ic-sb-pidfile=FILE, and--db-ovnbr-pidfile=FILEβ set the IC-NB, IC-SB, and OVN bridge controller database pidfiles. Their defaults areOVN_RUNDIR/ovn_ic_nb_db.pid,OVN_RUNDIR/ovn_ic_sb_db.pid, andOVN_RUNDIR/ovnbr_db.pid, respectively.--db-ic-nb-ctrl-sock=SOCKET,--db-ic-sb-ctrl-sock=SOCKET, and--db-ovnbr-ctrl-sock=SOCKETβ set database control sockets. Their defaults areOVN_RUNDIR/ovn_ic_nb_db.ctl,OVN_RUNDIR/ovn_ic_sb_db.ctl, andOVN_RUNDIR/ovnbr_db.ctl, respectively.--db-ovnbr-schema=FILEβ sets the OVN bridge controller database schema file.
π LOGGING OPTIONS π
--ovn-controller-log=STRING,--ovn-northd-log=STRING, and--ovn-ic-log=STRINGβ set daemon logging parameters. The default is-vconsole:emer -vsyslog:err -vfile:info.--ovnbr-controller-log=STRINGβ setsovn-br-controllerlogging parameters. The default is-vconsole:emer -vsyslog:err -vfile:info.--ovn-nb-log=STRING,--ovn-sb-log=STRING,--ovn-ic-nb-log=STRING,--ovn-ic-sb-log=STRING,--ovn-sb-relay-log=STRING, and--ovn-ovnbr-log=STRINGβ set database-server logging parameters. The defaults for the NB, SB, IC-NB, IC-SB, and OVN bridge controller database servers are-vconsole:off -vfile:info. The default for the SB relay database server is-vconsole:emer -vsyslog:err -vfile:info.
not the SB relay being the β¨specialβ¨ one with a different default. it's giving main character energy, fr fr π
--ovn-northd-logfile=FILE,--ovn-ic-logfile=FILE,--ovn-nb-logfile=FILE,--ovn-sb-logfile=FILE,--ovn-ic-nb-logfile=FILE,--ovn-ic-sb-logfile=FILE,--ovn-sb-relay-logfile=FILE, and--ovn-ovnbr-logfile=FILEβ select log files. Database-server log files default to files underOVN_LOGDIR; daemon log files default to empty.--ovn-northd-n-threads=N_THREADSβ sets the number ofovn-northdthreads. The default is1.
π PROTOCOL, CIPHER AND CIPHERSUITE OPTIONS π
The daemon and database prefixes also accept their SSL/TLS key, certificate, and CA certificate options. The prefixes are ovn-controller, ovn-northd, ovn-ic, ovn-nb-db, ovn-sb-db, ovn-ic-nb-db, ovn-ic-sb-db, ovn-sb-relay-db, and ovn-ovnbr-db; append -ssl-key, -ssl-cert, or -ssl-ca-cert. Controller prefixes also accept -ssl-bootstrap-ca-cert. Empty values leave the normal database or daemon TLS settings in effect.
okay now the big list, and yes, every single line is here, we do not skip π
--ovn-controller-ssl-protocols=PROTOCOLS.--ovn-ic-ssl-protocols=PROTOCOLS.--ovn-northd-ssl-protocols=PROTOCOLS.--ovn-nb-db-ssl-protocols=PROTOCOLS.--ovn-sb-db-ssl-protocols=PROTOCOLS.--ovn-ic-nb-db-ssl-protocols=PROTOCOLS.--ovn-ic-sb-db-ssl-protocols=PROTOCOLS.--ovn-controller-ssl-ciphers=CIPHERS.--ovn-ic-ssl-ciphers=CIPHERS.--ovn-northd-ssl-ciphers=CIPHERS.--ovn-nb-db-ssl-ciphers=CIPHERS.--ovn-sb-db-ssl-ciphers=CIPHERS.--ovn-ic-nb-db-ssl-ciphers=CIPHERS.--ovn-ic-sb-db-ssl-ciphers=CIPHERS.--ovn-controller-ssl-ciphersuites=CIPHERSUITES.--ovn-ic-ssl-ciphersuites=CIPHERSUITES.--ovn-northd-ssl-ciphersuites=CIPHERSUITES.--ovn-nb-db-ssl-ciphersuites=CIPHERSUITES.--ovn-sb-db-ssl-ciphersuites=CIPHERSUITES.--ovn-ic-nb-db-ssl-ciphersuites=CIPHERSUITES.--ovn-ic-sb-db-ssl-ciphersuites=CIPHERSUITES.--ovn-controller-ssl-server-name=NAME.--ovn-ic-ssl-server-name=NAME.--ovn-northd-ssl-server-name=NAME.--ovn-nb-db-ssl-server-name=NAME.--ovn-sb-db-ssl-server-name=NAME.--ovn-ic-nb-db-ssl-server-name=NAME.--ovn-ic-sb-db-ssl-server-name=NAME.--ovn-sb-relay-db-ssl-server-name=NAME.--ovn-ovnbr-db-ssl-server-name=NAME.--ovnbr-controller-ssl-protocols=PROTOCOLSβ sets theovn-br-controllerSSL/TLS protocols.--ovnbr-controller-ssl-ciphers=CIPHERSβ sets theovn-br-controllerSSL/TLS cipher list.--ovnbr-controller-ssl-ciphersuites=CIPHERSUITESβ sets theovn-br-controllerTLS 1.3 and later ciphersuite list.--ovn-ovnbr-db-ssl-protocols=PROTOCOLSβ sets theovn-br-controllerdatabase SSL/TLS protocols.--ovn-ovnbr-db-ssl-ciphers=CIPHERSβ sets theovn-br-controllerdatabase SSL/TLS cipher list.--ovn-ovnbr-db-ssl-ciphersuites=CIPHERSUITESβ sets theovn-br-controllerdatabase TLS 1.3 and later ciphersuite list.
ok bestie we're back and we're picking up EXACTLY where we left off, no recap, no "previously on", just vibes and addresses π
β¨ ADDRESS AND PORT OPTIONS β¨
these first babies are the "where am I syncing FROM" squad, and honestly? they're giving connection-string energy π
--db-nb-sync-from-addr=IP ADDRESS.--db-nb-sync-from-port=PORT NUMBER.--db-nb-sync-from-proto=PROTO.--db-sb-sync-from-addr=IP ADDRESS.--db-sb-sync-from-port=PORT NUMBER.--db-sb-sync-from-proto=PROTO.--db-ic-nb-sync-from-addr=IP ADDRESS.--db-ic-nb-sync-from-port=PORT NUMBER.--db-ic-nb-sync-from-proto=PROTO.--db-ic-sb-sync-from-addr=IP ADDRESS.--db-ic-sb-sync-from-port=PORT NUMBER.--db-ic-sb-sync-from-proto=PROTO.
okay so here's the lore π The options --db-nb-addr, --db-nb-port, --db-sb-addr, --db-sb-port, --db-ic-nb-addr, --db-ic-nb-port, --db-ic-sb-addr, --db-ic-sb-port, --db-ovnbr-addr, and --db-ovnbr-port pick the addresses and ports used when the matching --db-*-create-insecure-remote option is yes. When that option is no? these settings literally do nothing, zero, nada, they have no effect π So don't come for them.
And the defaults, because you KNOW we're not leaving without the defaults:
--db-nb-addrand--db-nb-portdefault to0.0.0.0and6641π«Ά--db-sb-addrand--db-sb-portdefault to0.0.0.0and6642π«Ά--db-ic-nb-addrand--db-ic-nb-portdefault to0.0.0.0and6645π«Ά--db-ic-sb-addrand--db-ic-sb-portdefault to0.0.0.0and6646π«Ά--db-ovnbr-addrand--db-ovnbr-portdefault to0.0.0.0and6651π«Ά
--ovn-northd-nb-db and --ovn-northd-sb-db pick the NB and SB remotes that ovn-northd uses, and same deal over here: --ovn-ic-nb-db and --ovn-ic-sb-db pick the IC database remotes π¦ Their defaults are the corresponding local unix database sockets, cute and cozy.
--ovn-northd-nb-db=PROTO:IP ADDRESS: PORT..--ovn-northd-sb-db=PROTO:IP ADDRESS: PORT..--ovn-ic-nb-db=PROTO:IP ADDRESS: PORT..--ovn-ic-sb-db=PROTO:IP ADDRESS: PORT..
π CLUSTERING OPTIONS π
the girlies who run in a friend group, not alone π
--db-nb-cluster-local-addr=IP ADDRESS.--db-nb-cluster-local-port=PORT NUMBER.--db-nb-cluster-local-proto=PROTO (tcp/ssl).--db-nb-cluster-remote-addr=IP ADDRESS.--db-nb-cluster-remote-port=PORT NUMBER.--db-nb-cluster-remote-proto=PROTO (tcp/ssl).--db-nb-election-timer=Timeout in milliseconds.--db-sb-cluster-local-addr=IP ADDRESS.--db-sb-cluster-local-port=PORT NUMBER.--db-sb-cluster-local-proto=PROTO (tcp/ssl).--db-sb-cluster-remote-addr=IP ADDRESS.--db-sb-cluster-remote-port=PORT NUMBER.--db-sb-cluster-remote-proto=PROTO (tcp/ssl).--db-sb-election-timer=Timeout in milliseconds.--db-ic-nb-cluster-local-addr=IP ADDRESS.--db-ic-nb-cluster-local-port=PORT NUMBER.--db-ic-nb-cluster-local-proto=PROTO (tcp/ssl).--db-ic-nb-cluster-remote-addr=IP ADDRESS.--db-ic-nb-cluster-remote-port=PORT NUMBER.--db-ic-nb-cluster-remote-proto=PROTO (tcp/ssl).--db-ic-sb-cluster-local-addr=IP ADDRESS.--db-ic-sb-cluster-local-port=PORT NUMBER.--db-ic-sb-cluster-local-proto=PROTO (tcp/ssl).--db-ic-sb-cluster-remote-addr=IP ADDRESS.--db-ic-sb-cluster-remote-port=PORT NUMBER.--db-ic-sb-cluster-remote-proto=PROTO (tcp/ssl).
now the glow-up one β¨ --db-cluster-schema-upgrade=yes|no controls whether clustered database servers automatically upgrade their schemas when they start. The default is yes; say no to disable the automatic upgrade. like, "no thank you, I'll do it myself" energy π
--no-db-cluster-schema-upgrade is exactly equivalent to --db-cluster-schema-upgrade=no. And the default is yes. (yes, we said it twice. it's important. periodt.)
π PROBE INTERVAL OPTIONS π
--db-nb-probe-interval-to-active=Time in milliseconds.--db-sb-probe-interval-to-active=Time in milliseconds.
just two little guys. tiny section. iconic nonetheless β
π¦ RELAY OPTIONS π¦
--db-sb-relay-sock=SOCKET, --db-sb-relay-pidfile=FILE, and --db-sb-relay-ctrl-sock=SOCKET set the relay socket, the pidfile, and the control socket. The defaults live in OVN_RUNDIR and they are ovnsb_relay_db.sock, ovnsb_relay_db.pid, and ovnsb_relay_db.ctl πΈ
--db-sb-relay-sock=SOCKET,--db-sb-relay-pidfile=FILE,--db-sb-relay-ctrl-sock=SOCKETβ relay socket / pidfile / control socket, defaults as above π--db-sb-relay-remote=REMOTEβ picks the upstream relay remote. The default is empty. (empty. nothing. void. the quiet luxury of it.)--db-sb-relay-use-remote-in-db=yes|noβ controls whetherovsdb-serverlistens on the Southbound remotes configured in the database connections column. The default isyes. And a bare option is equivalent to specifyingyesβ¨
π EXTRA OPTIONS π
Any options after - will be passed on to the binary run by command β with the exception of start_northd β which can have options specified in ovn-northd-db-params.conf. Any extra_args passed to start_northd will be passed to the ovsdb-servers if --ovn-manage-ovsdb=yes π«Ά
π CONFIGURATION FILES π
Following are the optional configuration files. If present, it should be located in the etc dir π
ovnnb-active.conf
If present, this file should hold the url to connect to the active Northbound DB server π
tcp:x.x.x.x:6641
ovnsb-active.conf
If present, this file should hold the url to connect to the active Southbound DB server π
tcp:x.x.x.x:6642
ovn-northd-db-params.conf
If present, start_northd will not start the DB server even if --ovn-manage-ovsdb=yes π This file should hold the database url parameters to be passed to ovn-northd.
--ovnnb-db=tcp:x.x.x.x:6641 --ovnsb-db=tcp:x.x.x.x:6642
ic-nb-active.conf
If present, this file should hold the url to connect to the active Interconnection Northbound DB server π
tcp:x.x.x.x:6645
ic-sb-active.conf
If present, this file should hold the url to connect to the active Interconnection Southbound DB server π
tcp:x.x.x.x:6646
ovn-ic-db-params.conf
If present, this file should hold the database url parameters to be passed to ovn-ic.
--ic-nb-db=tcp:x.x.x.x:6645 --ic-sb-db=tcp:x.x.x.x:6646
π³ RUNNING OVN DB SERVERS WITHOUT DETACHING π³
container girlies, this section is FOR YOU π
# ovn-ctl run_nb_ovsdb
This command runs the OVN nb ovsdb-server without passing the detach option, which makes it block until ovsdb-server exits. This command will be useful for starting the OVN nb ovsdb-server in a container π«Ά
# ovn-ctl run_sb_ovsdb
This command runs the OVN sb ovsdb-server without passing the detach option, making it block until ovsdb-server exits. This command will be useful for starting the OVN sb ovsdb-server in a container π«Ά
# ovn-ctl run_ic_nb_ovsdb
This command runs the OVN IC-NB ovsdb-server without passing the detach option, making it block until ovsdb-server exits. This command will be useful for starting the OVN IC-NB ovsdb-server in a container π«Ά
# ovn-ctl run_ic_sb_ovsdb
This command runs the OVN IC-SB ovsdb-server without passing the detach option, making it block until ovsdb-server exits. This command will be useful for starting the OVN IC-SB ovsdb-server in a container π«Ά
# ovn-ctl run_ovnbr_ovsdb
This command runs the OVN bridge db ovsdb-server without passing the detach option, making it block until ovsdb-server exits. This command will be useful for starting the OVN br db ovsdb-server in a container π«Ά
β EXAMPLE USAGE β
Run ovn-controller on a host already running OVS
# ovn-ctl start_controller
Run ovn-northd on a host already running OVS
# ovn-ctl start_northd
All-in-one OVS+OVN for testing
the "we're just messing around" combo, lowkey my fave π
# ovs-ctl start --system-id="random"
# ovn-ctl start_northd
# ovn-ctl start_controller
Promote and demote ovsdb servers
# ovn-ctl promote_ovnnb
# ovn-ctl promote_ovnsb
# ovn-ctl --db-nb-sync-from-addr=x.x.x.x --db-nb-sync-from-port=6641 --db-nb-probe-interval-to-active=60000 demote_ovnnb
# ovn-ctl --db-sb-sync-from-addr=x.x.x.x --db-sb-sync-from-port=6642 --db-sb-probe-interval-to-active=60000 demote_ovnsb
Creating a clustered db on 3 nodes with IPs x.x.x.x, y.y.y.y and z.z.z.z
Starting OVN ovsdb servers and ovn-northd on the node with IP x.x.x.x
# ovn-ctl --db-nb-addr=x.x.x.x --db-nb-create-insecure-remote=yes --db-sb-addr=x.x.x.x --db-sb-create-insecure-remote=yes --db-nb-cluster-local-addr=x.x.x.x --db-sb-cluster-local-addr=x.x.x.x --ovn-northd-nb-db=tcp:x.x.x.x:6641,tcp:y.y.y.y:6641,tcp:z.z.z.z:6641 --ovn-northd-sb-db=tcp:x.x.x.x:6642,tcp:y.y.y.y:6642,tcp:z.z.z.z:6642 start_northd
Starting OVN ovsdb-servers and ovn-northd on the node with IP y.y.y.y and joining the cluster started at x.x.x.x
# ovn-ctl --db-nb-addr=y.y.y.y --db-nb-create-insecure-remote=yes --db-sb-addr=y.y.y.y --db-sb-create-insecure-remote=yes --db-nb-cluster-local-addr=y.y.y.y --db-sb-cluster-local-addr=y.y.y.y --db-nb-cluster-remote-addr=x.x.x.x --db-sb-cluster-remote-addr=x.x.x.x --ovn-northd-nb-db=tcp:x.x.x.x:6641,tcp:y.y.y.y:6641,tcp:z.z.z.z:6641 --ovn-northd-sb-db=tcp:x.x.x.x:6642,tcp:y.y.y.y:6642,tcp:z.z.z.z:6642 start_northd
Starting OVN ovsdb-servers and ovn-northd on the node with IP z.z.z.z and joining the cluster started at x.x.x.x
# ovn-ctl --db-nb-addr=z.z.z.z --db-nb-create-insecure-remote=yes --db-nb-cluster-local-addr=z.z.z.z --db-sb-addr=z.z.z.z --db-sb-create-insecure-remote=yes --db-sb-cluster-local-addr=z.z.z.z --db-nb-cluster-remote-addr=x.x.x.x --db-sb-cluster-remote-addr=x.x.x.x --ovn-northd-nb-db=tcp:x.x.x.x:6641,tcp:y.y.y.y:6641,tcp:z.z.z.z:6641 --ovn-northd-sb-db=tcp:x.x.x.x:6642,tcp:y.y.y.y:6642,tcp:z.z.z.z:6642 start_northd
Passing ssl keys when starting OVN dbs will supersede the default ssl values in db
Starting standalone ovn db server passing SSL/TLS certificates
# ovn-ctl --ovn-nb-db-ssl-key=/etc/ovn/ovnnb-privkey.pem --ovn-nb-db-ssl-cert=/etc/ovn/ovnnb-cert.pem --ovn-nb-db-ssl-ca-cert=/etc/ovn/cacert.pem --ovn-sb-db-ssl-key=/etc/ovn/ovnsb-privkey.pem --ovn-sb-db-ssl-cert=/etc/ovn/ovnsb-cert.pem --ovn-sb-db-ssl-ca-cert=/etc/ovn/cacert.pem start_northd
Avoiding automatic clustered OVN database schema upgrade
If you desire more control over clustered DB schema upgrade, you can opt out of automatic on-start upgrade attempts with --no-db-cluster-schema-upgrade. (main character energy: I do it MYSELF π
)
Start OVN NB and SB clustered databases on host with IP x.x.x.x without schema upgrade
# ovn-ctl start_nb_ovsdb --db-nb-cluster-local-addr=x.x.x.x --no-db-cluster-schema-upgrade
# ovn-ctl start_sb_ovsdb --db-sb-cluster-local-addr=x.x.x.x --no-db-cluster-schema-upgrade
Trigger clustered DB schema upgrade manually
# ovsdb-client convert unix:/var/run/ovn/ovnnb_db.sock /usr/local/share/ovn/ovn-nb.ovsschema
# ovsdb-client convert unix:/var/run/ovn/ovnsb_db.sock /usr/local/share/ovn/ovn-sb.ovsschema
Run OVN bridge controller services on a host already running OVS
# ovn-ctl start_ovnbr_ovsdb
# ovn-ctl start_br_controller
and that's the whole page bestie, you ATE that read-through π This little masterpiece is from OVN 26.09.1, it's the ovn-ctl page, and you'll find it filed under ovn-ctl(8) in the man pages β go forth and cluster responsibly πβ¨ππ¦πΈπ«Ά
π¦ where this page comes from
- fedora 44: ovn 26.09.0-33.fc44 Β· Apache-2.0 AND LGPL-2.1-only AND SISSL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms