Atom feed of this document
  
 

 Install the Image Service

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]Note

This procedure assumes you set the appropriate environment variables to your credentials as described in the section called “Verify the Identity Service installation”.

  1. Install the Image Service on the controller node:

    # apt-get install glance python-glanceclient
  2. 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 and glance-registry services, each with its own configuration file. You must update both configuration files throughout this section. Replace GLANCE_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/glance
  3. Configure the Image Service to use the message broker:

    1. Edit the /etc/glance/glance-api.conf file and add the following keys to the [DEFAULT] section:

      Replace RABBIT_PASS with the password you chose for the guest account in RabbitMQ.

      [DEFAULT]
      ...
      rpc_backend = rabbit
      rabbit_host = controller
      rabbit_password = RABBIT_PASS
  4. By default, the Ubuntu packages create an SQLite database. Delete the glance.sqlite file created in the /var/lib/glance/ directory so that it does not get used by mistake:

    # rm /var/lib/glance/glance.sqlite
  5. Use the password you created to log in as root and create a glance database user:

    $ mysql -u root -p
    mysql> CREATE DATABASE glance;
    mysql> GRANT ALL PRIVILEGES ON glance.* TO 'glance'@'localhost' \
    IDENTIFIED BY 'GLANCE_DBPASS';
    mysql> GRANT ALL PRIVILEGES ON glance.* TO 'glance'@'%' \
    IDENTIFIED BY 'GLANCE_DBPASS';
  6. Create the database tables for the Image Service:

    # su -s /bin/sh -c "glance-manage db_sync" glance
  7. Create a glance user that the Image Service can use to authenticate with the Identity service. Choose a password and specify an email address for the glance user. Use the service tenant and give the user the admin role:

    $ keystone user-create --name=glance --pass=GLANCE_PASS \
       --email=[email protected]
    $ keystone user-role-add --user=glance --tenant=service --role=admin
  8. Configure the Image Service to use the Identity Service for authentication.

    Edit the /etc/glance/glance-api.conf and /etc/glance/glance-registry.conf files. Replace GLANCE_PASS with the password you chose for the glance user in the Identity service.

    1. Add or modify the following keys under the [keystone_authtoken] section:

      [keystone_authtoken]
      auth_uri = http://controller:5000
      auth_host = controller
      auth_port = 35357
      auth_protocol = http
      admin_tenant_name = service
      admin_user = glance
      admin_password = GLANCE_PASS
    2. Modify the following key under the [paste_deploy] section:

      [paste_deploy]
      ...
      flavor = keystone
  9. Register the Image Service with the Identity service so that other OpenStack services can locate it. Register the service and create the endpoint:

    $ keystone service-create --name=glance --type=image \
      --description="OpenStack Image Service"
    $ keystone endpoint-create \
      --service-id=$(keystone service-list | awk '/ image / {print $2}') \
      --publicurl=http://controller:9292 \
      --internalurl=http://controller:9292 \
      --adminurl=http://controller:9292
  10. Restart the glance service with its new settings:

    # service glance-registry restart
    # service glance-api restart
Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page

loading table of contents...