1 ##########################################################
2 # Copyright (C) The Arvados Authors. All rights reserved.
4 # SPDX-License-Identifier: CC-BY-SA-3.0
6 # These are the basic parameters to configure the installation
8 # The Arvados cluster ID, needs to be 5 lowercase alphanumeric characters.
9 CLUSTER="cluster_fixme_or_this_wont_work"
11 # The domain name you want to give to your cluster's hosts
12 # the end result hostnames will be $SERVICE.$CLUSTER.$DOMAIN
13 DOMAIN="domain_fixme_or_this_wont_work"
15 # For multi-node installs, the ssh log in for each node
16 # must be root or able to sudo
19 # The mapping of nodes to roles
20 # installer.sh will log in to each of these nodes and then provision
21 # it for the specified roles.
23 [controller.${CLUSTER}.${DOMAIN}]=api,controller,websocket,dispatcher,keepbalance
24 [keep0.${CLUSTER}.${DOMAIN}]=keepstore
25 [keep1.${CLUSTER}.${DOMAIN}]=keepstore
26 [keep.${CLUSTER}.${DOMAIN}]=keepproxy,keepweb
27 [workbench.${CLUSTER}.${DOMAIN}]=workbench,workbench2,webshell
28 [shell.${CLUSTER}.${DOMAIN}]=shell
31 # Host SSL port where you want to point your browser to access Arvados
32 # Defaults to 443 for regular runs, and to 8443 when called in Vagrant.
33 # You can point it to another port if desired
34 # In Vagrant, make sure it matches what you set in the Vagrantfile (8443)
35 CONTROLLER_EXT_SSL_PORT=443
37 # Both for collections and downloads
38 KEEPWEB_EXT_SSL_PORT=443
39 WEBSHELL_EXT_SSL_PORT=443
40 WEBSOCKET_EXT_SSL_PORT=443
41 WORKBENCH1_EXT_SSL_PORT=443
42 WORKBENCH2_EXT_SSL_PORT=443
44 # Internal IPs for the configuration
45 CLUSTER_INT_CIDR=10.0.0.0/16
47 # Note the IPs in this example are shared between roles, as suggested in
48 # https://doc.arvados.org/main/install/salt-multi-host.html
49 CONTROLLER_INT_IP=10.0.0.1
50 WEBSOCKET_INT_IP=10.0.0.1
52 # Both for collections and downloads
53 KEEPWEB_INT_IP=10.0.0.2
54 KEEPSTORE0_INT_IP=10.0.0.3
55 KEEPSTORE1_INT_IP=10.0.0.4
56 WORKBENCH1_INT_IP=10.0.0.5
57 WORKBENCH2_INT_IP=10.0.0.5
58 WEBSHELL_INT_IP=10.0.0.5
59 DATABASE_INT_IP=10.0.0.6
64 # If not specified, the initial user email will be composed as
65 # INITIAL_USER@CLUSTER.DOMAIN
66 INITIAL_USER_EMAIL="admin@cluster_fixme_or_this_wont_work.domain_fixme_or_this_wont_work"
67 INITIAL_USER_PASSWORD="password"
69 # YOU SHOULD CHANGE THESE TO SOME RANDOM STRINGS
70 BLOB_SIGNING_KEY=blobsigningkeymushaveatleast32characters
71 MANAGEMENT_TOKEN=managementtokenmushaveatleast32characters
72 SYSTEM_ROOT_TOKEN=systemroottokenmushaveatleast32characters
73 ANONYMOUS_USER_TOKEN=anonymoususertokenmushaveatleast32characters
74 WORKBENCH_SECRET_KEY=workbenchsecretkeymushaveatleast32characters
75 DATABASE_PASSWORD=please_set_this_to_some_secure_value
78 # Arvados requires SSL certificates to work correctly. This installer supports these options:
79 # * self-signed: let the installer create self-signed certificate(s)
80 # * bring-your-own: supply your own certificate(s) in the `certs` directory
81 # * lets-encrypt: automatically obtain and install SSL certificates for your hostname(s)
83 # See https://doc.arvados.org/intall/salt-multi-host.html for more information.
84 SSL_MODE="lets-encrypt"
85 USE_LETSENCRYPT_ROUTE53="yes"
86 # For collections, we need to obtain a wildcard certificate for
87 # '*.collections.<cluster>.<domain>'. This is only possible through a DNS-01 challenge.
88 # For that reason, you'll need to provide AWS credentials with permissions to manage
89 # RRs in the route53 zone for the cluster.
90 # WARNING!: If AWS credentials files already exist in the hosts, they won't be replaced.
91 LE_AWS_REGION="us-east-1"
92 LE_AWS_ACCESS_KEY_ID="AKIABCDEFGHIJKLMNOPQ"
93 LE_AWS_SECRET_ACCESS_KEY="thisistherandomstringthatisyoursecretkey"
95 # If you going to provide your own certificates for Arvados, the provision script can
96 # help you deploy them. In order to do that, you need to set `SSL_MODE=bring-your-own` above,
97 # and copy the required certificates under the directory specified in the next line.
98 # The certs will be copied from this directory by the provision script.
99 # Please set it to the FULL PATH to the certs dir if you're going to use a different dir
100 # Default is "${SCRIPT_DIR}/certs", where the variable "SCRIPT_DIR" has the path to the
101 # directory where the "provision.sh" script was copied in the destination host.
102 # CUSTOM_CERTS_DIR="${SCRIPT_DIR}/local_config_dir/certs"
103 # The script expects cert/key files with these basenames (matching the role except for
104 # keepweb, which is split in both download/collections):
110 # "download" # Part of keepweb
111 # "collections" # Part of keepweb
112 # "keepproxy" # Keepproxy
113 # Ie., 'keep', the script will lookup for
114 # ${CUSTOM_CERTS_DIR}/keepproxy.crt
115 # ${CUSTOM_CERTS_DIR}/keepproxy.key
117 # The directory to check for the config files (pillars, states) you want to use.
118 # There are a few examples under 'config_examples'.
119 # CONFIG_DIR="local_config_dir"
120 # Extra states to apply. If you use your own subdir, change this value accordingly
121 # EXTRA_STATES_DIR="${CONFIG_DIR}/states"
123 # These are ARVADOS-related settings.
124 # Which release of Arvados repo you want to use
126 # Which version of Arvados you want to install. Defaults to latest stable
129 # This is an arvados-formula setting.
130 # If branch is set, the script will switch to it before running salt
131 # Usually not needed, only used for testing
134 ##########################################################
135 # Usually there's no need to modify things below this line
138 # ARVADOS_TAG="2.2.0"
139 # POSTGRES_TAG="v0.44.0"
141 # DOCKER_TAG="v2.4.2"
142 # LOCALE_TAG="v0.3.4"
143 # LETSENCRYPT_TAG="v2.1.0"