
As specified in the blueprint, we are only going to set log_file in the configuration file for now, and we read it last in glance.cmd.manage. This allows glance-manage to use the appropriate log-file and still retain the settings it needs in glance-api.conf and glance-registry.conf DocImpact Change-Id: I87595a29634e6ffda4e1581d42a92dfe6f84044b Implements: blueprint create-glance-manage-conf Closes-bug: #1391211
2.0 KiB
glance-manage
Glance Management Utility
- Author
- Date
-
2014-01-16
- Copyright
-
OpenStack LLC
- Version
-
2014.1
- Manual section
-
1
- Manual group
-
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
- db
This is the prefix for the commands below when used with a space rather than a _. For example "db version".
- db_version
This will print the current migration level of a glance database.
- db_upgrade <VERSION>
This will take an existing database and upgrade it to the specified VERSION.
- db_downgrade <VERSION>
This will take an existing database and downgrade it to the specified VERSION.
- db_version_control
Place the database untder migration control.
- db_sync <VERSION> <CURRENT_VERSION>
Place a database under migration control and upgrade, creating it first if necessary.
OPTIONS
General Options
- --sql_connection=CONN_STRING
A proper SQLAlchemy connection string as described here
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-registry.conf
and
glance-api.conf
.