openstack/glance
Code Issues Proposed changes

Adds sql_ config settings to glance-api.conf.

Browse Source 
The Glance v2 API makes use of the DB directly. As such
we should include the sql_ configs in the default glance-api.conf
file.

Fixes LP Bug #1003504.

Change-Id: I5e287dafcd65864f56789ae22bab3dcc6b353a47
This commit is contained in:
Dan Prince 2012-05-23 11:56:10 -04:00
parent 9462474c14
commit a92b01fe58
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
etc/glance-api.conf
View File

@ -32,6 +32,20 @@ log_file = /var/log/glance/api.log
# Backlog requests when creating socket
backlog = 4096
# SQLAlchemy connection string for the reference implementation
# registry server. Any valid SQLAlchemy connection string is fine.
# See: http://www.sqlalchemy.org/docs/05/reference/sqlalchemy/connections.html#sqlalchemy.create_engine
sql_connection = sqlite:///glance.sqlite
# Period in seconds after which SQLAlchemy should reestablish its connection
# to the database.
#
# MySQL uses a default `wait_timeout` of 8 hours, after which it will drop
# idle connections. This can result in 'MySQL Gone Away' exceptions. If you
# notice this, you can lower this value to ensure that SQLAlchemy reconnects
# before MySQL can drop the connection.
sql_idle_timeout = 3600
# Number of Glance API worker processes to start.
# On machines with more than one CPU increasing this value
# may improve performance (especially if using SSL with