1 # Copyright (C) The Arvados Authors. All rights reserved.
3 # SPDX-License-Identifier: AGPL-3.0
5 # Do not use this file for site configuration. Create
6 # /etc/arvados/config.yml instead.
8 # The order of precedence (highest to lowest):
9 # 1. Legacy component-specific config files (deprecated)
10 # 2. /etc/arvados/config.yml
11 # 3. config.default.yml
15 # Token used internally by Arvados components to authenticate to
16 # one another. Use a string of at least 50 random alphanumerics.
19 # Token to be included in all healthcheck requests. Disabled by default.
20 # Server expects request header of the format "Authorization: Bearer xxx"
25 # In each of the service sections below, the keys under
26 # InternalURLs are the endpoints where the service should be
27 # listening, and reachable from other hosts in the
31 # "http://host1.example:12345": {}
32 # "http://host2.example:12345": {}
35 InternalURLs: {SAMPLE: {}}
38 InternalURLs: {SAMPLE: {}}
41 InternalURLs: {SAMPLE: {}}
44 InternalURLs: {SAMPLE: {}}
47 InternalURLs: {SAMPLE: {}}
50 InternalURLs: {SAMPLE: {}}
53 InternalURLs: {SAMPLE: {}}
56 InternalURLs: {SAMPLE: {}}
59 InternalURLs: {SAMPLE: {}}
62 InternalURLs: {SAMPLE: {}}
63 # Base URL for Workbench inline preview. If blank, use
64 # WebDAVDownload instead, and disable inline preview.
65 # If both are empty, downloading collections from workbench
68 # It is important to properly configure the download service
69 # to migitate cross-site-scripting (XSS) attacks. A HTML page
70 # can be stored in collection. If an attacker causes a victim
71 # to visit that page through Workbench, it will be rendered by
72 # the browser. If all collections are served at the same
73 # domain, the browser will consider collections as coming from
74 # the same origin and having access to the same browsing data,
75 # enabling malicious Javascript on that page to access Arvados
76 # on behalf of the victim.
78 # This is mitigating by having separate domains for each
79 # collection, or limiting preview to circumstances where the
80 # collection is not accessed with the user's regular
83 # Serve preview links using uuid or pdh in subdomain
84 # (requires wildcard DNS and TLS certificate)
85 # https://*.collections.uuid_prefix.arvadosapi.com
87 # Serve preview links using uuid or pdh in main domain
88 # (requires wildcard DNS and TLS certificate)
89 # https://*--collections.uuid_prefix.arvadosapi.com
91 # Serve preview links by setting uuid or pdh in the path.
92 # This configuration only allows previews of public data or
93 # collection-sharing links, because these use the anonymous
94 # user token or the token is already embedded in the URL.
95 # Other data must be handled as downloads via WebDAVDownload:
96 # https://collections.uuid_prefix.arvadosapi.com
101 InternalURLs: {SAMPLE: {}}
102 # Base URL for download links. If blank, serve links to WebDAV
103 # with disposition=attachment query param. Unlike preview links,
104 # browsers do not render attachments, so there is no risk of XSS.
106 # If WebDAVDownload is blank, and WebDAV uses a
107 # single-origin form, then Workbench will show an error page
109 # Serve download links by setting uuid or pdh in the path:
110 # https://download.uuid_prefix.arvadosapi.com
117 # Rendezvous is normally empty/omitted. When changing the
118 # URL of a Keepstore service, Rendezvous should be set to
119 # the old URL (with trailing slash omitted) to preserve
120 # rendezvous ordering.
124 InternalURLs: {SAMPLE: {}}
127 InternalURLs: {SAMPLE: {}}
128 # ShellInABox service endpoint URL for a given VM. If empty, do not
129 # offer web shell logins.
131 # E.g., using a path-based proxy server to forward connections to shell hosts:
132 # https://webshell.uuid_prefix.arvadosapi.com
134 # E.g., using a name-based proxy server to forward connections to shell hosts:
135 # https://*.webshell.uuid_prefix.arvadosapi.com
138 InternalURLs: {SAMPLE: {}}
141 InternalURLs: {SAMPLE: {}}
144 InternalURLs: {SAMPLE: {}}
148 # max concurrent connections per arvados server daemon
151 # All parameters here are passed to the PG client library in a connection string;
152 # see https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS
160 # Limits for how long a client token created by regular users can be valid,
161 # and also is used as a default expiration policy when no expiration date is
163 # Default value zero means token expirations don't get clamped and no
164 # default expiration is set.
167 # Maximum size (in bytes) allowed for a single API request. This
168 # limit is published in the discovery document for use by clients.
169 # Note: You must separately configure the upstream web server or
170 # proxy to actually enforce the desired maximum request size on the
172 MaxRequestSize: 134217728
174 # Limit the number of bytes read from the database during an index
175 # request (by retrieving and returning fewer rows than would
176 # normally be returned in a single response).
177 # Note 1: This setting never reduces the number of returned rows to
178 # zero, no matter how big the first data row is.
179 # Note 2: Currently, this is only checked against a specific set of
180 # columns that tend to get large (collections.manifest_text,
181 # containers.mounts, workflows.definition). Other fields (e.g.,
182 # "properties" hashes) are not counted against this limit.
183 MaxIndexDatabaseRead: 134217728
185 # Maximum number of items to return when responding to a APIs that
186 # can return partial result sets using limit and offset parameters
187 # (e.g., *.index, groups.contents). If a request specifies a "limit"
188 # parameter higher than this value, this value is used instead.
189 MaxItemsPerResponse: 1000
191 # Maximum number of concurrent requests to accept in a single
192 # service process, or 0 for no limit.
193 MaxConcurrentRequests: 0
195 # Maximum number of 64MiB memory buffers per Keepstore server process, or
196 # 0 for no limit. When this limit is reached, up to
197 # (MaxConcurrentRequests - MaxKeepBlobBuffers) HTTP requests requiring
198 # buffers (like GET and PUT) will wait for buffer space to be released.
199 # Any HTTP requests beyond MaxConcurrentRequests will receive an
200 # immediate 503 response.
202 # MaxKeepBlobBuffers should be set such that (MaxKeepBlobBuffers * 64MiB
203 # * 1.1) fits comfortably in memory. On a host dedicated to running
204 # Keepstore, divide total memory by 88MiB to suggest a suitable value.
205 # For example, if grep MemTotal /proc/meminfo reports MemTotal: 7125440
206 # kB, compute 7125440 / (88 * 1024)=79 and set MaxKeepBlobBuffers: 79
207 MaxKeepBlobBuffers: 128
209 # API methods to disable. Disabled methods are not listed in the
210 # discovery document, and respond 404 to all requests.
211 # Example: {"jobs.create":{}, "pipeline_instances.create": {}}
214 # Interval (seconds) between asynchronous permission view updates. Any
215 # permission-updating API called with the 'async' parameter schedules a an
216 # update on the permission view in the future, if not already scheduled.
217 AsyncPermissionsUpdateInterval: 20s
219 # Maximum number of concurrent outgoing requests to make while
220 # serving a single incoming multi-cluster (federated) request.
221 MaxRequestAmplification: 4
223 # Maximum wall clock time to spend handling an incoming request.
226 # Websocket will send a periodic empty event after 'SendTimeout'
227 # if there is no other activity to maintain the connection /
228 # detect dropped connections.
231 WebsocketClientEventQueue: 64
232 WebsocketServerEventQueue: 4
234 # Timeout on requests to internal Keep services.
235 KeepServiceRequestTimeout: 15s
237 # Vocabulary file path, local to the node running the controller.
238 # This JSON file should contain the description of what's allowed
239 # as object's metadata. Its format is described at:
240 # https://doc.arvados.org/admin/metadata-vocabulary.html
244 # Config parameters to automatically setup new users. If enabled,
245 # this users will be able to self-activate. Enable this if you want
246 # to run an open instance where anyone can create an account and use
247 # the system without requiring manual approval.
249 # The params AutoSetupNewUsersWith* are meaningful only when AutoSetupNewUsers is turned on.
250 # AutoSetupUsernameBlacklist is a list of usernames to be blacklisted for auto setup.
251 AutoSetupNewUsers: false
252 AutoSetupNewUsersWithVmUUID: ""
253 AutoSetupNewUsersWithRepository: false
254 AutoSetupUsernameBlacklist:
263 # When NewUsersAreActive is set to true, new users will be active
264 # immediately. This skips the "self-activate" step which enforces
265 # user agreements. Should only be enabled for development.
266 NewUsersAreActive: false
268 # Newly activated users (whether set up by an admin or via
269 # AutoSetupNewUsers) immediately become visible to other active
272 # On a multi-tenant cluster, where the intent is for users to be
273 # invisible to one another unless they have been added to the
274 # same group(s) via Workbench admin interface, change this to
276 ActivatedUsersAreVisibleToOthers: true
278 # The e-mail address of the user you would like to become marked as an admin
279 # user on their first login.
280 AutoAdminUserWithEmail: ""
282 # If AutoAdminFirstUser is set to true, the first user to log in when no
283 # other admin users exist will automatically become an admin user.
284 AutoAdminFirstUser: false
286 # Email address to notify whenever a user creates a profile for the
288 UserProfileNotificationAddress: ""
289 AdminNotifierEmailFrom: arvados@example.com
290 EmailSubjectPrefix: "[ARVADOS] "
291 UserNotifierEmailFrom: arvados@example.com
292 UserNotifierEmailBcc: {}
293 NewUserNotificationRecipients: {}
294 NewInactiveUserNotificationRecipients: {}
296 # Set AnonymousUserToken to enable anonymous user access. Populate this
297 # field with a long random string. Then run "bundle exec
298 # ./script/get_anonymous_user_token.rb" in the directory where your API
299 # server is running to record the token in the database.
300 AnonymousUserToken: ""
302 # If a new user has an alternate email address (local@domain)
303 # with the domain given here, its local part becomes the new
304 # user's default username. Otherwise, the user's primary email
306 PreferDomainForUsername: ""
309 <% if not @user.full_name.empty? -%>
310 <%= @user.full_name %>,
315 Your Arvados account has been set up. You can log in at
317 <%= Rails.configuration.Services.Workbench1.ExternalURL %>
320 Your Arvados administrator.
323 # Time to keep audit logs, in seconds. (An audit log is a row added
324 # to the "logs" table in the PostgreSQL database each time an
325 # Arvados object is created, modified, or deleted.)
327 # Currently, websocket event notifications rely on audit logs, so
328 # this should not be set lower than 300 (5 minutes).
331 # Maximum number of log rows to delete in a single SQL transaction.
333 # If MaxDeleteBatch is 0, log entries will never be
334 # deleted by Arvados. Cleanup can be done by an external process
335 # without affecting any Arvados system processes, as long as very
336 # recent (<5 minutes old) logs are not deleted.
338 # 100000 is a reasonable batch size for most sites.
341 # Attributes to suppress in events and audit logs. Notably,
342 # specifying {"manifest_text": {}} here typically makes the database
343 # smaller and faster.
345 # Warning: Using any non-empty value here can have undesirable side
346 # effects for any client or component that relies on event logs.
347 # Use at your own risk.
348 UnloggedAttributes: {}
352 # Logging threshold: panic, fatal, error, warn, info, debug, or
356 # Logging format: json or text
359 # Maximum characters of (JSON-encoded) query parameters to include
360 # in each request log entry. When params exceed this size, they will
361 # be JSON-encoded, truncated to this size, and logged as
363 MaxRequestLogParamsSize: 2000
367 # Enable access controls for data stored in Keep. This should
368 # always be set to true on a production cluster.
371 # BlobSigningKey is a string of alphanumeric characters used to
372 # generate permission signatures for Keep locators. It must be
373 # identical to the permission key given to Keep. IMPORTANT: This
374 # is a site secret. It should be at least 50 characters.
376 # Modifying BlobSigningKey will invalidate all existing
377 # signatures, which can cause programs to fail (e.g., arv-put,
378 # arv-get, and Crunch jobs). To avoid errors, rotate keys only
379 # when no such processes are running.
382 # Enable garbage collection of unreferenced blobs in Keep.
385 # Time to leave unreferenced blobs in "trashed" state before
386 # deleting them, or 0 to skip the "trashed" state entirely and
387 # delete unreferenced blobs.
389 # If you use any Amazon S3 buckets as storage volumes, this
390 # must be at least 24h to avoid occasional data loss.
391 BlobTrashLifetime: 336h
393 # How often to check for (and delete) trashed blocks whose
394 # BlobTrashLifetime has expired.
395 BlobTrashCheckInterval: 24h
397 # Maximum number of concurrent "trash blob" and "delete trashed
398 # blob" operations conducted by a single keepstore process. Each
399 # of these can be set to 0 to disable the respective operation.
401 # If BlobTrashLifetime is zero, "trash" and "delete trash"
402 # happen at once, so only the lower of these two values is used.
403 BlobTrashConcurrency: 4
404 BlobDeleteConcurrency: 4
406 # Maximum number of concurrent "create additional replica of
407 # existing blob" operations conducted by a single keepstore
409 BlobReplicateConcurrency: 4
411 # Default replication level for collections. This is used when a
412 # collection's replication_desired attribute is nil.
413 DefaultReplication: 2
415 # BlobSigningTTL determines the minimum lifetime of transient
416 # data, i.e., blocks that are not referenced by
417 # collections. Unreferenced blocks exist for two reasons:
419 # 1) A data block must be written to a disk/cloud backend device
420 # before a collection can be created/updated with a reference to
423 # 2) Deleting or updating a collection can remove the last
424 # remaining reference to a data block.
426 # If BlobSigningTTL is too short, long-running
427 # processes/containers will fail when they take too long (a)
428 # between writing blocks and writing collections that reference
429 # them, or (b) between reading collections and reading the
432 # If BlobSigningTTL is too long, data will still be stored long
433 # after the referring collections are deleted, and you will
434 # needlessly fill up disks or waste money on cloud storage.
436 # Modifying BlobSigningTTL invalidates existing signatures; see
437 # BlobSigningKey note above.
439 # The default is 2 weeks.
442 # When running keep-balance, this is the destination filename for
443 # the list of lost block hashes if there are any, one per line.
444 # Updated automically during each successful run.
445 BlobMissingReport: ""
447 # keep-balance operates periodically, i.e.: do a
448 # scan/balance operation, sleep, repeat.
450 # BalancePeriod determines the interval between start times of
451 # successive scan/balance operations. If a scan/balance operation
452 # takes longer than BalancePeriod, the next one will follow it
455 # If SIGUSR1 is received during an idle period between operations,
456 # the next operation will start immediately.
459 # Limits the number of collections retrieved by keep-balance per
460 # API transaction. If this is zero, page size is
461 # determined by the API server's own page size limits (see
462 # API.MaxItemsPerResponse and API.MaxIndexDatabaseRead).
463 BalanceCollectionBatch: 0
465 # The size of keep-balance's internal queue of
466 # collections. Higher values use more memory and improve throughput
467 # by allowing keep-balance to fetch the next page of collections
468 # while the current page is still being processed. If this is zero
469 # or omitted, pages are processed serially.
470 BalanceCollectionBuffers: 1000
472 # Maximum time for a rebalancing run. This ensures keep-balance
473 # eventually gives up and retries if, for example, a network
474 # error causes a hung connection that is never closed by the
475 # OS. It should be long enough that it doesn't interrupt a
476 # long-running balancing operation.
479 # Maximum number of replication_confirmed /
480 # storage_classes_confirmed updates to write to the database
481 # after a rebalancing run. When many updates are needed, this
482 # spreads them over a few runs rather than applying them all at
484 BalanceUpdateLimit: 100000
486 # Default lifetime for ephemeral collections: 2 weeks. This must not
487 # be less than BlobSigningTTL.
488 DefaultTrashLifetime: 336h
490 # Interval (seconds) between trash sweeps. During a trash sweep,
491 # collections are marked as trash if their trash_at time has
492 # arrived, and deleted if their delete_at time has arrived.
493 TrashSweepInterval: 60s
495 # If true, enable collection versioning.
496 # When a collection's preserve_version field is true or the current version
497 # is older than the amount of seconds defined on PreserveVersionIfIdle,
498 # a snapshot of the collection's previous state is created and linked to
499 # the current collection.
500 CollectionVersioning: false
502 # 0s = auto-create a new version on every update.
503 # -1s = never auto-create new versions.
504 # > 0s = auto-create a new version when older than the specified number of seconds.
505 PreserveVersionIfIdle: -1s
507 # If non-empty, allow project and collection names to contain
508 # the "/" character (slash/stroke/solidus), and replace "/" with
509 # the given string in the filesystem hierarchy presented by
510 # WebDAV. Example values are "%2f" and "{slash}". Names that
511 # contain the substitution string itself may result in confusing
512 # behavior, so a value like "_" is not recommended.
514 # If the default empty value is used, the server will reject
515 # requests to create or rename a collection when the new name
518 # If the value "/" is used, project and collection names
519 # containing "/" will be allowed, but they will not be
520 # accessible via WebDAV.
522 # Use of this feature is not recommended, if it can be avoided.
523 ForwardSlashNameSubstitution: ""
525 # Include "folder objects" in S3 ListObjects responses.
526 S3FolderObjects: true
528 # Managed collection properties. At creation time, if the client didn't
529 # provide the listed keys, they will be automatically populated following
530 # one of the following behaviors:
532 # * UUID of the user who owns the containing project.
533 # responsible_person_uuid: {Function: original_owner, Protected: true}
535 # * Default concrete value.
536 # foo_bar: {Value: baz, Protected: false}
538 # If Protected is true, only an admin user can modify its value.
540 SAMPLE: {Function: original_owner, Protected: true}
542 # In "trust all content" mode, Workbench will redirect download
543 # requests to WebDAV preview link, even in the cases when
544 # WebDAV would have to expose XSS vulnerabilities in order to
545 # handle the redirect (see discussion on Services.WebDAV).
547 # This setting has no effect in the recommended configuration, where the
548 # WebDAV service is configured to have a separate domain for every
549 # collection and XSS protection is provided by browsers' same-origin
552 # The default setting (false) is appropriate for a multi-user site.
553 TrustAllContent: false
555 # Cache parameters for WebDAV content serving:
557 # Time to cache manifests, permission checks, and sessions.
560 # Time to cache collection state.
563 # Block cache entries. Each block consumes up to 64 MiB RAM.
566 # Collection cache entries.
567 MaxCollectionEntries: 1000
569 # Approximate memory limit (in bytes) for collection cache.
570 MaxCollectionBytes: 100000000
572 # UUID cache entries.
575 # Persistent sessions.
578 # Selectively set permissions for regular users and admins to
579 # download or upload data files using the upload/download
580 # features for Workbench, WebDAV and S3 API support.
589 # Selectively set permissions for regular users and admins to be
590 # able to download or upload blocks using arv-put and
591 # arv-get from outside the cluster.
600 # Post upload / download events to the API server logs table, so
601 # that they can be included in the arv-user-activity report.
602 # You can disable this if you find that it is creating excess
603 # load on the API server and you don't need it.
604 WebDAVLogEvents: true
607 # One of the following mechanisms (Google, PAM, LDAP, or
608 # LoginCluster) should be enabled; see
609 # https://doc.arvados.org/install/setup-login.html
612 # Authenticate with Google.
615 # Use the Google Cloud console to enable the People API (APIs
616 # and Services > Enable APIs and services > Google People API
617 # > Enable), generate a Client ID and secret (APIs and
618 # Services > Credentials > Create credentials > OAuth client
619 # ID > Web application) and add your controller's /login URL
620 # (e.g., "https://zzzzz.example.com/login") as an authorized
625 # Allow users to log in to existing accounts using any verified
626 # email address listed by their Google account. If true, the
627 # Google People API must be enabled in order for Google login to
628 # work. If false, only the primary email address will be used.
629 AlternateEmailAddresses: true
631 # Send additional parameters with authentication requests. See
632 # https://developers.google.com/identity/protocols/oauth2/openid-connect#authenticationuriparameters
633 # for a list of supported parameters.
634 AuthenticationRequestParameters:
635 # Show the "choose which Google account" page, even if the
636 # client is currently logged in to exactly one Google
638 prompt: select_account
643 # Authenticate with an OpenID Connect provider.
646 # Issuer URL, e.g., "https://login.example.com".
648 # This must be exactly equal to the URL returned by the issuer
649 # itself in its config response ("isser" key). If the
650 # configured value is "https://example" and the provider
651 # returns "https://example:443" or "https://example/" then
652 # login will fail, even though those URLs are equivalent
656 # Your client ID and client secret (supplied by the provider).
660 # OpenID claim field containing the user's email
661 # address. Normally "email"; see
662 # https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims
665 # OpenID claim field containing the email verification
666 # flag. Normally "email_verified". To accept every returned
667 # email address without checking a "verified" field at all,
668 # use the empty string "".
669 EmailVerifiedClaim: "email_verified"
671 # OpenID claim field containing the user's preferred
672 # username. If empty, use the mailbox part of the user's email
676 # Send additional parameters with authentication requests,
677 # like {display: page, prompt: consent}. See
678 # https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest
679 # and refer to your provider's documentation for supported
681 AuthenticationRequestParameters:
684 # Accept an OIDC access token as an API token if the OIDC
685 # provider's UserInfo endpoint accepts it.
687 # AcceptAccessTokenScope should also be used when enabling
689 AcceptAccessToken: false
691 # Before accepting an OIDC access token as an API token, first
692 # check that it is a JWT whose "scope" value includes this
693 # value. Example: "https://zzzzz.example.com/" (your Arvados
696 # If this value is empty and AcceptAccessToken is true, all
697 # access tokens will be accepted regardless of scope,
698 # including non-JWT tokens. This is not recommended.
699 AcceptAccessTokenScope: ""
702 # Use PAM to authenticate users.
705 # PAM service name. PAM will apply the policy in the
706 # corresponding config file (e.g., /etc/pam.d/arvados) or, if
707 # there is none, the default "other" config.
710 # Domain name (e.g., "example.com") to use to construct the
711 # user's email address if PAM authentication returns a
712 # username with no "@". If empty, use the PAM username as the
713 # user's email address, whether or not it contains "@".
715 # Note that the email address is used as the primary key for
716 # user records when logging in. Therefore, if you change
717 # PAMDefaultEmailDomain after the initial installation, you
718 # should also update existing user records to reflect the new
719 # domain. Otherwise, next time those users log in, they will
720 # be given new accounts instead of accessing their existing
722 DefaultEmailDomain: ""
725 # Use an LDAP service to authenticate users.
728 # Server URL, like "ldap://ldapserver.example.com:389" or
729 # "ldaps://ldapserver.example.com:636".
730 URL: "ldap://ldap:389"
732 # Use StartTLS upon connecting to the server.
735 # Skip TLS certificate name verification.
738 # Strip the @domain part if a user supplies an email-style
739 # username with this domain. If "*", strip any user-provided
740 # domain. If "", never strip the domain part. Example:
744 # If, after applying StripDomain, the username contains no "@"
745 # character, append this domain to form an email-style
746 # username. Example: "example.com"
749 # The LDAP attribute to filter on when looking up a username
750 # (after applying StripDomain and AppendDomain).
753 # Bind with this username (DN or UPN) and password when
754 # looking up the user record.
756 # Example user: "cn=admin,dc=example,dc=com"
758 SearchBindPassword: ""
760 # Directory base for username lookup. Example:
761 # "ou=Users,dc=example,dc=com"
764 # Additional filters to apply when looking up users' LDAP
765 # entries. This can be used to restrict access to a subset of
766 # LDAP users, or to disambiguate users from other directory
767 # entries that have the SearchAttribute present.
769 # Special characters in assertion values must be escaped (see
772 # Example: "(objectClass=person)"
775 # LDAP attribute to use as the user's email address.
777 # Important: This must not be an attribute whose value can be
778 # edited in the directory by the users themselves. Otherwise,
779 # users can take over other users' Arvados accounts trivially
780 # (email address is the primary key for Arvados accounts.)
783 # LDAP attribute to use as the preferred Arvados username. If
784 # no value is found (or this config is empty) the username
785 # originally supplied by the user will be used.
786 UsernameAttribute: uid
789 # Authenticate users listed here in the config file. This
790 # feature is intended to be used in test environments, and
791 # should not be used in production.
795 Email: alice@example.com
798 # The cluster ID to delegate the user database. When set,
799 # logins on this cluster will be redirected to the login cluster
800 # (login cluster must appear in RemoteClusters with Proxy: true)
803 # How long a cached token belonging to a remote cluster will
804 # remain valid before it needs to be revalidated.
805 RemoteTokenRefresh: 5m
807 # How long a client token created from a login flow will be valid without
808 # asking the user to re-login. Example values: 60m, 8h.
809 # Default value zero means tokens don't have expiration.
812 # If true (default) tokens issued through login are allowed to create
814 # If false, tokens issued through login are not allowed to
815 # viewing/creating other tokens. New tokens can only be created
816 # by going through login again.
817 IssueTrustedTokens: true
819 # When the token is returned to a client, the token itself may
820 # be restricted from viewing/creating other tokens based on whether
821 # the client is "trusted" or not. The local Workbench1 and
822 # Workbench2 are trusted by default, but if this is a
823 # LoginCluster, you probably want to include the other Workbench
824 # instances in the federation in this list.
827 "https://workbench.federate1.example": {}
828 "https://workbench.federate2.example": {}
831 # Path to git or gitolite-shell executable. Each authenticated
832 # request will execute this program with the single argument "http-backend"
833 GitCommand: /usr/bin/git
835 # Path to Gitolite's home directory. If a non-empty path is given,
836 # the CGI environment will be set up to support the use of
837 # gitolite-shell as a GitCommand: for example, if GitoliteHome is
838 # "/gh", then the CGI environment will have GITOLITE_HTTP_HOME=/gh,
839 # PATH=$PATH:/gh/bin, and GL_BYPASS_ACCESS_CHECKS=1.
842 # Git repositories must be readable by api server, or you won't be
843 # able to submit crunch jobs. To pass the test suites, put a clone
844 # of the arvados tree in {git_repositories_dir}/arvados.git or
845 # {git_repositories_dir}/arvados/.git
846 Repositories: /var/lib/arvados/git/repositories
854 # List of supported Docker Registry image formats that compute nodes
855 # are able to use. `arv keep docker` will error out if a user tries
856 # to store an image with an unsupported format. Use an empty array
857 # to skip the compatibility check (and display a warning message to
860 # Example for sites running docker < 1.10: {"v1": {}}
861 # Example for sites running docker >= 1.10: {"v2": {}}
862 # Example for disabling check: {}
863 SupportedDockerImageFormats:
867 # Include details about job reuse decisions in the server log. This
868 # causes additional database queries to run, so it should not be
869 # enabled unless you expect to examine the resulting logs for
870 # troubleshooting purposes.
871 LogReuseDecisions: false
873 # Default value for keep_cache_ram of a container's runtime_constraints.
874 DefaultKeepCacheRAM: 268435456
876 # Number of times a container can be unlocked before being
877 # automatically cancelled.
878 MaxDispatchAttempts: 5
880 # Default value for container_count_max for container requests. This is the
881 # number of times Arvados will create a new container to satisfy a container
882 # request. If a container is cancelled it will retry a new container if
883 # container_count < container_count_max on any container requests associated
884 # with the cancelled container.
887 # The maximum number of compute nodes that can be in use simultaneously
888 # If this limit is reduced, any existing nodes with slot number >= new limit
889 # will not be counted against the new limit. In other words, the new limit
890 # won't be strictly enforced until those nodes with higher slot numbers
894 # Preemptible instance support (e.g. AWS Spot Instances)
895 # When true, child containers will get created with the preemptible
896 # scheduling parameter parameter set.
897 UsePreemptibleInstances: false
899 # PEM encoded SSH key (RSA, DSA, or ECDSA) used by the
900 # cloud dispatcher for executing containers on worker VMs.
901 # Begins with "-----BEGIN RSA PRIVATE KEY-----\n"
902 # and ends with "\n-----END RSA PRIVATE KEY-----\n".
903 DispatchPrivateKey: ""
905 # Maximum time to wait for workers to come up before abandoning
906 # stale locks from a previous dispatch process.
909 # The crunch-run command used to start a container on a worker node.
911 # When dispatching to cloud VMs, this is used only if
912 # DeployRunnerBinary in the CloudVMs section is set to the empty
914 CrunchRunCommand: "crunch-run"
916 # Extra arguments to add to crunch-run invocation
917 # Example: ["--cgroup-parent-subsystem=memory"]
918 CrunchRunArgumentsList: []
920 # Extra RAM to reserve on the node, in addition to
921 # the amount specified in the container's RuntimeConstraints
922 ReserveExtraRAM: 256MiB
924 # Minimum time between two attempts to run the same container
927 # Container runtime: "docker" (default) or "singularity"
928 RuntimeEngine: docker
930 # When running a container, run a dedicated keepstore process,
931 # using the specified number of 64 MiB memory buffers per
932 # allocated CPU core (VCPUs in the container's runtime
933 # constraints). The dedicated keepstore handles I/O for
934 # collections mounted in the container, as well as saving
937 # A zero value disables this feature.
939 # In order for this feature to be activated, no volume may use
940 # AccessViaHosts, and each volume must have Replication higher
941 # than Collections.DefaultReplication. If these requirements are
942 # not satisfied, the feature is disabled automatically
943 # regardless of the value given here.
945 # Note that when this configuration is enabled, the entire
946 # cluster configuration file, including the system root token,
947 # is copied to the worker node and held in memory for the
948 # duration of the container.
949 LocalKeepBlobBuffersPerVCPU: 1
951 # When running a dedicated keepstore process for a container
952 # (see LocalKeepBlobBuffersPerVCPU), write keepstore log
953 # messages to keepstore.txt in the container's log collection.
955 # These log messages can reveal some volume configuration
956 # details, error messages from the cloud storage provider, etc.,
957 # which are not otherwise visible to users.
960 # * "none" -- no keepstore.txt file
961 # * "all" -- all logs, including request and response lines
962 # * "errors" -- all logs except "response" logs with 2xx
963 # response codes and "request" logs
964 LocalKeepLogsToContainerLog: none
967 # When you run the db:delete_old_container_logs task, it will find
968 # containers that have been finished for at least this many seconds,
969 # and delete their stdout, stderr, arv-mount, crunch-run, and
970 # crunchstat logs from the logs table.
973 # These two settings control how frequently log events are flushed to the
974 # database. Log lines are buffered until either crunch_log_bytes_per_event
975 # has been reached or crunch_log_seconds_between_events has elapsed since
977 LogBytesPerEvent: 4096
978 LogSecondsBetweenEvents: 5s
980 # The sample period for throttling logs.
981 LogThrottlePeriod: 60s
983 # Maximum number of bytes that job can log over crunch_log_throttle_period
984 # before being silenced until the end of the period.
985 LogThrottleBytes: 65536
987 # Maximum number of lines that job can log over crunch_log_throttle_period
988 # before being silenced until the end of the period.
989 LogThrottleLines: 1024
991 # Maximum bytes that may be logged by a single job. Log bytes that are
992 # silenced by throttling are not counted against this total.
993 LimitLogBytesPerJob: 67108864
995 LogPartialLineThrottlePeriod: 5s
997 # Container logs are written to Keep and saved in a
998 # collection, which is updated periodically while the
999 # container runs. This value sets the interval between
1000 # collection updates.
1001 LogUpdatePeriod: 30m
1003 # The log collection is also updated when the specified amount of
1004 # log data (given in bytes) is produced in less than one update
1006 LogUpdateSize: 32MiB
1009 # An admin user can use "arvados-client shell" to start an
1010 # interactive shell (with any user ID) in any running
1014 # Any user can use "arvados-client shell" to start an
1015 # interactive shell (with any user ID) in any running
1016 # container that they started, provided it isn't also
1017 # associated with a different user's container request.
1019 # Interactive sessions make it easy to alter the container's
1020 # runtime environment in ways that aren't recorded or
1021 # reproducible. Consider the implications for automatic
1022 # container reuse before enabling and using this feature. In
1023 # particular, note that starting an interactive session does
1024 # not disqualify a container from being reused by a different
1025 # user/workflow in the future.
1030 SbatchArgumentsList: []
1031 SbatchEnvironmentVariables:
1034 # Path to dns server configuration directory
1035 # (e.g. /etc/unbound.d/conf.d). If false, do not write any config
1036 # files or touch restart.txt (see below).
1037 DNSServerConfDir: ""
1039 # Template file for the dns server host snippets. See
1040 # unbound.template in this directory for an example. If false, do
1041 # not write any config files.
1042 DNSServerConfTemplate: ""
1044 # String to write to {dns_server_conf_dir}/restart.txt (with a
1045 # trailing newline) after updating local data. If false, do not
1046 # open or write the restart.txt file.
1047 DNSServerReloadCommand: ""
1049 # Command to run after each DNS update. Template variables will be
1050 # substituted; see the "unbound" example below. If false, do not run
1052 DNSServerUpdateCommand: ""
1054 ComputeNodeDomain: ""
1055 ComputeNodeNameservers:
1059 # Hostname to assign to a compute node when it sends a "ping" and the
1060 # hostname in its Node record is nil.
1061 # During bootstrapping, the "ping" script is expected to notice the
1062 # hostname given in the ping response, and update its unix hostname
1064 # If false, leave the hostname alone (this is appropriate if your compute
1065 # nodes' hostnames are already assigned by some other mechanism).
1067 # One way or another, the hostnames of your node records should agree
1068 # with your DNS records and your /etc/slurm-llnl/slurm.conf files.
1070 # Example for compute0000, compute0001, ....:
1071 # assign_node_hostname: compute%<slot_number>04d
1072 # (See http://ruby-doc.org/core-2.2.2/Kernel.html#method-i-format for more.)
1073 AssignNodeHostname: "compute%<slot_number>d"
1076 # Arguments to bsub when submitting Arvados containers as LSF jobs.
1078 # Template variables starting with % will be substituted as follows:
1081 # %C number of VCPUs
1085 # Use %% to express a literal %. The %%J in the default will be changed
1086 # to %J, which is interpreted by bsub itself.
1088 # Note that the default arguments cause LSF to write two files
1089 # in /tmp on the compute node each time an Arvados container
1090 # runs. Ensure you have something in place to delete old files
1091 # from /tmp, or adjust the "-o" and "-e" arguments accordingly.
1092 BsubArgumentsList: ["-o", "/tmp/crunch-run.%%J.out", "-e", "/tmp/crunch-run.%%J.err", "-J", "%U", "-n", "%C", "-D", "%MMB", "-R", "rusage[mem=%MMB:tmp=%TMB] span[hosts=1]"]
1094 # Use sudo to switch to this user account when submitting LSF
1097 # This account must exist on the hosts where LSF jobs run
1098 # ("execution hosts"), as well as on the host where the
1099 # Arvados LSF dispatcher runs ("submission host").
1100 BsubSudoUser: "crunch"
1103 # Enable the legacy 'jobs' API (crunch v1). This value must be a string.
1105 # Note: this only enables read-only access, creating new
1106 # legacy jobs and pipelines is not supported.
1108 # 'auto' -- (default) enable the Jobs API only if it has been used before
1109 # (i.e., there are job records in the database)
1110 # 'true' -- enable the Jobs API despite lack of existing records.
1111 # 'false' -- disable the Jobs API despite presence of existing records.
1114 # Git repositories must be readable by api server, or you won't be
1115 # able to submit crunch jobs. To pass the test suites, put a clone
1116 # of the arvados tree in {git_repositories_dir}/arvados.git or
1117 # {git_repositories_dir}/arvados/.git
1118 GitInternalDir: /var/lib/arvados/internal.git
1121 # Enable the cloud scheduler.
1124 # Name/number of port where workers' SSH services listen.
1127 # Interval between queue polls.
1130 # Shell command to execute on each worker to determine whether
1131 # the worker is booted and ready to run containers. It should
1132 # exit zero if the worker is ready.
1133 BootProbeCommand: "systemctl is-system-running"
1135 # Minimum interval between consecutive probes to a single
1139 # Maximum probes per second, across all workers in a pool.
1140 MaxProbesPerSecond: 10
1142 # Time before repeating SIGTERM when killing a container.
1145 # Time to give up on a process (most likely arv-mount) that
1146 # still holds a container lockfile after its main supervisor
1147 # process has exited, and declare the instance broken.
1148 TimeoutStaleRunLock: 5s
1150 # Time to give up on SIGTERM and write off the worker.
1153 # Maximum create/destroy-instance operations per second (0 =
1155 MaxCloudOpsPerSecond: 10
1157 # Maximum concurrent instance creation operations (0 = unlimited).
1159 # MaxConcurrentInstanceCreateOps limits the number of instance creation
1160 # requests that can be in flight at any one time, whereas
1161 # MaxCloudOpsPerSecond limits the number of create/destroy operations
1162 # that can be started per second.
1164 # Because the API for instance creation on Azure is synchronous, it is
1165 # recommended to increase MaxConcurrentInstanceCreateOps when running
1166 # on Azure. When using managed images, a value of 20 would be
1167 # appropriate. When using Azure Shared Image Galeries, it could be set
1168 # higher. For more information, see
1169 # https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image
1171 # MaxConcurrentInstanceCreateOps can be increased for other cloud
1172 # providers too, if desired.
1173 MaxConcurrentInstanceCreateOps: 1
1175 # Interval between cloud provider syncs/updates ("list all
1179 # Time to leave an idle worker running (in case new containers
1180 # appear in the queue that it can run) before shutting it
1184 # Time to wait for a new worker to boot (i.e., pass
1185 # BootProbeCommand) before giving up and shutting it down.
1188 # Maximum time a worker can stay alive with no successful
1189 # probes before being automatically shut down.
1192 # Time after shutting down a worker to retry the
1193 # shutdown/destroy operation.
1194 TimeoutShutdown: 10s
1196 # Worker VM image ID.
1197 # (aws) AMI identifier
1198 # (azure) managed disks: the name of the managed disk image
1199 # (azure) shared image gallery: the name of the image definition. Also
1200 # see the SharedImageGalleryName and SharedImageGalleryImageVersion fields.
1201 # (azure) unmanaged disks (deprecated): the complete URI of the VHD, e.g.
1202 # https://xxxxx.blob.core.windows.net/system/Microsoft.Compute/Images/images/xxxxx.vhd
1205 # An executable file (located on the dispatcher host) to be
1206 # copied to cloud instances at runtime and used as the
1207 # container runner/supervisor. The default value is the
1208 # dispatcher program itself.
1210 # Use the empty string to disable this step: nothing will be
1211 # copied, and cloud instances are assumed to have a suitable
1212 # version of crunch-run installed; see CrunchRunCommand above.
1213 DeployRunnerBinary: "/proc/self/exe"
1215 # Tags to add on all resources (VMs, NICs, disks) created by
1216 # the container dispatcher. (Arvados's own tags --
1217 # InstanceType, IdleBehavior, and InstanceSecret -- will also
1222 # Prefix for predefined tags used by Arvados (InstanceSetID,
1223 # InstanceType, InstanceSecret, IdleBehavior). With the
1224 # default value "Arvados", tags are "ArvadosInstanceSetID",
1225 # "ArvadosInstanceSecret", etc.
1227 # This should only be changed while no cloud resources are in
1228 # use and the cloud dispatcher is not running. Otherwise,
1229 # VMs/resources that were added using the old tag prefix will
1230 # need to be detected and cleaned up manually.
1231 TagKeyPrefix: Arvados
1233 # Cloud driver: "azure" (Microsoft Azure) or "ec2" (Amazon AWS).
1236 # Cloud-specific driver parameters.
1239 # (ec2) Credentials. Omit or leave blank if using IAM role.
1243 # (ec2) Instance configuration.
1249 AdminUsername: debian
1251 # (azure) Credentials.
1257 # (azure) Instance configuration.
1258 CloudEnvironment: AzurePublicCloud
1261 # (azure) The resource group where the VM and virtual NIC will be
1265 # (azure) The resource group of the Network to use for the virtual
1266 # NIC (if different from ResourceGroup)
1267 NetworkResourceGroup: ""
1271 # (azure) managed disks: The resource group where the managed disk
1272 # image can be found (if different from ResourceGroup).
1273 ImageResourceGroup: ""
1275 # (azure) shared image gallery: the name of the gallery
1276 SharedImageGalleryName: ""
1277 # (azure) shared image gallery: the version of the image definition
1278 SharedImageGalleryImageVersion: ""
1280 # (azure) unmanaged disks (deprecated): Where to store the VM VHD blobs
1284 # (azure) How long to wait before deleting VHD and NIC
1285 # objects that are no longer being used.
1286 DeleteDanglingResourcesAfter: 20s
1288 # Account (that already exists in the VM image) that will be
1289 # set up with an ssh authorized key to allow the compute
1290 # dispatcher to connect.
1291 AdminUsername: arvados
1295 # Use the instance type name as the key (in place of "SAMPLE" in
1296 # this sample entry).
1298 # Cloud provider's instance type. Defaults to the configured type name.
1302 IncludedScratch: 16GB
1309 # If you use multiple storage classes, specify them here, using
1310 # the storage class name as the key (in place of "SAMPLE" in
1311 # this sample entry).
1313 # Further info/examples:
1314 # https://doc.arvados.org/admin/storage-classes.html
1317 # Priority determines the order volumes should be searched
1318 # when reading data, in cases where a keepstore server has
1319 # access to multiple volumes with different storage classes.
1322 # Default determines which storage class(es) should be used
1323 # when a user/client writes data or saves a new collection
1324 # without specifying storage classes.
1326 # If any StorageClasses are configured, at least one of them
1327 # must have Default: true.
1332 # AccessViaHosts specifies which keepstore processes can read
1333 # and write data on the volume.
1335 # For a local filesystem, AccessViaHosts has one entry,
1336 # indicating which server the filesystem is located on.
1338 # For a network-attached backend accessible by all keepstore
1339 # servers, like a cloud storage bucket or an NFS mount,
1340 # AccessViaHosts can be empty/omitted.
1342 # Further info/examples:
1343 # https://doc.arvados.org/install/configure-fs-storage.html
1344 # https://doc.arvados.org/install/configure-s3-object-storage.html
1345 # https://doc.arvados.org/install/configure-azure-blob-storage.html
1349 "http://host1.example:25107": {}
1353 # If you have configured storage classes (see StorageClasses
1354 # section above), add an entry here for each storage class
1355 # satisfied by this volume.
1359 # for s3 driver -- see
1360 # https://doc.arvados.org/install/configure-s3-object-storage.html
1363 SecretAccessKey: aaaaa
1367 LocationConstraint: false
1374 # Use aws-s3-go (v2) instead of goamz
1375 UseAWSS3v2Driver: false
1377 # For S3 driver, potentially unsafe tuning parameter,
1378 # intentionally excluded from main documentation.
1380 # Enable deletion (garbage collection) even when the
1381 # configured BlobTrashLifetime is zero. WARNING: eventual
1382 # consistency may result in race conditions that can cause
1383 # data loss. Do not enable this unless you understand and
1387 # for azure driver -- see
1388 # https://doc.arvados.org/install/configure-azure-blob-storage.html
1389 StorageAccountName: aaaaa
1390 StorageAccountKey: aaaaa
1391 StorageBaseURL: core.windows.net
1392 ContainerName: aaaaa
1394 ListBlobsRetryDelay: 10s
1395 ListBlobsMaxAttempts: 10
1397 WriteRaceInterval: 15s
1398 WriteRacePollTime: 1s
1400 # for local directory driver -- see
1401 # https://doc.arvados.org/install/configure-fs-storage.html
1402 Root: /var/lib/arvados/keep-data
1404 # For local directory driver, potentially confusing tuning
1405 # parameter, intentionally excluded from main documentation.
1407 # When true, read and write operations (for whole 64MiB
1408 # blocks) on an individual volume will queued and issued
1409 # serially. When false, read and write operations will be
1410 # issued concurrently.
1412 # May possibly improve throughput if you have physical spinning disks
1413 # and experience contention when there are multiple requests
1414 # to the same volume.
1416 # Otherwise, when using SSDs, RAID, or a shared network filesystem, you
1417 # should leave this alone.
1423 SendUserSetupNotificationEmail: true
1425 # Bug/issue report notification to and from addresses
1426 IssueReporterEmailFrom: "arvados@example.com"
1427 IssueReporterEmailTo: "arvados@example.com"
1428 SupportEmailAddress: "arvados@example.com"
1430 # Generic issue email from
1431 EmailFrom: "arvados@example.com"
1438 ActivateUsers: false
1440 # API endpoint host or host:port; default is {id}.arvadosapi.com
1441 Host: sample.arvadosapi.com
1443 # Perform a proxy request when a local client requests an
1444 # object belonging to this remote.
1447 # Default "https". Can be set to "http" for testing.
1450 # Disable TLS verify. Can be set to true for testing.
1453 # When users present tokens issued by this remote cluster, and
1454 # their accounts are active on the remote cluster, activate
1455 # them on this cluster too.
1456 ActivateUsers: false
1459 # Workbench1 configs
1461 ActivationContactLink: mailto:info@arvados.org
1462 ArvadosDocsite: https://doc.arvados.org
1463 ArvadosPublicDataDocURL: https://playground.arvados.org/projects/public
1464 ShowUserAgreementInline: false
1467 # Scratch directory used by the remote repository browsing
1468 # feature. If it doesn't exist, it (and any missing parents) will be
1469 # created using mkdir_p.
1470 RepositoryCache: /var/www/arvados-workbench/current/tmp/git
1472 # Below is a sample setting of user_profile_form_fields config parameter.
1473 # This configuration parameter should be set to either false (to disable) or
1474 # to a map as shown below.
1475 # Configure the map of input fields to be displayed in the profile page
1476 # using the attribute "key" for each of the input fields.
1477 # This sample shows configuration with one required and one optional form fields.
1478 # For each of these input fields:
1479 # You can specify "Type" as "text" or "select".
1480 # List the "Options" to be displayed for each of the "select" menu.
1481 # Set "Required" as "true" for any of these fields to make them required.
1482 # If any of the required fields are missing in the user's profile, the user will be
1483 # redirected to the profile page before they can access any Workbench features.
1484 UserProfileFormFields:
1487 FormFieldTitle: Best color
1488 FormFieldDescription: your favorite color
1497 # exampleTextValue: # key that will be set in properties
1499 # FormFieldTitle: ""
1500 # FormFieldDescription: ""
1503 # exampleOptionsValue:
1505 # FormFieldTitle: ""
1506 # FormFieldDescription: ""
1514 # Use "UserProfileFormMessage to configure the message you want
1515 # to display on the profile page.
1516 UserProfileFormMessage: 'Welcome to Arvados. All <span style="color:red">required fields</span> must be completed before you can proceed.'
1518 # Mimetypes of applications for which the view icon
1519 # would be enabled in a collection's show page.
1520 # It is sufficient to list only applications here.
1521 # No need to list text and image types.
1522 ApplicationMimetypesWithViewIcon:
1540 # The maximum number of bytes to load in the log viewer
1541 LogViewerMaxBytes: 1M
1543 # When anonymous_user_token is configured, show public projects page
1544 EnablePublicProjectsPage: true
1546 # By default, disable the "Getting Started" popup which is specific to Arvados playground
1547 EnableGettingStartedPopup: false
1549 # Ask Arvados API server to compress its response payloads.
1550 APIResponseCompression: true
1552 # Timeouts for API requests.
1553 APIClientConnectTimeout: 2m
1554 APIClientReceiveTimeout: 5m
1556 # Maximum number of historic log records of a running job to fetch
1557 # and display in the Log tab, while subscribing to web sockets.
1558 RunningJobLogRecordsToFetch: 2000
1560 # In systems with many shared projects, loading of dashboard and topnav
1561 # can be slow due to collections indexing; use the following parameters
1562 # to suppress these properties
1563 ShowRecentCollectionsOnDashboard: true
1564 ShowUserNotifications: true
1566 # Enable/disable "multi-site search" in top nav ("true"/"false"), or
1567 # a link to the multi-site search page on a "home" Workbench site.
1570 # https://workbench.zzzzz.arvadosapi.com/collections/multisite
1573 # Should workbench allow management of local git repositories? Set to false if
1574 # the jobs api is disabled and there are no local git repositories.
1577 SiteName: Arvados Workbench
1578 ProfilingEnabled: false
1580 # This is related to obsolete Google OpenID 1.0 login
1581 # but some workbench stuff still expects it to be set.
1582 DefaultOpenIdPrefix: "https://www.google.com/accounts/o8/id"
1584 # Workbench2 configs
1585 FileViewersConfigURL: ""
1587 # Idle time after which the user's session will be auto closed.
1588 # This feature is disabled when set to zero.
1591 # Workbench welcome screen, this is HTML text that will be
1592 # incorporated directly onto the page.
1594 <img src="/arvados-logo-big.png" style="width: 20%; float: right; padding: 1em;" />
1595 <h2>Please log in.</h2>
1597 <p>If you have never used Arvados Workbench before, logging in
1598 for the first time will automatically create a new
1601 <i>Arvados Workbench uses your information only for
1602 identification, and does not retrieve any other personal
1605 # Workbench screen displayed to inactive users. This is HTML
1606 # text that will be incorporated directly onto the page.
1608 <img src="/arvados-logo-big.png" style="width: 20%; float: right; padding: 1em;" />
1609 <h3>Hi! You're logged in, but...</h3>
1610 <p>Your account is inactive.</p>
1611 <p>An administrator must activate your account before you can get
1614 # Connecting to Arvados shell VMs tends to be site-specific.
1615 # Put any special instructions here. This is HTML text that will
1616 # be incorporated directly onto the Workbench page.
1618 <a href="https://doc.arvados.org/user/getting_started/ssh-access-unix.html">Accessing an Arvados VM with SSH</a> (generic instructions).
1619 Site configurations vary. Contact your local cluster administrator if you have difficulty accessing an Arvados shell node.
1621 # Sample text if you are using a "switchyard" ssh proxy.
1622 # Replace "zzzzz" with your Cluster ID.
1624 # <p>Add a section like this to your SSH configuration file ( <i>~/.ssh/config</i>):</p>
1627 # ServerAliveInterval 60
1628 # ProxyCommand ssh -p2222 turnout@switchyard.zzzzz.arvadosapi.com -x -a $SSH_PROXY_FLAGS %h
1631 # If you are using a switchyard ssh proxy, shell node hostnames
1632 # may require a special hostname suffix. In the sample ssh
1633 # configuration above, this would be ".zzzzz"
1634 # This is added to the hostname in the "command line" column
1635 # the Workbench "shell VMs" page.
1637 # If your shell nodes are directly accessible by users without a
1638 # proxy and have fully qualified host names, you should leave
1640 SSHHelpHostSuffix: ""
1642 # (Experimental) Restart services automatically when config file
1643 # changes are detected. Only supported by `arvados-server boot` in
1645 AutoReloadConfig: false