X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/35d15b6e1fcd793d8e279588dea878101c3ab055..f54cc984969657be50c093b917feb49a19d78c22:/doc/install/salt-multi-host.html.textile.liquid diff --git a/doc/install/salt-multi-host.html.textile.liquid b/doc/install/salt-multi-host.html.textile.liquid index 2e4f49b019..f3afcd5031 100644 --- a/doc/install/salt-multi-host.html.textile.liquid +++ b/doc/install/salt-multi-host.html.textile.liquid @@ -75,11 +75,7 @@ We added a few "terraform":https://terraform.io/ scripts (https://github.com/arv h2(#multi_host). Multi host install using the provision.sh script -{% if site.current_version %} -{% assign branchname = site.current_version | slice: 1, 5 | append: '-dev' %} -{% else %} -{% assign branchname = 'main' %} -{% endif %} +{% include 'branchname' %} This is a package-based installation method. Start with the @provision.sh@ script which is available by cloning the @{{ branchname }}@ branch from "https://git.arvados.org/arvados.git":https://git.arvados.org/arvados.git . The @provision.sh@ script and its supporting files can be found in the "arvados/tools/salt-install":https://git.arvados.org/arvados.git/tree/refs/heads/{{ branchname }}:/tools/salt-install directory in the Arvados git repository. @@ -110,7 +106,28 @@ cp -r config_examples/multi_host/aws local_config_dir Edit the variables in the local.params file. Pay attention to the *_INT_IP, *_TOKEN and *KEY variables. Those variables will be used to do a search and replace on the pillars/* in place of any matching __VARIABLE__. -The multi_host include LetsEncrypt salt code to automatically request and install the certificates for the public-facing hosts (API/controller, Workbench, Keepproxy/Keepweb) using AWS' Route53. If you will provide custom certificates, please set the variable USE_LETSENCRYPT=no. +The multi_host include LetsEncrypt salt code to automatically request and install the certificates for the public-facing hosts (API/controller, Workbench, Keepproxy/Keepweb) using AWS' Route53. + +If you plan to use custom certificates, please set the variable USE_LETSENCRYPT=no and copy your certificates to the directory specified with the variable @CUSTOM_CERTS_DIR@ (usually "./certs") in the remote directory where you copied the @provision.sh@ script. From this dir, the provision script will install the certificates required for the role you're installing. + +The script expects cert/key files with these basenames (matching the role except for keepweb, which is split in both downoad / collections): + +* "controller" +* "websocket" +* "workbench" +* "workbench2" +* "webshell" +* "download" # Part of keepweb +* "collections" # Part of keepweb +* "keepproxy" + +Ie., for 'keepproxy', the script will lookup for + + +
${CUSTOM_CERTS_DIR}/keepproxy.crt
+${CUSTOM_CERTS_DIR}/keepproxy.key
+
+
h3(#further_customization). Further customization of the installation (modifying the salt pillars and states)