X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/81b8e05dcd7397de4e2facd47be899edb9a21c6a..9bc0194676e3f22b41976fefc6146d7dd965d173:/doc/install/install-keepproxy.html.textile.liquid diff --git a/doc/install/install-keepproxy.html.textile.liquid b/doc/install/install-keepproxy.html.textile.liquid index 26addb7529..5a5b66aaae 100644 --- a/doc/install/install-keepproxy.html.textile.liquid +++ b/doc/install/install-keepproxy.html.textile.liquid @@ -4,9 +4,12 @@ navsection: installguide title: Install Keepproxy server ... -The Keepproxy server is a gateway into your Keep storage. Unlike the Keepstore servers, which are only accessible on the local LAN, Keepproxy is designed to provide secure access into Keep from anywhere on the internet. +The Keepproxy server is a gateway into your Keep storage. Unlike the Keepstore servers, which are only accessible on the local LAN, Keepproxy is suitable for clients located elsewhere on the internet. Specifically, in contrast to Keepstore: +* A client writing through Keepproxy generates less network traffic: the client sends a single copy of a data block, and Keepproxy sends copies to the appropriate Keepstore servers. +* A client can write through Keepproxy without precomputing content hashes. Notably, the browser-based upload feature in Workbench requires Keepproxy. +* Keepproxy checks API token validity before processing requests. (Clients that can connect directly to Keepstore can use it as scratch space even without a valid API token.) -By convention, we use the following hostname for the Keepproxy: +By convention, we use the following hostname for the Keepproxy server:
table(table table-bordered table-condensed). @@ -36,12 +39,13 @@ Verify that Keepproxy is functional:
~$ keepproxy -h
-Usage of default:
+Usage of keepproxy:
   -default-replicas=2: Default number of replicas to write if not specified by the client.
   -listen=":25107": Interface on which to listen for requests, in the format ipaddr:port. e.g. -listen=10.0.1.24:8000. Use -listen=:port to listen on all network interfaces.
   -no-get=false: If set, disable GET operations
   -no-put=false: If set, disable PUT operations
   -pid="": Path to write pid file
+  -timeout=15: Timeout on requests to internal Keep services (default 15 seconds)
 
@@ -52,7 +56,7 @@ The Keepproxy server needs a token to talk to the API server. On the API server, use the following command to create the token: -
~/arvados/services/api/script$ RAILS_ENV=production bundle exec ./get_anonymous_user_token.rb
+
/var/www/arvados-api/current/script$ RAILS_ENV=production bundle exec ./get_anonymous_user_token.rb
 hoShoomoo2bai3Ju1xahg6aeng1siquuaZ1yae2gi2Uhaeng2r
 
@@ -85,8 +89,8 @@ server { proxy_set_header X-Real-IP $remote_addr; ssl on; - ssl_certificate /etc/nginx/keep.example.com-ssl.crt; - ssl_certificate_key /etc/nginx/keep.example.com-ssl.key; + ssl_certificate /etc/nginx/keep.uuid_prefix.your.domain-ssl.crt; + ssl_certificate_key /etc/nginx/keep.uuid_prefix.your.domain-ssl.key; # Clients need to be able to upload blocks of data up to 64MiB in size. client_max_body_size 64m; @@ -104,11 +108,11 @@ h3. Tell the API server about the Keepproxy server The API server needs to be informed about the presence of your Keepproxy server. Please execute the following commands on your shell server. -
~$ prefix=`arv --format=uuid user current | cut -d- -f1`
-~$ echo "Site prefix is '$prefix'"
+
~$ uuid_prefix=`arv --format=uuid user current | cut -d- -f1`
+~$ echo "Site prefix is '$uuid_prefix'"
 ~$ read -rd $'\000' keepservice <<EOF; arv keep_service create --keep-service "$keepservice"
 {
- "service_host":"keep.$prefix.your.domain",
+ "service_host":"keep.$uuid_prefix.your.domain",
  "service_port":443,
  "service_ssl_flag":true,
  "service_type":"proxy"