X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/e3e255e8aca055a51b9c6722719e712cdf6e650e..9539317a22d8ea16f94b0e086507ab595d758216:/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 827d65db28..ab36035a84 100644 --- a/doc/install/salt-multi-host.html.textile.liquid +++ b/doc/install/salt-multi-host.html.textile.liquid @@ -9,6 +9,7 @@ Copyright (C) The Arvados Authors. All rights reserved. SPDX-License-Identifier: CC-BY-SA-3.0 {% endcomment %} +# "Introduction":#introduction # "Hosts preparation":#hosts_preparation ## "Hosts setup using terraform (experimental)":#hosts_setup_using_terraform ## "Create a compute image":#create_a_compute_image @@ -21,6 +22,18 @@ SPDX-License-Identifier: CC-BY-SA-3.0 # "Initial user and login":#initial_user # "Test the installed cluster running a simple workflow":#test_install + + +h2(#introduction). Introduction + +Arvados components can be installed in a distributed infrastructure, whether it is an "on-prem" with physical or virtual hosts, or a cloud environment. + +As infrastructures vary a great deal from site to site, these instructions should be considered more as 'guidelines' than fixed steps to follow. + +We provide an "installer script":salt.html that can help you deploy the different Arvados components. At the time of writing, the provided examples are suitable to install Arvados on AWS. + + + h2(#hosts_preparation). Hosts preparation In order to run Arvados on a multi-host installation, there are a few requirements that your infrastructure has to fulfill. @@ -39,6 +52,7 @@ We suggest distributing the Arvados components in the following way, creating at # WORKBENCH node: ## arvados workbench ## arvados workbench2 +## arvados webshell # KEEPPROXY node: ## arvados keepproxy ## arvados keepweb @@ -49,22 +63,31 @@ We suggest distributing the Arvados components in the following way, creating at Note that these hosts can be virtual machines in your infrastructure and they don't need to be physical machines. -h3(#hosts_setup_using_terraform). Hosts setup using terraform (experimental) +Again, if your infrastructure differs from the setup proposed above (ie, using RDS or an existing DB server), remember that you will need to edit the configuration files for the scripts so they work with your infrastructure. + + +h3(#hosts_setup_using_terraform). Hosts setup using terraform (AWS, experimental) + +We added a few "terraform":https://terraform.io/ scripts (https://github.com/arvados/arvados/tree/main/tools/terraform) to let you create these instances easier in an AWS account. Check "the Arvados terraform documentation":/doc/install/terraform.html for more details. + + -We added a few "terraform":https://terraform.io/ scripts (https://github.com/arvados/arvados/tree/master/tools/terraform) to let you create these instances easier. -Check "the Arvados terraform documentation":/doc/install/terraform.html for more details. h2(#multi_host). Multi host install using the provision.sh script -This is a package-based installation method. The Salt scripts are available from the "tools/salt-install":https://github.com/arvados/arvados/tree/master/tools/salt-install directory in the Arvados git repository. +{% 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. -This procedure will install all the main Arvados components to get you up and running in a multi host environment. +This procedure will install all the main Arvados components to get you up and running in a multi-host environment. -We suggest you to use the @provision.sh@ script to deploy Arvados, which is implemented with the @arvados-formula@ in a Saltstack master-less setup. After setting up a few variables in a config file (next step), you'll be ready to run it and get Arvados deployed. +The @provision.sh@ script will help you deploy Arvados by preparing your environment to be able to run the installer, then running it. The actual installer is located at "arvados-formula":https://git.arvados.org/arvados-formula.git/tree/refs/heads/{{ branchname }} and will be cloned during the running of the @provision.sh@ script. The installer is built using "Saltstack":https://saltproject.io/ and @provision.sh@ performs the install using master-less mode. + +After setting up a few variables in a config file (next step), you'll be ready to run it and get Arvados deployed. h3(#create_a_compute_image). Create a compute image -In a multi-host installation, containers are dispatched in docker daemons running in the compute instances, which need some special setup. We provide a "compute image builder script":https://github.com/arvados/arvados/tree/master/tools/compute-images that you can use to build a template image following "these instructions":https://doc.arvados.org/main/install/crunch2-cloud/install-compute-node.html . Once you have that image created, you can use the image reference in the Arvados configuration in the next steps. +In a multi-host installation, containers are dispatched in docker daemons running in the compute instances, which need some special setup. We provide a "compute image builder script":https://github.com/arvados/arvados/tree/main/tools/compute-images that you can use to build a template image following "these instructions":https://doc.arvados.org/main/install/crunch2-cloud/install-compute-node.html . Once you have that image created, you can use the image ID in the Arvados configuration in the next steps. h2(#choose_configuration). Choose the desired configuration @@ -83,7 +106,9 @@ 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, Workbench) so it will need the hostnames to be reachable from the Internet. If this cluster will not be the case, please set the variable USE_LETSENCRYPT=no. +The multi_host example includes Let's Encrypt salt code to automatically request and install the certificates for the public-facing hosts (API/controller, Workbench, Keepproxy/Keepweb) using AWS' Route53. + +{% include 'install_custom_certificates' %} h3(#further_customization). Further customization of the installation (modifying the salt pillars and states) @@ -145,7 +170,7 @@ ssh user@host sudo ./provision.sh --config local.params --roles keepstore #. Workbench
scp -r provision.sh local* user@host:
-ssh user@host sudo ./provision.sh --config local.params --roles workbench,workbench2
+ssh user@host sudo ./provision.sh --config local.params --roles workbench,workbench2,webshell
 
@@ -163,7 +188,7 @@ ssh user@host sudo ./provision.sh --config local.params --roles shell -h2(#initial_user). Initial user and login +h2(#initial_user). Initial user and login At this point you should be able to log into the Arvados cluster. The initial URL will be: