The OpenStack Image Service acts as a registry for virtual disk images. Users can add new images or take a snapshot of an image from an existing server for immediate storage. Use snapshots for back up and as templates to launch new servers. You can store registered images in Object Storage or in other locations. For example, you can store images in simple file systems or external web servers.
![]() | Note |
---|---|
This procedure assumes you set the appropriate environment variables to your credentials as described in the section called “Verify the Identity Service installation”. |
Install the Image Service on the controller node:
# apt-get install glance python-glanceclient
Respond to prompts for database management,
[keystone_authtoken]
settings, RabbitMQ credentials and API endpoint registration. You must also select the caching type:The Image Service stores information about images in a database. The examples in this guide use the MySQL database that is used by other OpenStack services.
Configure the location of the database. The Image Service provides the
glance-api
andglance-registry
services, each with its own configuration file. You must update both configuration files throughout this section. ReplaceGLANCE_DBPASS
with your Image Service database password.Edit
/etc/glance/glance-api.conf
and/etc/glance/glance-registry.conf
and edit the[database]
section of each file:... [database] connection = mysql://glance:GLANCE_DBPASS@
controller
/glanceRestart the
glance
service with its new settings:# service glance-registry restart # service glance-api restart