17204: Fix misleading log message on 304 Not Modified response.

[arvados.git] / doc / admin / storage-classes.html.textile.liquid

diff --git a/doc/admin/storage-classes.html.textile.liquid b/doc/admin/storage-classes.html.textile.liquid
index b518502c70ad50e5b356af5e3136896683d2059b..e5c9a3973fa37226d4866eb5433fb64ae0a8b300 100644 (file)
--- a/doc/admin/storage-classes.html.textile.liquid
+++ b/doc/admin/storage-classes.html.textile.liquid
@@ -1,7 +1,7 @@
 ---
 layout: default
 navsection: admin
-title: Storage classes
+title: Configuring storage classes
 ...
 
 {% comment %}
@@ -12,49 +12,25 @@ SPDX-License-Identifier: CC-BY-SA-3.0
 
 Storage classes (alternately known as "storage tiers") allow you to control which volumes should be used to store particular collection data blocks.  This can be used to implement data storage policies such as moving data to archival storage.
 
-h3. Configuring storage classes
-
 The storage classes for each volume are set in the per-volume "keepstore configuration":{{site.baseurl}}/install/install-keepstore.html
 
 <pre>
-Volumes:
- - ... Volume configuration ...
-   #
-   # If no storage classes are specified, will use [default]
-   #
-   StorageClasses: null
-
- - ... Volume configuration ...
-   #
-   # Specify this volume is in the "archival" storage class.
-   #
-   StorageClasses: [archival]
-
+    Volumes:
+      ClusterID-nyw5e-000000000000000:
+        # This volume is in the "default" storage class.
+        StorageClasses:
+          default: true
+      ClusterID-nyw5e-000000000000001:
+        # Specify this volume is in the "archival" storage class.
+        StorageClasses:
+          archival: true
 </pre>
 
 Names of storage classes are internal to the cluster and decided by the administrator.  Aside from "default", Arvados currently does not define any standard storage class names.
 
 h3. Using storage classes
 
-Desired storage classes are specified by setting the "storage_classes_desired" field of a Collection.  For example, at the command line:
-
-<pre>
-$ arv collection update --uuid zzzzz-4zz18-dhhm0ay8k8cqkvg --collection '{"storage_classes_desired": ["archival"]}'
-</pre>
-
-By setting "storage_classes_desired" to "archival", the blocks that make up the collection will be preferentially moved to keepstore volumes which are configured with the "archival" storage class.
-
-You may also specify the desired storage class when using @arv-put@:
-
-<pre>
-$ arv-put --storage-classes=hot myfile.txt
-</pre>
-
-Collection blocks will be in the "default" storage class if not otherwise specified.
-
-A collection may have only specify one desired storage class.
-
-A user with write access to a collection may set any storage class.
+"Discussed in the user guide":{{site.baseurl}}/user/topics/storage-classes.html
 
 h3. Storage management notes