does glance bzr129 version support swift
Hi Everyone, I configured a virtual machine with swift using this guide:
http://swift.openstack.org/development_saio.html (http://swift.openstack.org/developmen...)
and in the cloud controller I'm using glance imaging service, here is the config file of glance:
[DEFAULT]
Show more verbose log output (sets INFO log level output)
verbose = True
Show debugging output in logs (sets DEBUG log level output)
debug = False
[app:glance-api] paste.app_factory = glance.server:app_factory
Which backend store should Glance use by default is not specified
in a request to add a new image to Glance? Default: 'file'
Available choices are 'file', 'swift', and 's3'
default_store = swift
Address to bind the API server
bind_host = 0.0.0.0
Port the bind the API server to
bind_port = 9292
Address to find the registry server
registry_host = 0.0.0.0
Port the registry server is listening on
registry_port = 9191
Log to this file. Make sure you do not set the same log
file for both the API and registry servers!
log_file = /var/log/glance/api.log
============ Filesystem Store Options ========================
Directory that the Filesystem backend store
writes image data to
filesystem_store_datadir = /var/lib/glance/images/
============ Swift Store Options =============================
Address where the Swift authentication service lives
swift_store_auth_address = 192.168.1.217:8080/auth/v1.0/
User to authenticate against the Swift authentication service
swift_store_user = test:tester
Auth key for the user authenticating against the
Swift authentication service
swift_store_key = testing
Container within the account that the account should use
for storing images in Swift
swift_store_container = glance
Do we create the container if it does not exist?
swift_store_create_container_on_put = true
[app:glance-registry] paste.app_factory = glance.registry.server:app_factory
Address to bind the registry server
bind_host = 0.0.0.0
Port the bind the registry server to
bind_port = 9191
Log to this file. Make sure you do not set the same log
file for both the API and registry servers!
log_file = /var/log/glance/registry.log
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 (http://www.sqlalchemy.org/docs/05/ref...)
sql_connection = sqlite:////var/lib/glance/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
When I tried to add an image to glance I got the following error:
glance add --verbose name="Centos 5.5 Qcow2-2-SWIFT" is_public=true disk_format=qcow2 container_format=bare < Centos5.5-32Bits_1.0rev2_vhd/Centos5.5-32Bits_1.0rev2.qcow2 Failed to add image. Got error: 400 Bad Request
The server could not comply with the request since it is either malformed or otherwise incorrect.
Error uploading image: No module named swift.common
Note: Your image metadata may still be in the registry, but the image's status ...