[iyunv@stackcc etc]# for file in *; do diff -u $file /etc/glance/$file; done
--- glance-api.conf 2012-11-14 19:12:12.011623218 +0800
+++ /etc/glance/glance-api.conf 2012-11-16 09:44:37.534701521 +0800
@@ -9,7 +9,7 @@
# in a request to add a new image to Glance? Known schemes are determined
# by the known_stores option below.
# Default: 'file'
-default_store = file
+default_store = swift
# List of which store classes and store class locations are
# currently known to glance at startup.
@@ -46,7 +46,7 @@
# 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
+sql_connection = mysql://glance:glance@localhost/glance
# Period in seconds after which SQLAlchemy should reestablish its connection
# to the database.
@@ -137,7 +137,7 @@
# There are three methods of sending notifications, logging (via the
# log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid
# message queue), or noop (no notifications sent, the default)
-notifier_strategy = noop
+notifier_strategy = qpid
# Configuration options if sending notifications via rabbitmq (these are
# the defaults)
@@ -192,7 +192,7 @@
# If you use Swift authentication service, set it to 'account':'user'
# where 'account' is a Swift storage account and 'user'
# is a user in that account
-swift_store_user = jdoe:jdoe
+swift_store_user = service:glance
# Auth key for the user authenticating against the
# Swift authentication service
@@ -203,7 +203,7 @@
swift_store_container = glance
# Do we create the container if it does not exist?
-swift_store_create_container_on_put = False
+swift_store_create_container_on_put = True
# What size, in MB, should Glance start chunking image files
# and do a large object manifest in Swift? By default, this is
@@ -311,16 +311,16 @@
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
-admin_tenant_name = %SERVICE_TENANT_NAME%
-admin_user = %SERVICE_USER%
-admin_password = %SERVICE_PASSWORD%
+admin_tenant_name = service
+admin_user = glance
+admin_password = service123
[paste_deploy]
# Name of the paste configuration file that defines the available pipelines
-#config_file = glance-api-paste.ini
+config_file = /etc/glance/glance-api-paste.ini
# Partial name of a pipeline in your paste configuration file with the
# service name removed. For example, if your paste section name is
# [pipeline:glance-api-keystone], you would configure the flavor below
# as 'keystone'.
-#flavor=
+flavor=keystone
--- glance-registry.conf 2012-11-14 19:10:51.688606629 +0800
+++ /etc/glance/glance-registry.conf 2012-11-14 19:48:43.600719378 +0800
@@ -25,7 +25,7 @@
# 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
+sql_connection = mysql://glance:glance@localhost/glance
# Period in seconds after which SQLAlchemy should reestablish its connection
# to the database.
@@ -71,16 +71,16 @@
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
-admin_tenant_name = %SERVICE_TENANT_NAME%
-admin_user = %SERVICE_USER%
-admin_password = %SERVICE_PASSWORD%
+admin_tenant_name = service
+admin_user = glance
+admin_password = service123
[paste_deploy]
# Name of the paste configuration file that defines the available pipelines
-#config_file = glance-registry-paste.ini
+config_file = /etc/glance/glance-registry-paste.ini
# Partial name of a pipeline in your paste configuration file with the
# service name removed. For example, if your paste section name is
# [pipeline:glance-registry-keystone], you would configure the flavor below
# as 'keystone'.
-#flavor=
+flavor=keystone