X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/20a69e126c68236a3c73daab101e351346f8bfaf..d22da8c4ae59fa50bfecaf3c5857fe8c0cc5fae7:/doc/install/configure-fs-storage.html.textile.liquid diff --git a/doc/install/configure-fs-storage.html.textile.liquid b/doc/install/configure-fs-storage.html.textile.liquid index 1e13190aa5..be0a48cb8c 100644 --- a/doc/install/configure-fs-storage.html.textile.liquid +++ b/doc/install/configure-fs-storage.html.textile.liquid @@ -1,7 +1,7 @@ --- layout: default navsection: installguide -title: Filesystem storage +title: Configure filesystem storage ... {% comment %} Copyright (C) The Arvados Authors. All rights reserved. @@ -15,7 +15,7 @@ h2. Setting up filesystem mounts Volumes are configured in the @Volumes@ section of the cluster configuration file. You may provide multiple volumes for a single keepstore process to manage multiple disks. Keepstore distributes blocks among volumes in round-robin fashion. -Note that each volume has a UUID, like "zzzzz-nyw5e-0123456789abcde". You can assign these manually, but once assigned they should not be changed. +{% include 'assign_volume_uuid' %} Note that each volume has an AccessViaHosts section indicating that (for example) keep0's /mnt/local-disk directory is volume 0, while keep1's /mnt/local-disk directory is volume 1. @@ -25,7 +25,7 @@ Note that each volume has an AccessViaHosts section indicating that (for example Volumes: uuid_prefix-nyw5e-000000000000000: AccessViaHosts: - "http://keep0.zzzzz.example.com:25107/": {} + "http://keep0.uuid_prefix.example.com:25107": {} Driver: Directory DriverParameters: # The directory that will be used as the backing store. @@ -59,20 +59,29 @@ Note that each volume has an AccessViaHosts section indicating that (for example uuid_prefix-nyw5e-000000000000001: AccessViaHosts: - "http://keep1.zzzzz.example.com:25107/": {} + "http://keep1.uuid_prefix.example.com:25107": {} Driver: Directory DriverParameters: Root: /mnt/local-disk -In the case of a network-attached filesystem accessible by all keepstore servers, the AccessViaHosts section is omitted. +In the case of a network-attached filesystem, the AccessViaHosts section can have multiple entries. If the filesystem is accessible by all keepstore servers, the AccessViaHosts section can be empty, or omitted entirely.
Clusters:
   uuid_prefix:
     Volumes:
-      # This volume is used by all keepstore servers.
       uuid_prefix-nyw5e-000000000000002:
+        AccessViaHosts:
+          # This section determines which keepstore servers access the
+          # volume. In this example, keep0 has read/write access, and
+          # keep1 has read-only access.
+          #
+          # If the AccessViaHosts section is empty or omitted, all
+          # keepstore servers will have read/write access to the
+          # volume.
+          "http://keep0.uuid_prefix.example.com:25107/": {}
+          "http://keep1.uuid_prefix.example.com:25107/": {ReadOnly: true}
         Driver: Directory
         DriverParameters:
           Root: /mnt/network-attached-filesystem