Bug 1168371

Summary:	[RFE][glance]: Glance Swift Store to use Multiple Containers for Storing Images
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-glance	Assignee:	Flavio Percoco <fpercoco>
Status:	CLOSED ERRATA	QA Contact:	Prasanth Anbalagan <panbalag>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	dnavale, eglynn, fpercoco, markmc, nlevinki, scohen, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/swift-store-multiple-containers
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, Image service's 'swift' store implementation stored all images on a single container. While this worked well, it created a performance bottleneck in large scale deployments. With this update, it is now possible to use several Object Storage containers as storage for the 'glance' images. In order to use this feature, you need to set 'swift_store_multiple_containers_seed' to a value bigger than '0'. You can disable using multiple containers by enabling the 'swift_uer_multi_tenant' parameter, as these containers are split on a per-tenant basis.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:19:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-11-26 17:51:33 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/swift-store-multiple-containers.

Description:

Glance, when configured to use Swift store in Single Tenant Mode, stores images in one container as indicated by the configuration option, swift_store_container. This approach of storing images in ONE container
is subject to performance bottleneck.

Storing images in one container is prone to Swift rate-limiting on containers. Swift is equipped with container rate-limiting that can throttle concurrent POST, PUT and DELETE operations in a single container.
This becomes a serious issue in a large scale deployments especially when coupled with smaller segment sizes.

To reduce/overcome the performance bottleneck, we propose the use of multiple containers for storing images in Single Tenant Mode (this change will not affect Multi Tenant Mode because that setup stores each image in its own container). This leads to increased concurrency of image creation and deletion operations.

Specification URL (additional information):

None

Comment 5 errata-xmlrpc 2015-08-05 13:19:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548