X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/908d141b6564f90c2ed9e0e6c9d7a4397a528c9f..98969e546c909ac2ee4256934b5339080598d252:/tools/salt-install/local.params.example.multiple_hosts diff --git a/tools/salt-install/local.params.example.multiple_hosts b/tools/salt-install/local.params.example.multiple_hosts index ef682c3193..72f910b735 100644 --- a/tools/salt-install/local.params.example.multiple_hosts +++ b/tools/salt-install/local.params.example.multiple_hosts @@ -16,47 +16,7 @@ DOMAIN="domain_fixme_or_this_wont_work" # must be root or able to sudo DEPLOY_USER=admin -# The mapping of nodes to roles -# installer.sh will log in to each of these nodes and then provision -# it for the specified roles. -NODES=( - [controller.${CLUSTER}.${DOMAIN}]=database,api,controller,websocket,dispatcher,keepbalance - [workbench.${CLUSTER}.${DOMAIN}]=monitoring,workbench,workbench2,webshell,keepproxy,keepweb - [keep0.${CLUSTER}.${DOMAIN}]=keepstore - [shell.${CLUSTER}.${DOMAIN}]=shell -) - -# Host SSL port where you want to point your browser to access Arvados -# Defaults to 443 for regular runs, and to 8443 when called in Vagrant. -# You can point it to another port if desired -# In Vagrant, make sure it matches what you set in the Vagrantfile (8443) -CONTROLLER_EXT_SSL_PORT=443 -KEEP_EXT_SSL_PORT=443 -# Both for collections and downloads -KEEPWEB_EXT_SSL_PORT=443 -WEBSHELL_EXT_SSL_PORT=443 -WEBSOCKET_EXT_SSL_PORT=443 -WORKBENCH1_EXT_SSL_PORT=443 -WORKBENCH2_EXT_SSL_PORT=443 - -# Internal IPs for the configuration -CLUSTER_INT_CIDR=10.1.0.0/16 - -# Note the IPs in this example are shared between roles, as suggested in -# https://doc.arvados.org/main/install/salt-multi-host.html -CONTROLLER_INT_IP=10.1.1.11 -WEBSOCKET_INT_IP=10.1.1.11 -KEEP_INT_IP=10.1.1.15 -# Both for collections and downloads -KEEPWEB_INT_IP=10.1.1.15 -KEEPSTORE0_INT_IP=10.1.2.13 -WORKBENCH1_INT_IP=10.1.1.15 -WORKBENCH2_INT_IP=10.1.1.15 -WEBSHELL_INT_IP=10.1.1.15 -DATABASE_INT_IP=10.1.1.11 -SHELL_INT_IP=10.1.2.17 - -INITIAL_USER="admin" +INITIAL_USER=admin # If not specified, the initial user email will be composed as # INITIAL_USER@CLUSTER.DOMAIN @@ -113,6 +73,8 @@ LE_AWS_SECRET_ACCESS_KEY="thisistherandomstringthatisyoursecretkey" # "download" # Part of keepweb # "collections" # Part of keepweb # "keepproxy" # Keepproxy +# "prometheus" +# "grafana" # Ie., 'keep', the script will lookup for # ${CUSTOM_CERTS_DIR}/keepproxy.crt # ${CUSTOM_CERTS_DIR}/keepproxy.key @@ -130,6 +92,46 @@ MONITORING_EMAIL=${INITIAL_USER_EMAIL} # Sets the directory for Grafana dashboards # GRAFANA_DASHBOARDS_DIR="${SCRIPT_DIR}/local_config_dir/dashboards" +# The mapping of nodes to roles +# installer.sh will log in to each of these nodes and then provision +# it for the specified roles. +NODES=( + [controller.${CLUSTER}.${DOMAIN}]=database,api,controller,websocket,dispatcher,keepbalance + [workbench.${CLUSTER}.${DOMAIN}]=monitoring,workbench,workbench2,webshell,keepproxy,keepweb + [keep0.${CLUSTER}.${DOMAIN}]=keepstore + [shell.${CLUSTER}.${DOMAIN}]=shell +) + +# Host SSL port where you want to point your browser to access Arvados +# Defaults to 443 for regular runs, and to 8443 when called in Vagrant. +# You can point it to another port if desired +# In Vagrant, make sure it matches what you set in the Vagrantfile (8443) +CONTROLLER_EXT_SSL_PORT=443 +KEEP_EXT_SSL_PORT=443 +# Both for collections and downloads +KEEPWEB_EXT_SSL_PORT=443 +WEBSHELL_EXT_SSL_PORT=443 +WEBSOCKET_EXT_SSL_PORT=443 +WORKBENCH1_EXT_SSL_PORT=443 +WORKBENCH2_EXT_SSL_PORT=443 + +# Internal IPs for the configuration +CLUSTER_INT_CIDR=10.1.0.0/16 + +# Note the IPs in this example are shared between roles, as suggested in +# https://doc.arvados.org/main/install/salt-multi-host.html +CONTROLLER_INT_IP=10.1.1.11 +WEBSOCKET_INT_IP=10.1.1.11 +KEEP_INT_IP=10.1.1.15 +# Both for collections and downloads +KEEPWEB_INT_IP=10.1.1.15 +KEEPSTORE0_INT_IP=10.1.2.13 +WORKBENCH1_INT_IP=10.1.1.15 +WORKBENCH2_INT_IP=10.1.1.15 +WEBSHELL_INT_IP=10.1.1.15 +DATABASE_INT_IP=10.1.1.11 +SHELL_INT_IP=10.1.2.17 + # The directory to check for the config files (pillars, states) you want to use. # There are a few examples under 'config_examples'. # CONFIG_DIR="local_config_dir"