GLANCE-API(1)

πŸ’– GLANCE-API πŸ’–

okay bestie, welcome to the glance-api man page β€” that's the Glance API Server, living in manual section 1, filed under the cloud computing manual group. it's giving server daemon realness. 🫢


🌸 SERVER FOR THE GLANCE IMAGE SERVICE API 🌸

before we get into the whole thing, here's the lil cast list of who made this and when, because credits matter, periodt:

  • Author: OpenStack Glance Project Team
  • Contact: <glance@lists.launchpad.net>
  • Date: 2025-04-02
  • Copyright: OpenStack Foundation
  • Version: 30.0.0
  • Manual section: 1
  • Manual group: cloud computing

✨ SYNOPSIS ✨

glance-api [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

glance-api is a server daemon that serves the Glance API. that's the whole vibe. no cap, that's literally it β€” it sits there, it serves the API, it slays. πŸ’…


πŸ‘‘ OPTIONS πŸ‘‘

🌈 General options

this is the main character section. every single flag, right here, nothing skipped, iykyk:

  • -h, --help β€” shows you the help message, then dips out and exits. πŸŽ€
  • --version β€” prints the version number and exits.
  • -v, --verbose β€” prints more verbose output. more words, more lore.
  • --noverbose β€” turns verbose output off. βœ‹
  • -d, --debug β€” prints debugging output (sets the logging level to DEBUG instead of the default WARNING level). the way that it tells you *everything*… LOL. πŸ”₯
  • --nodebug β€” disables debugging output.
  • --use-syslog β€” uses syslog for logging. πŸ“
  • --nouse-syslog β€” disables the use of syslog for logging.
  • --syslog-log-facility SYSLOG_LOG_FACILITY β€” the syslog facility that receives the log lines.
  • --config-dir DIR β€” path to a config directory to pull *.conf files from. this file set is sorted, so you get a predictable parse order if individual options get over-ridden. the set is parsed after the file(s) specified via previous --config-file arguments β€” hence over-ridden options in the directory take precedence. which means: configuration from files in a specified --config-dir will always take precedence over configuration from files specified by --config-file, regardless of argument order. not me re-reading that twice, but it's important, bestie. ⭐
  • --config-file PATH β€” path to a config file to use. you can specify multiple config files by using this flag multiple times, like, for example, --config-file <file1> --config-file <file2>. values in the latter files take precedence. πŸ‘‘
  • --log-config-append PATH --log-config PATH β€” the name of the logging configuration file. it does not disable existing loggers β€” it just appends the specified logging configuration to any other existing logging options. please see the Python logging module documentation for the details on logging configuration files. heads up: the log-config name for this option is deprecated. πŸ’€
  • --log-format FORMAT β€” a logging.Formatter log message format string, which may use any of the available logging.LogRecord attributes. Default: None
  • --log-date-format DATE_FORMAT β€” format string for %(asctime)s in log records. Default: None
  • --log-file PATH, --logfile PATH β€” (optional) name of the log file to output to. if it's not set, logging will go to stdout. 🌸
  • --log-dir LOG_DIR, --logdir LOG_DIR β€” (optional) the directory to keep log files in (this will be prepended to --log-file).

πŸŽ€ FILES πŸŽ€

  • /etc/glance/glance-api.conf β€” the default configuration file for Glance API. your home base, honestly. πŸ’œ

πŸ’« SEE ALSO πŸ’«


πŸ™ˆ BUGS πŸ™ˆ

  • Glance bugs are tracked in Launchpad, so you can view current bugs at OpenStack Glance <http://bugs.launchpad.net/glance>. go be nosy, bestie, it's encouraged. πŸ›

🧚 Author

OpenStack

2010-present, OpenStack Foundation.


so that's the whole page!! every flag, every path, every default, all of it, untouched. no cap. 🫢✨

and a lil sign-off: this one's version 33.0.0, dated Sep 30, 2026, and it's the GLANCE-API(1) page you just read. bye bestie, go serve that API πŸ’…πŸŒˆβ­

πŸ“¦ where this page comes from