X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/85e4b825947790d9cde66cb8c390dc2e216dac9a..2f5d03d2f49db23ee6c22285357cafad581f1dcb:/tools/salt-install/local.params.example.single_host_single_hostname?ds=sidebyside diff --git a/tools/salt-install/local.params.example.single_host_single_hostname b/tools/salt-install/local.params.example.single_host_single_hostname index d09cdb2ef0..6a7460de8e 100644 --- a/tools/salt-install/local.params.example.single_host_single_hostname +++ b/tools/salt-install/local.params.example.single_host_single_hostname @@ -15,11 +15,10 @@ DOMAIN="domain_fixme_or_this_wont_work" # to access all the instances. Not used in the other examples. # When using virtualization (ie AWS), this should be # the EXTERNAL/PUBLIC hostname for the instance. -# If empty, ${CLUSTER}.${DOMAIN} will be used -HOSTNAME_EXT="" +HOSTNAME_EXT="hostname_ext_fixme_or_this_wont_work" # The internal hostname for the host. In the example files, only used in the # single_host/single_hostname example -HOSTNAME_INT="127.0.1.1" +IP_INT="127.0.1.1" # 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 @@ -49,17 +48,40 @@ WORKBENCH_SECRET_KEY=workbenchsecretkeymushaveatleast32characters DATABASE_PASSWORD=please_set_this_to_some_secure_value # SSL CERTIFICATES -# Arvados REQUIRES valid SSL to work correctly. Otherwise, some components will -# fail to communicate and can silently drop traffic. Set USE_LETSENCRYPT="yes" -# to use the Let's Encrypt salt formula -# (https://github.com/saltstack-formulas/letsencrypt-formula) to automatically -# obtain and install SSL certificates for your hostname(s). +# 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 # -# Alternatively, set this variable to "no" and provide and upload your own -# certificates to the instances and modify the 'nginx_*' salt pillars -# accordingly -USE_LETSENCRYPT="no" +# See https://doc.arvados.org/intall/salt-single-host.html#certificates for more information. +SSL_MODE="self-signed" +# If you want to use letsencrypt, set SSL_MODE="lets-encrypt" +# A single certificate for the external hostname of the host will be retrieved, using +# "standalone" mode of LE. + +# 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 `SSL_MODE=bring-your-own` 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" # Keepproxy +# Ie., 'keep', the script will lookup for +# ${CUSTOM_CERTS_DIR}/keepproxy.crt +# ${CUSTOM_CERTS_DIR}/keepproxy.key + +# The certs will be copied from this directory by the provision script. # 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" @@ -83,7 +105,7 @@ RELEASE="production" # Formulas versions # ARVADOS_TAG="2.2.0" # POSTGRES_TAG="v0.43.0" -# NGINX_TAG="temp-fix-missing-statements-in-pillar" +# NGINX_TAG="v2.8.0" # DOCKER_TAG="v2.0.7" # LOCALE_TAG="v0.3.4" # LETSENCRYPT_TAG="v2.1.0"