Use the distributed memcached locked dbm cache backend

This commit switches the backend used on the api server to be the dbm
file backend with using memcached for distributed locking. This enables
having an async worker, but avoids the size limitations with storing
the cached data in memcached directly.

Change-Id: If506bbca1eb867135430c7f435c5e4a1db1a0232
Depends-On: Ied241ca1762c62a047bd366d7bd105028a884f30
changes/03/324103/1
Matthew Treinish 2016-06-01 17:04:53 -04:00
parent 814b6585e5
commit c94f14be3d
No known key found for this signature in database
GPG Key ID: FD12A0F214C9E177
2 changed files with 1 additions and 2 deletions

View File

@ -105,7 +105,7 @@ class openstack_health::api(
}
exec { 'requirements':
command => "${virtualenv_dir}/bin/pip install -U -r ${source_dir}/requirements.txt pylibmc",
command => "${virtualenv_dir}/bin/pip install -U -r ${source_dir}/requirements.txt",
require => [
Python::Virtualenv[$virtualenv_dir],
Package['libmemcached-dev'],

View File

@ -1,7 +1,6 @@
[default]
query_dir = <%= @elastic_recheck_dir %>/queries
cache_expiration = <%= @cache_expiration %>
cache_backend = dogpile.cache.pylibmc
cache_url = 127.0.0.1
db_uri = <%= scope.lookupvar("openstack_health::api::db_uri") %>
<% if @ignored_keys.length > 0 -%>