X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/53862c0bfbd654016a16892dbedf382270de3f10..ce47881591ac69a606f8235c9775e87c1075dcd1:/doc/install/install-keepstore.html.textile.liquid?ds=sidebyside diff --git a/doc/install/install-keepstore.html.textile.liquid b/doc/install/install-keepstore.html.textile.liquid index e1bd5f73b2..869ca15d9e 100644 --- a/doc/install/install-keepstore.html.textile.liquid +++ b/doc/install/install-keepstore.html.textile.liquid @@ -9,9 +9,18 @@ Copyright (C) The Arvados Authors. All rights reserved. SPDX-License-Identifier: CC-BY-SA-3.0 {% endcomment %} +# "Introduction":#introduction +# "Update config.yml":#update-config +# "Install keepstore package":#install-packages +# "Restart the API server and controller":#restart-api +# "Confirm working installation":#confirm-working +# "Note on storage management":#note + +h2. Introduction + 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. -h2. Plan your storage layout +h3. Plan your storage layout 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. @@ -26,87 +35,75 @@ By convention, we use the following hostname pattern:
Services:
Keepstore:
# No ExternalURL because they are only accessed by the internal subnet.
InternalURLs:
- "http://keep0.ClusterID.example.com:25107/": {}
- "http://keep1.ClusterID.example.com:25107/": {}
- # and so forth
+ "http://keep0.ClusterID.example.com:25107": {}
+ "http://keep1.ClusterID.example.com:25107": {}
+ # and so forth
# yum install keepstore
-
-# apt-get install keepstore
-
-# systemctl restart nginx arvados-controller
+
+$ arv keep_service accessible
+[...]
-$ echo "hello world!" > hello.txt +If keepstore does not show up in the "accessible" list, and you are accessing it from within the private network, check that you have "properly configured the @geo@ block for the API server":install-api-server.html#update-nginx . -$ arv-put --portable-data-hash hello.txt -2018-07-12 13:35:25 arvados.arv_put[28702] INFO: Creating new cache file at /home/example/.cache/arvados/arv-put/1571ec0adb397c6a18d5c74cc95b3a2a -0M / 0M 100.0% 2018-07-12 13:35:27 arvados.arv_put[28702] INFO: +Next, install the "Python SDK":{{site.baseurl}}/sdk/python/sdk-python.html -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' -59389a8f9ee9d399be35462a0f92541c+53 +You should now be able to use @arv-put@ to upload collections and @arv-get@ to fetch collections. Be sure to execute this from _inside_ the cluster's private network. You will be able to access keep from _outside_ the private network after setting up "keepproxy":install-keepproxy.html . -$ arv-get 59389a8f9ee9d399be35462a0f92541c+53/hello.txt -hello world! -+{% include 'arv_put_example' %} -h3. Note on storage management +h2(#note). Note on storage management 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.