NOVA-API-OS-COMPUTE(1)

📦
version 29.2.0 · 5 versions
, in ubuntu noble

✨ NOVA-API-OS-COMPUTE ✨

okay bestie, welcome to the nova-api-os-compute(1) glow-up 💖 this is the manual page for the Nova OpenStack Compute API server daemon, and we're gonna go through it together, no skimming, no skipping, because every single flag here matters and I refuse to let you miss one.

🎀 NAME 🎀

nova-api-os-compute — the server for the OpenStack Compute API service. that's it, that's the whole vibe. she's a server daemon, she serves, she's the moment. 👑

🌸 SYNOPSIS 🌸

nova-api-os-compute [<options>...]

like, that's the whole thing. just run her with whatever options you need, and honestly? iconic behaviour.

🦋 DESCRIPTION 🦋

so nova-api-os-compute is a server daemon that serves the Nova OpenStack Compute API. that's her whole job, that's her whole personality, and she's so good at it. if you're trying to talk to the Compute API, this is the girl you're talking to. no cap. ✨

💅 OPTIONS 💅

🍓 General options 🍓

okay this is the big one, bestie. grab a snack. 🥤

  • --config-dir DIR — path to a config directory to pull *.conf files from. this file set is sorted, so the parse order is predictable if individual options get over-ridden. it's parsed after the file(s) you specified via previous --config-file arguments, so any over-ridden options living in the directory win. ⚠️ 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. defaults to None. also must be set from the command-line. 💅
  • --debug, -d — sets the logging level to DEBUG instead of the default INFO level. living your truth, loudly. 🔥
  • --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 details about logging configuration files, go look at the Python logging module documentation. heads up though: when logging configuration files are used, all logging configuration is set in the configuration file and the other logging configuration options get ignored (like, for example, log-date-format). 🫶
  • --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. ignored if log_config_append is set. 💜
  • --log-file PATH, --logfile PATH — (optional) name of the log file to send logging output to. if no default is set, logging goes to stderr as defined by use_stderr. ignored if log_config_append is set. 🌸
  • --nodebug — the inverse of --debug. ✨
  • --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 — the syslog facility that receives log lines. ignored if log_config_append is set. 📮
  • --use-journal — enable journald for logging. if you're running in a systemd environment you might wanna turn journal support on. doing that uses 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. 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. ignored if log_config_append is set.
  • --version — show the program's version number and exit. short queen behaviour. 👑
  • --watch-log-file — uses a logging handler designed to watch the file system. when the log file gets 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 you're on a Linux platform. ignored if log_config_append is set. 🔍

🌈 Debugger options 🌈

okay so listen. these two are giving "I know what I'm doing" energy, and if you don't, maybe don't. 🫣
  • --remote_debug-host REMOTE_DEBUG_HOST — debug host (IP or name) to connect to. this command line parameter is used when you want to connect to a nova service via a debugger running on a different host. 🚨 note that using the remote debug option changes how Nova uses the eventlet library to support async IO. this could result in failures that do not occur under normal operation. use at your own risk. fr fr.
  • --remote_debug-port REMOTE_DEBUG_PORT — debug port to connect to. this command line parameter lets you specify the port you want to use to connect to a nova service via a debugger running on a different host. 🚨 same warning, bestie: using the remote debug option changes how Nova uses the eventlet library to support async IO, and this could result in failures that do not occur under normal operation. use at your own risk. 💀

🗂️ FILES 🗂️

here's where she keeps her stuff, and yes, we're listing all of them:

  • /etc/nova/nova.conf
  • /etc/nova/api-paste.ini
  • /etc/nova/policy.yaml
  • /etc/nova/policy.d/
  • /etc/nova/rootwrap.conf
  • /etc/nova/rootwrap.d/

👀 SEE ALSO 👀

go read these too, they're part of the friend group:

🐛 BUGS 🐛

  • Nova bugs are managed at Launchpad. that's the spot. take it there. 📍

💌 AUTHOR 💌

openstack@lists.openstack.org

2010-present, OpenStack Foundation

and that's the whole page, bestie!! 💖 you just read nova-api-os-compute, from the nova manual, version 29.2.0, dated Jun 10, 2026. go forth, serve that Compute API, and remember: every option above is load-bearing, so don't skip any. slay, periodt, bye!! ✨💅🦋

📦 where this page comes from