Scroll to navigation

GLANCE-MANAGE(1) glance GLANCE-MANAGE(1)

NAME

glance-manage - Glance Management Utility

GLANCE MANAGEMENT UTILITY

OpenStack Glance Project Team
glance@lists.launchpad.net
2019-04-10
OpenStack Foundation
18.0.0
1
cloud computing

SYNOPSIS

glance-manage [options]


DESCRIPTION

glance-manage is a utility for managing and configuring a Glance installation. One important use of glance-manage is to setup the database. To do this run:

glance-manage db_sync


Note: glance-manage commands can be run either like this:

glance-manage db sync


or with the db commands concatenated, like this:

glance-manage db_sync


COMMANDS

This is the prefix for the commands below when used with a space rather than a _. For example "db version".
This will print the current migration level of a glance database.
This will take an existing database and upgrade it to the specified VERSION.
Place the database under migration control.
Place an existing database under migration control and upgrade it to the specified VERSION.
Run this command to expand the database as the first step of a rolling upgrade process.
Run this command to migrate the database as the second step of a rolling upgrade process.
Run this command to contract the database as the last step of a rolling upgrade process.
Export the metadata definitions into json format. By default the definitions are exported to /etc/glance/metadefs directory. Note: this command will overwrite existing files in the supplied or default path.
Load the metadata definitions into glance database. By default the definitions are imported from /etc/glance/metadefs directory.
Unload the metadata definitions. 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.

OPTIONS

General Options

Show the help message and exit
Print the version number and exit
Print more verbose output
Disable verbose output
Print debugging output (set logging level to DEBUG instead of default WARNING level)
Disable debugging output
Use syslog for logging
Disable the use of syslog for logging
syslog facility to receive log lines
Path to a config directory to pull *.conf files from. This file set is sorted, to provide a predictable parse order if individual options are 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. This means that configuration from files in a specified config-dir will always take precedence over configuration from files specified by --config-file, regardless to argument order.
Path to a config file to use. Multiple config files can be specified by using this flag multiple times, for example, --config-file <file1> --config-file <file2>. Values in latter files take precedence.
The name of logging configuration file. It does not disable existing loggers, but just appends specified logging configuration to any other existing logging options. Please see the Python logging module documentation for details on logging configuration files. The log-config name for this option is deprecated.
A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. Default: None
Format string for %(asctime)s in log records. Default: None
(Optional) Name of log file to output to. If not set, logging will go to stdout.
(Optional) The directory to keep log files in (will be prepended to --log-file)

SEE ALSO

OpenStack Glance

BUGS

Glance bugs are tracked in Launchpad so you can view current bugs at OpenStack Glance

CONFIGURATION

The following paths are searched for a glance-manage.conf file in the following order:

  • ~/.glance
  • ~/
  • /etc/glance
  • /etc

All options set in glance-manage.conf override those set in glance-api.conf.

AUTHOR

OpenStack

COPYRIGHT

2010-present, OpenStack Foundation.

March 30, 2022