3 navsection: installguide
4 title: Install Keepstore servers
7 Copyright (C) The Arvados Authors. All rights reserved.
9 SPDX-License-Identifier: CC-BY-SA-3.0
12 Keepstore provides access to underlying storage for reading and writing content-addressed blocks, with enforcement of Arvados permissions. Keepstore supports a variety of cloud object storage and POSIX filesystems for its backing store.
14 h2. Plan your storage layout
16 In the steps below, you will configure a number of backend storage volumes (like local filesystems and S3 buckets) and specify which keepstore servers have read-only and read-write access to which volumes.
18 It is possible to configure arbitrary server/volume layouts. However, in order to provide good performance and efficient use of storage resources, we strongly recommend using one of the following layouts:
20 # Each volume is writable by exactly one server, and optionally readable by one or more other servers. The total capacity of all writable volumes is the same for each server.
21 # Each volume is writable by all servers. Each volume has enough built-in redundancy to satisfy your requirements, i.e., you do not need Arvados to mirror data across multiple volumes.
23 We recommend starting off with two Keepstore servers. Exact server specifications will be site and workload specific, but in general keepstore will be I/O bound and should be set up to maximize aggregate bandwidth with compute nodes. To increase capacity (either space or throughput) it is straightforward to add additional servers, or (in cloud environments) to increase the machine size of the existing servers.
25 By convention, we use the following hostname pattern:
28 table(table table-bordered table-condensed).
30 |keep0.@ClusterID@.example.com|
31 |keep1.@ClusterID@.example.com|
34 Keepstore servers should not be directly accessible from the Internet (they are accessed via "keepproxy":install-keepproxy.html), so the hostnames only need to resolve on the private network.
36 h2. Update cluster config
40 Add each keepstore server to @/etc/arvados/config.yml@ .
45 # No ExternalURL because they are only accessed by the internal subnet.
47 "http://<span class="userinput">keep0.ClusterID.example.com</span>:25107/": {}
48 "http://<span class="userinput">keep1.ClusterID.example.com</span>:25107/": {}
53 h3. Configure storage volumes
55 Available storage volume types include POSIX filesystems and cloud object storage.
57 * To use a POSIX filesystem, including both local filesystems (ext4, xfs) and network file system such as GPFS or Lustre, follow the setup instructions on "Filesystem storage":configure-fs-storage.html
58 * If you are using S3-compatible object storage (including Amazon S3, Google Cloud Storage, and Ceph RADOS), follow the setup instructions on "S3 Object Storage":configure-s3-object-storage.html
59 * If you are using Azure Blob Storage, follow the setup instructions on "Azure Blob Storage":configure-azure-blob-storage.html
61 h2. Install keepstore package
63 On each host that will run keepstore, install the @keepstore@ package.
68 <pre><code># <span class="userinput">yum install keepstore</span>
75 <pre><code># <span class="userinput">apt-get install keepstore</span>
79 h2. Restart the API server and controller
81 After adding all of your keepstore servers to the Services section, make sure the cluster config file is up to date on the API server host, and restart the API server and controller processes to ensure the changes are applied.
84 <pre><code># <span class="userinput">systemctl restart nginx arvados-controller</span>
88 h2(#testing). Testing keep
90 Install the "Python SDK":{{site.baseurl}}/sdk/python/sdk-python.html
92 @ARVADOS_API_HOST@ and @ARVADOS_API_TOKEN@ must be set in the environment.
94 You should now be able to use @arv-put@ to upload collections and @arv-get@ to fetch collections:
97 $ echo "hello world!" > hello.txt
99 $ arv-put --portable-data-hash hello.txt
100 2018-07-12 13:35:25 arvados.arv_put[28702] INFO: Creating new cache file at /home/example/.cache/arvados/arv-put/1571ec0adb397c6a18d5c74cc95b3a2a
101 0M / 0M 100.0% 2018-07-12 13:35:27 arvados.arv_put[28702] INFO:
103 2018-07-12 13:35:27 arvados.arv_put[28702] INFO: Collection saved as 'Saved at 2018-07-12 17:35:25 UTC by example@example'
104 59389a8f9ee9d399be35462a0f92541c+53
106 $ arv-get 59389a8f9ee9d399be35462a0f92541c+53/hello.txt
110 h3. Note on storage management
112 On its own, a keepstore server never deletes data. Instead, the keep-balance service determines which blocks are candidates for deletion and instructs the keepstore to move those blocks to the trash. Please see the "Balancing Keep servers":{{site.baseurl}}/admin/keep-balance.html for more details.