NOVA-CONDUCTOR(1)

πŸ’– NOVA-CONDUCTOR πŸ’–

okay bestie, gather round, because this is the manual page for nova-conductor, part of the nova family β€” and it's literally the server for the OpenStack Compute conductor service. slay. let's get into it. πŸŽ€


✨ NAME ✨

nova-conductor β€” the server for the OpenStack Compute conductor service. she's the one keeping everybody coordinated. periodt. πŸ‘‘


🌸 SYNOPSIS 🌸

nova-conductor [<options>...]

πŸ¦‹ DESCRIPTION πŸ¦‹

so nova-conductor is a server daemon that serves the Nova Conductor service. and what does that service do, you ask? it provides coordination and database query support for nova. that's it, that's the job, and she does it beautifully. πŸ’…


πŸ”₯ OPTIONS πŸ”₯

General options

  • --config-dir DIR β€” path to a config directory to pull *.conf files from. this file set gets sorted, so you get a predictable parse order if individual options are over-ridden, iykyk. the set is parsed after the file(s) you specified via previous --config-file arguments, so over-ridden options in the directory take precedence. heads up: this option must be set from the command-line. no sneaking it in elsewhere. 😀
  • --config-file PATH β€” path to a config file to use. you can specify multiple config files, and values in later files take precedence (main character behaviour, honestly). defaults to None. and yeah β€” this one must also be set from the command-line. πŸ’–
  • --debug, -d β€” set the logging level to DEBUG instead of the default INFO level. when you need to see everything. 🌈
  • --log-config-append PATH, --log-config PATH, --log_config PATH β€” the name of a logging configuration file. this file gets appended to any existing logging configuration files. for the deets about logging configuration files, go look at the Python logging module documentation. ⚠️ important caveat bestie: when logging configuration files are used, then all logging configuration is set in the configuration file and the other logging configuration options are ignored (for example, log-date-format). so don't come crying to me when that one does nothing. πŸ’€
  • --log-date-format DATE_FORMAT β€” defines the format string for %(asctime)s in log records. default: None. this option is ignored if log_config_append is set. πŸ™ˆ
  • --log-dir LOG_DIR, --logdir LOG_DIR β€” (optional) the base directory used for relative log_file paths. this option is ignored if log_config_append is set. classic. ✨
  • --log-file PATH, --logfile PATH β€” (optional) name of the log file to send logging output to. if no default is set, logging will go to stderr as defined by use_stderr. this option is ignored if log_config_append is set. 🫢
  • --nodebug β€” the inverse of --debug. she's the anti-debug, the hater of verbosity, the calm one. 😌
  • --nouse-journal β€” the inverse of --use-journal. πŸ”„
  • --nouse-json β€” the inverse of --use-json. πŸ”„
  • --nouse-syslog β€” the inverse of --use-syslog. πŸ”„
  • --nowatch-log-file β€” the inverse of --watch-log-file. πŸ”„
  • --syslog-log-facility SYSLOG_LOG_FACILITY β€” syslog facility to receive log lines. this option is ignored if log_config_append is set. 😭
  • --use-journal β€” enable journald for logging. if you're running in a systemd environment you may wish to enable journal support. doing so will use the journal native protocol, which includes structured metadata in addition to log messages. this option is ignored if log_config_append is set. 🧚
  • --use-json β€” use JSON formatting for logging. this option is ignored if log_config_append is set. ✨
  • --use-syslog β€” use syslog for logging. ⚠️ the existing syslog format is DEPRECATED and will be changed later to honor RFC5424. this option is ignored if log_config_append is set. we love a heads-up, we do not love a deprecation. πŸ’€
  • --version β€” show the program's version number and exit. short, sweet, iconic. πŸ‘‘
  • --watch-log-file β€” uses a logging handler designed to watch the file system. when the log file is moved or removed, this handler will open a new log file with the specified path instantaneously. it makes sense only if the log_file option is specified and a Linux platform is used. this option is ignored if log_config_append is set. πŸ‘€

πŸŽ€ FILES πŸŽ€

  • /etc/nova/nova.conf

πŸ’œ SEE ALSO πŸ’œ


πŸ’€ BUGS πŸ’€


πŸ‘‘ Author πŸ‘‘

openstack@lists.openstack.org

2010-present, OpenStack Foundation


and that's the whole vibe check, bestie 🫢 this was nova version 34.0.0, dated Oct 01, 2026, and honestly? she ate. go coordinate some databases. mwah. πŸ’…πŸ’–β­

πŸ“¦ where this page comes from