openstack-manuals/doc/common/section_tenant-specific-image-storage.xml
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

36 lines
1.9 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="configuring-tenant-specific-storage-for-images">
<title>Configuring Tenant-specific Storage Locations for Images
with Object Storage</title>
<para>For some deployers, storing all images in a single place for
all tenants and users to access is not ideal. To enable access
control to specific images for cloud users, you can configure
the Image service with the ability to store image data in the
image owner-specific locations.</para>
<para>The relevant configuration options in the
<filename>glance-api.conf</filename> file are:</para>
<itemizedlist>
<listitem>
<para><literal>swift_store_multi_tenant</literal>: set to
<literal>True</literal> to enable tenant-specific storage locations (Default
value is <literal>False</literal>).</para>
</listitem>
<listitem>
<para><literal>swift_store_admin_tenants</literal>: Specify a list of tenants
by ID to which to grant read and write access to all Object Storage
containers created by the Image service.</para>
</listitem>
</itemizedlist>
<para>Assuming you configured 'swift' as your default_store in
<filename>glance-api.conf</filename> and you enable this
feature as described above, images will be stored in an Object
Storage service (swift) endpoint pulled from the authenticated
user's service_catalog. The created image data will only be
accessible through the Image service by the tenant that owns
it and any tenants defined in swift_store_admin_tenants that
are identified as having admin-level accounts.</para>
</section>