GLANCE-MANAGE(1)

📦
version 33.0.0 · 11 versions
, in ubuntu stonking

🎀 glance-manage 🎀

okay bestie, sit down, hydrate, and let me tell you about glance-manage — it's the management utility for Glance, and honestly? it's giving little-black-dress-of-OpenStack-tooling. it does the unglamorous but iconic work. 💅

✨ GLANCE MANAGEMENT UTILITY ✨

here's the receipts on who made this and what it is, so you know it's legit:

  • 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-manage [options]

💖 DESCRIPTION

glance-manage is the utility that manages and configures a Glance installation, no cap. and the one job people hit the most? setting up the database. to do that, you literally just run:

glance-manage db_sync
📌 note bestie: glance-manage commands can be run either like this:
glance-manage db sync
or with the db commands concatenated, with that underscore, like this:
glance-manage db_sync

both slay. same energy. pick your fave. 🫶

🧚 COMMANDS

  • db — this here is the prefix for all the commands below, for when you're using a space instead of a _. so like, "db version". iykyk.
  • db_version — prints out the current migration level of a glance database. it's the vibe check for your schema. 🌈
  • db_upgrade [VERSION] — grabs an existing database and upgrades it all the way to the VERSION you specify. glow-up time.
  • db_version_control — places the database under migration control. welcome to the system, babe.
  • db_sync [VERSION] — puts an existing database under migration control and upgrades it to the specified VERSION. it's two steps, one command, we love efficiency. ✨
  • db_expand — run this one as the first step of a rolling upgrade process. database expansion, okayyy.
  • db_migrate — run this as the second step of a rolling upgrade process.
  • db_contract — run this as the last step of a rolling upgrade process. closing the curtains, periodt. 🎭
  • db_export_metadefs [PATH | PREFIX] — exports the metadata definitions out into json format. by default they get exported into the /etc/glance/metadefs directory.
⚠️ note: this command will overwrite existing files in the supplied path or the default path. be careful, bestie, that's destructive behavior fr fr. 😭
  • db_load_metadefs [PATH] — loads the metadata definitions into the glance database. by default it imports them from the /etc/glance/metadefs directory.
  • db_unload_metadefs — unloads the metadata definitions. this one clears the contents of all the glance db tables, including metadef_namespace_resource_types, metadef_tags, metadef_objects, metadef_resource_types, metadef_namespaces and metadef_properties. it's giving spring cleaning but scary. 💀
  • db_purge — purges deleted rows older than a given age from the glance db tables.

when it's invoked, this command interprets the following options:

  • --max_rows — Purge deleted rows older than age in days (default value if not specified: 100)
  • --age_in_days — Limit number of records to delete (default value if not specified: 30 days)
🚨 WARNING: This function is useful primarily in test systems. We do not recommend its use in production systems unless you have reviewed OpenStack Security Note OSSN-0075 https://wiki.openstack.org/wiki/OSSN/OSSN-0075 and understand the risk involved. like, read the note first, queen. 👑
  • db_purge_images_table — purges deleted rows older than a given age from the images db tables.

when it's invoked, this command interprets the following options:

  • --max_rows — Purge deleted rows older than age in days (default value if not specified: 100)
  • --age_in_days — Limit number of records to delete (default value if not specified: 30 days)
🚨 WARNING: This function is useful primarily in test systems. We do not recommend its use in production systems unless you have reviewed OpenStack Security Note OSSN-0075 https://wiki.openstack.org/wiki/OSSN/OSSN-0075 and understand the risk involved. same warning, same energy, do not skip it. 🙈

🛠️ OPTIONS

🌸 General Options

  • -h, --help — shows the help message and then dips out. classic. ✌️
  • --version — prints the version number and exits.
  • -v, --verbose — prints more verbose output. give me all the details, i want the tea. 🍵
  • --noverbose — disables verbose output. shhh mode.
  • -d, --debug — prints debugging output — it sets the logging level to DEBUG instead of the default WARNING level. we're going full detective mode 🔍
  • --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 — the 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. what that 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. so order does not save you here, bestie. 🫠
  • --config-file PATH — the path to a config file to use. you can specify multiple config files by using this flag multiple times, for example, --config-file <file1> --config-file <file2>. values in latter files take precedence. last one wins, main character behavior. 👑
  • --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.
⚠️ the log-config name for this option is deprecated.
  • --log-format FORMAT — a logging.Formatter log message format string, and it may use any of the available logging.LogRecord attributes. Default: None
  • --log-date-format DATE_FORMAT — the format string for %(asctime)s in log records. Default: None
  • --log-file PATH, --logfile PATH — (Optional) Name of log file to output to. If not set, logging will go to stdout.
  • --log-dir LOG_DIR, --logdir LOG_DIR — (Optional) The directory to keep log files in (it will be prepended to --log-file).

👀 SEE ALSO

🐛 BUGS

🌈 CONFIGURATION

these paths get searched for a glance-manage.conf file, in exactly this order:

  1. ~/.glance
  2. ~/
  3. /etc/glance
  4. /etc

and hear me out: every single option set in glance-manage.conf overrides those set in glance-api.conf. so that file is the one holding the aux cord, fr fr. 🎧

💜 Author

OpenStack

2010-present, OpenStack Foundation.

and that's the whole page, bestie ✨ it's version 33.0.0, dated Sep 30, 2026, and it lives in the GLANCE-MANAGE(1) section. go forth and manage your glance, you absolute icon 🎀💖🦋 no cap.

📦 where this page comes from