Bug 1041877

Summary:	[RFE][keystone]: Use Dogpile.cache as a KVS abstraction for backends
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, ayoung, breeler, markmc, nkinder, ukalifon, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/dogpile-kvs-backends
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-keystone-2014.1-4.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-22 11:50:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:50:39 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/dogpile-kvs-backends.

Description:

THe Dogpile.cache library provides a common API that will support inmemory KVS and Memcahced, as well as persistant KV stores such as Cassandra.  THe CUrrent KVS backends will instead use  Dogpile, and the differences between them will be handled in keystoen/common/dogpile

Specification URL (additional information):

None

Comment 4 Nathan Kinder 2014-06-25 18:28:48 UTC

This is a purely internal change, so there is no need to provide a documentation update.