From e7d6210e70c35c0a163b455a2b1b6f81f6fc5dd6 Mon Sep 17 00:00:00 2001 From: Brian Waldon Date: Thu, 30 Aug 2012 11:00:38 -0700 Subject: [PATCH] Document how to deploy cachemanage middleware Related to bp glance-folsom-docs-cleanup Change-Id: If72a82222ebf33b08bbceba2d780bddfe7b7aad0 --- doc/source/configuring.rst | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/doc/source/configuring.rst b/doc/source/configuring.rst index 714926b9..6fbc9deb 100644 --- a/doc/source/configuring.rst +++ b/doc/source/configuring.rst @@ -607,11 +607,25 @@ configuration file, select the appropriate deployment flavor like so:: [paste_deploy] flavor = caching -And that would give you a transparent image cache on the API server. +Enabling the Image Cache Management Middleware +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +There is an optional ``cachemanage`` middleware that allows you to +directly interact with cache images. Use this flavor in place of the +``cache`` flavor in your api config file. + + [paste_deploy] + flavor = cachemanage Configuration Options Affecting the Image Cache ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. note:: + + These configuration options must be set in both the glance-cache + and glance-api configuration files. + + One main configuration file option affects the image cache. * ``image_cache_dir=PATH`` @@ -666,10 +680,6 @@ to or less than this value. The ``glance-cache-pruner`` executable is designed to be run via cron on a regular basis. See more about this executable in :doc:`Controlling the Growth of the Image Cache ` -.. note:: - - These configuration options must be set in both the glance-cache - and glance-api configuration files. Configuring the Glance Registry -------------------------------