openstack/openstack-manuals
Code Issues Proposed changes
dab9a830d4
openstack-manuals/doc/admin-guide/source/objectstorage-tenant-specific-image-storage.rst
qiaomin 84b1a2ffed [admin-guide] Use "project" to replace "tenant" term in admin-guide 
This patch use "project" to replace "tenant" term in admin-guide for
cleanup.

Change-Id: I879a6c1ecfbbed2d8db0a02457d06375a268b176
Partial-Bug: #1475005
2016-09-22 14:15:50 +00:00

1.3 KiB
Raw Blame History

Configure project-specific image locations with Object Storage

For some deployers, it is not ideal to store all images in one place to enable all projects and users to access them. You can configure the Image service to store image data in project-specific image locations. Then, only the following projects can use the Image service to access the created image:

  • The project who owns the image
  • Projects that are defined in swift_store_admin_tenants and that have admin-level accounts

To configure project-specific image locations

  1. Configure swift as your default_store in the glance-api.conf file.
  2. Set these configuration options in the glance-api.conf file:
    • swift_store_multi_tenant

      Set to True to enable tenant-specific storage locations. Default is False.

    • swift_store_admin_tenants

      Specify a list of tenant IDs that can grant read and write access to all Object Storage containers that are created by the Image service.

With this configuration, images are stored in an Object Storage service (swift) endpoint that is pulled from the service catalog for the authenticated user.