X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/a6c7c8db01d37534622763dd385019e9dad17181..1d5727fcdd6e524898d7507417456b9fedcb79dd:/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 b110a8bd11..db24953fcc 100644 --- a/doc/install/install-keepproxy.html.textile.liquid +++ b/doc/install/install-keepproxy.html.textile.liquid @@ -3,6 +3,11 @@ layout: default navsection: installguide title: Install Keepproxy server ... +{% comment %} +Copyright (C) The Arvados Authors. All rights reserved. + +SPDX-License-Identifier: CC-BY-SA-3.0 +{% endcomment %} 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. @@ -74,22 +79,24 @@ upstream keepproxy { } server { - listen [your public IP address]:443 ssl; - server_name keep.uuid_prefix.your.domain; + listen [your public IP address]:443 ssl; + server_name keep.uuid_prefix.your.domain; - proxy_connect_timeout 90s; - proxy_read_timeout 300s; - proxy_set_header X-Real-IP $remote_addr; + proxy_connect_timeout 90s; + proxy_read_timeout 300s; + proxy_set_header X-Real-IP $remote_addr; + proxy_http_version 1.1; + proxy_request_buffering off; - ssl on; - ssl_certificate /etc/nginx/keep.uuid_prefix.your.domain-ssl.crt; - ssl_certificate_key /etc/nginx/keep.uuid_prefix.your.domain-ssl.key; + ssl on; + 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; + client_max_body_size 64m; location / { - proxy_pass http://keepproxy; + proxy_pass http://keepproxy; } } @@ -98,7 +105,18 @@ Note: if the Web uploader is failing to upload data and there are no logs from k 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. +The API server needs to be informed about the presence of your Keepproxy server. + +First, if you don't already have an admin token, create a superuser token. + +{% include 'create_superuser_token' %} + +Configure your environment to run @arv@ using the output of create_superuser_token.rb: + +
+export ARVADOS_API_HOST=zzzzz.example.com
+export ARVADOS_API_TOKEN=zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
+
~$ uuid_prefix=`arv --format=uuid user current | cut -d- -f1`
@@ -112,3 +130,13 @@ The API server needs to be informed about the presence of your Keepproxy server.
 }
 EOF
 
+ +h3. Testing keepproxy + +Log into a host that is on an external network from your private Arvados network. The host should be able to contact your keepproxy server (eg keep.$uuid_prefix.arvadosapi.com), but not your keepstore servers (eg keep[0-9].$uuid_prefix.arvadosapi.com). + +Install the "Python SDK":{{site.baseurl}}/sdk/python/sdk-python.html + +@ARVADOS_API_HOST@ and @ARVADOS_API_TOKEN@ must be set in the environment. + +You should now be able to use @arv-put@ to upload collections and @arv-get@ to fetch collections, for an example see "Testing keep.":install-keepstore.html#testing on the keepstore install page.