X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/4f5540fdd686522e73f2c4416bd11d1000f99004..6a1a9849137351b7ddbfe52011174ea3182f4b30:/tools/salt-install/local.params.example.single_host_multiple_hostnames diff --git a/tools/salt-install/local.params.example.single_host_multiple_hostnames b/tools/salt-install/local.params.example.single_host_multiple_hostnames index 11ebc119f7..8dece2b76f 100644 --- a/tools/salt-install/local.params.example.single_host_multiple_hostnames +++ b/tools/salt-install/local.params.example.single_host_multiple_hostnames @@ -5,74 +5,87 @@ # These are the basic parameters to configure the installation -# The FIVE ALPHANUMERIC CHARACTERS name you want to give your cluster +# The Arvados cluster ID, needs to be 5 lowercase alphanumeric characters. CLUSTER="cluster_fixme_or_this_wont_work" # The domainname you want tou give to your cluster's hosts DOMAIN="domain_fixme_or_this_wont_work" -# 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) +# For multi-node installs, the ssh log in for each node +# must be root or able to sudo +DEPLOY_USER=admin + +INITIAL_USER=admin + +# If not specified, the initial user email will be composed as +# INITIAL_USER@CLUSTER.DOMAIN +INITIAL_USER_EMAIL="admin@cluster_fixme_or_this_wont_work.domain_fixme_or_this_wont_work" + +# SSL CERTIFICATES +# Arvados requires SSL certificates to work correctly. This installer supports these options: +# * self-signed: let the installer create self-signed certificate(s) +# * bring-your-own: supply your own certificate(s) in the `certs` directory +# * lets-encrypt: automatically obtain and install SSL certificates for your hostname(s) +# +# See https://doc.arvados.org/intall/salt-single-host.html#certificates for more information. +SSL_MODE="self-signed" + +# CUSTOM_CERTS_DIR is only used when SSL_MODE is set to "bring-your-own". +# See https://doc.arvados.org/intall/salt-single-host.html#bring-your-own for more information. +# CUSTOM_CERTS_DIR="${SCRIPT_DIR}/local_config_dir/certs" + +# Set the following to "yes" if the key files are encrypted and optionally set +# a custom AWS secret name for each node to retrieve the password. +SSL_KEY_ENCRYPTED="no" +SSL_KEY_AWS_SECRET_NAME="${CLUSTER}-arvados-ssl-privkey-password" + +# Customize Prometheus & Grafana web UI access credentials +MONITORING_USERNAME=${INITIAL_USER} +MONITORING_PASSWORD=${INITIAL_USER_PASSWORD} +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=( + [localhost]='' +) + +# External ports used by the Arvados services CONTROLLER_EXT_SSL_PORT=443 KEEP_EXT_SSL_PORT=25101 -# Both for collections and downloads KEEPWEB_EXT_SSL_PORT=9002 WEBSHELL_EXT_SSL_PORT=4202 WEBSOCKET_EXT_SSL_PORT=8002 WORKBENCH1_EXT_SSL_PORT=443 WORKBENCH2_EXT_SSL_PORT=3001 -INITIAL_USER="admin" - -# If not specified, the initial user email will be composed as -# INITIAL_USER@CLUSTER.DOMAIN -INITIAL_USER_EMAIL="admin@cluster_fixme_or_this_wont_work.domain_fixme_or_this_wont_work" -INITIAL_USER_PASSWORD="password" - -# YOU SHOULD CHANGE THESE TO SOME RANDOM STRINGS -BLOB_SIGNING_KEY=blobsigningkeymushaveatleast32characters -MANAGEMENT_TOKEN=managementtokenmushaveatleast32characters -SYSTEM_ROOT_TOKEN=systemroottokenmushaveatleast32characters -ANONYMOUS_USER_TOKEN=anonymoususertokenmushaveatleast32characters -WORKBENCH_SECRET_KEY=workbenchsecretkeymushaveatleast32characters -DATABASE_PASSWORD=please_set_this_to_some_secure_value +CLUSTER_INT_CIDR="" +CONTROLLER_INT_IP="" +DATABASE_INT_IP="" +WORKBENCH1_INT_IP="" +DISPATCHER_INT_IP="" +KEEPBALANCE_INT_IP="" +WEBSOCKET_INT_IP="" +KEEPWEB_INT_IP="" +WORKBENCH2_INT_IP="" +WEBSHELL_INT_IP="" +KEEP_INT_IP="" +KEEPSTORE0_INT_IP="" +SHELL_INT_IP="" -# SSL CERTIFICATES -# Arvados REQUIRES valid SSL to work correctly. Otherwise, some components will fail -# to communicate and can silently drop traffic. You can try to use the Letsencrypt -# salt formula (https://github.com/saltstack-formulas/letsencrypt-formula) to try to -# automatically obtain and install SSL certificates for your instances or set this -# variable to "no", provide and upload your own certificates to the instances and -# modify the 'nginx_*' salt pillars accordingly (see CUSTOM_CERTS_DIR below) -USE_LETSENCRYPT="no" - -# If you going to provide your own certificates for Arvados, the provision script can -# help you deploy them. In order to do that, you need to set `USE_LETSENCRYPT=no` above, -# and copy the required certificates under the directory specified in the next line. -# The certs will be copied from this directory by the provision script. -# Please set it to the FULL PATH to the certs dir if you're going to use a different dir -# Default is "${SCRIPT_DIR}/certs", where the variable "SCRIPT_DIR" has the path to the -# directory where the "provision.sh" script was copied in the destination host. -# CUSTOM_CERTS_DIR="${SCRIPT_DIR}/certs" -# The script expects cert/key files with these basenames (matching the role except for -# keepweb, which is split in both download/collections): -# "controller" -# "websocket" -# "workbench" -# "workbench2" -# "webshell" -# "download" # Part of keepweb -# "collections" # Part of keepweb -# "keepproxy" -# Ie., 'keepproxy', the script will lookup for -# ${CUSTOM_CERTS_DIR}/keepproxy.crt -# ${CUSTOM_CERTS_DIR}/keepproxy.key +DATABASE_NAME="${CLUSTER}_arvados" +DATABASE_USER="${CLUSTER}_arvados" +# Set these if using an external PostgreSQL service. +#DATABASE_EXTERNAL_SERVICE_HOST_OR_IP= +#DATABASE_POSTGRESQL_VERSION= # 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" + # Extra states to apply. If you use your own subdir, change this value accordingly # EXTRA_STATES_DIR="${CONFIG_DIR}/states" @@ -92,8 +105,10 @@ RELEASE="production" # Formulas versions # ARVADOS_TAG="2.2.0" -# POSTGRES_TAG="v0.41.6" -# NGINX_TAG="temp-fix-missing-statements-in-pillar" -# DOCKER_TAG="v2.0.7" +# POSTGRES_TAG="v0.44.0" +# NGINX_TAG="v2.8.1" +# DOCKER_TAG="v2.4.2" # LOCALE_TAG="v0.3.4" # LETSENCRYPT_TAG="v2.1.0" +# PROMETHEUS_TAG="v5.6.5" +# GRAFANA_TAG="v3.1.3"