summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rabel <rabel@b1-systems.de>2018-01-17 18:58:59 +0100
committerDavid Rabel <rabel@b1-systems.de>2018-02-12 14:20:39 +0000
commitfff76ae4d26d9a5398df21e46577ea374a0b2d65 (patch)
tree10bfb7c20d49db182cbe9f5e961b3bd03c55a18b
parent08e28cd921920cf8f5401c839376b65c19a97880 (diff)
downloadglance-fff76ae4d26d9a5398df21e46577ea374a0b2d65.tar.gz
Fix format cache.rst
Fix format in doc/source/admin/cache.rst : - Fix indentation. - Add two missing bullet points. Change-Id: I8d88c9f1b15f7de7159bfda662aca0c7ad1b47ed
-rw-r--r--doc/source/admin/cache.rst44
1 files changed, 22 insertions, 22 deletions
diff --git a/doc/source/admin/cache.rst b/doc/source/admin/cache.rst
index f1de58b62..d4f852afe 100644
--- a/doc/source/admin/cache.rst
+++ b/doc/source/admin/cache.rst
@@ -117,17 +117,17 @@ from a local cache.
To queue an image for prefetching, you can use one of the following methods:
- * If the ``cache_manage`` middleware is enabled in the application pipeline,
- you may call ``PUT /queued-images/<IMAGE_ID>`` to queue the image with
- identifier ``<IMAGE_ID>``
+* If the ``cache_manage`` middleware is enabled in the application pipeline,
+ you may call ``PUT /queued-images/<IMAGE_ID>`` to queue the image with
+ identifier ``<IMAGE_ID>``
- Alternately, you can use the ``glance-cache-manage`` program to queue the
- image. This program may be run from a different host than the host
- containing the image cache. Example usage::
+* Alternately, you can use the ``glance-cache-manage`` program to queue the
+ image. This program may be run from a different host than the host
+ containing the image cache. Example usage::
- $> glance-cache-manage --host=<HOST> queue-image <IMAGE_ID>
+ $> glance-cache-manage --host=<HOST> queue-image <IMAGE_ID>
- This will queue the image with identifier ``<IMAGE_ID>`` for prefetching
+ This will queue the image with identifier ``<IMAGE_ID>`` for prefetching
Once you have queued the images you wish to prefetch, call the
``glance-cache-prefetcher`` executable, which will prefetch all queued images
@@ -139,26 +139,26 @@ Finding Which Images are in the Image Cache
You can find out which images are in the image cache using one of the
following methods:
- * If the ``cachemanage`` middleware is enabled in the application pipeline,
- you may call ``GET /cached-images`` to see a JSON-serialized list of
- mappings that show cached images, the number of cache hits on each image,
- the size of the image, and the times they were last accessed.
+* If the ``cachemanage`` middleware is enabled in the application pipeline,
+ you may call ``GET /cached-images`` to see a JSON-serialized list of
+ mappings that show cached images, the number of cache hits on each image,
+ the size of the image, and the times they were last accessed.
- Alternately, you can use the ``glance-cache-manage`` program. This program
- may be run from a different host than the host containing the image cache.
- Example usage::
+* Alternately, you can use the ``glance-cache-manage`` program. This program
+ may be run from a different host than the host containing the image cache.
+ Example usage::
- $> glance-cache-manage --host=<HOST> list-cached
+ $> glance-cache-manage --host=<HOST> list-cached
- * You can issue the following call on \*nix systems (on the host that contains
- the image cache)::
+* You can issue the following call on \*nix systems (on the host that contains
+ the image cache)::
- $> ls -lhR $IMAGE_CACHE_DIR
+ $> ls -lhR $IMAGE_CACHE_DIR
- where ``$IMAGE_CACHE_DIR`` is the value of the ``image_cache_dir``
- configuration variable.
+ where ``$IMAGE_CACHE_DIR`` is the value of the ``image_cache_dir``
+ configuration variable.
- Note that the image's cache hit is not shown using this method.
+ Note that the image's cache hit is not shown using this method.
Manually Removing Images from the Image Cache
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~