Central Configuration¶
The Central Configuration is where all global settings for a Domino installation are enumerated. You can access the Central Configuration interface from the Admin portal by clicking Advanced > Central Config.
The interface is organized into a list of records. You can click on an existing record to edit its attributes, or you can add a record with the Add Record button at top right. If there is no record explicitly set for an option, the default value will be used. In order for changes made in the Central Config to take effect, you must to restart Domino services using the link at the top of the interface.
Project visibility options¶
These options are related to
project visibility settings
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
true |
If set to false, users cannot set projects to public visibility. |
|
Public |
Controls the default visibility setting for new projects. Options are Public or Private. |
Email notifications¶
These options are related to
email notifications from Domino
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
None | The ‘from’ address for email notifications sent by Domino. |
|
None | Hostname of SMTP relay to use for sending emails from Domino. |
|
None | Username to use for authenticating to the SMTP host. |
|
None | Password for the SMTP user. |
|
25 |
Port to use for connecting to SMTP host. |
|
false |
Whether the SMTP host uses SSL. |
Model APIs¶
These options are related to
Model APIs
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
2 |
Default number of instances per Model used for Model API scaling. |
|
32 |
Maximum number of instances per Model used for Model API scaling. |
|
dominodatalab.com/node-pool |
Key used in Kubernetes label node selector for Model API pods. |
|
default |
Value used in Kubernetes label node selector for Model API pods. |
Environments¶
These options are related to
Domino Environments
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
true |
If set to false only system administrators will be able to edit environments. |
|
|
Docker image URI for the initial default environment. |
|
Domino Analytics Distribution Py3.6 R3.6 | Name of the initial default environment. |
Authentication¶
These options are related to the Keycloak authentication service
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
false |
When true Domino will manage Organization membership via users’ group SAML attributes |
|
false |
When true Domino will manage Admin roles assignments via users’ role SAML attributes |
Long-running workspaces¶
These options are related to long-running workspace sessions
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
259200 |
Defines how long a workspace must run in seconds before the workspace is classified as ‘long-running’ and begins to generate notifications or becomes subject to automatic shutdown. |
|
false |
Set to true to enable the option for email notifications to users when their workspaces become long-running. Users can turn these notifications on or off for themselves in their account settings. |
|
false |
Set to true to turn on long-running workspace notifications for all users. While this is true users cannot turn off long-running workspace notifications. |
|
7200 |
Maximum time in seconds users may set as the period between receiving long-running notification emails. Users will receive repeated notifications about long-running workspaces with this frequency. |
|
false |
Set to true to enable automatic shutdown of long-running workspaces. Users can turn automatic shutdown for their workspaces on or off from their account settings. |
|
false |
Set to true to turn on automatic shutdown of long-running workspaces for all users. While this is true users cannot turn off automatic shutdown of their long-running workspaces. |
|
259200 |
Longest time in seconds a long-running workspace will be allowed to continue before automatic shutdown. Users cannot set their automatic shutdown timer to be longer than this. |
Datasets scratch spaces¶
These options are related to datasets scratch spaces
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
5.5 |
This option sets the first datasets scratch space risk threshold in days. Scratch spaces with changes that have not been recorded as a snapshot for this duration are marked as medium risk. |
|
10 |
This option controls the second datasets scratch space risk threshold in days. Scratch spaces with changes that have not been recorded as a snapshot for this duration are marked as high risk. |
Compute grid¶
These options are related to the compute grid
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
10min |
Controls how often the garbage collector runs to delete old or excess persistent volumes. |
|
None | Setting a value in minutes here will cause persistent volumes older than that to be automatically deleted by the garbage collector. |
|
32 |
Maximum number of idle persistent volumes to keep. Idle volumes in excess of this number will be deleted by the garbage collector. |
|
64 |
Maximum number of salvaged volumes to keep. Salvaged volumes in excess of this number will be deleted by the garbage collector. |
|
7d |
Setting a value in days here will cause salvaged volumes older than that to be automatically deleted by the garbage collector. |
|
dominodisk |
Kubernetes storage class that will be used to dynamically provision persistent volumes. This is set initially to the value of storage_classes.block.name in the installer storage classes configuration. |
|
15 |
Size in GB of compute grid persistent volumes. This is the total amount of disk space available to users in runs and workspaces. |
|
25 |
This is the maximum number of executions each user will be allowed to run concurrently. If a user attempts to start additional executions in excess of this those executions will be queued until some of the user’s other executions finish. |
On-demand Spark¶
These options are related to the on-demand Spark clusters
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
1 |
Frequency in seconds to run status checks on on-demand Spark clusters. |
|
/tmp |
File system path on which Spark worker storage is mounted. |
|
None | Option to supply alternative default configuration directory for on-demand Spark clusters. |
|
384 |
Minimum amount of memory in MiB to use for Spark worker overhead. |
|
0.1 |
Spark worker overhead scaling factor. |
File download API¶
These options are related to the file contents download API endpoint
and are available in namespace common and should be recorded with no name.
| key | default | description |
|---|---|---|
|
false |
Set to true to require an admin API key to download files via API. When false, any user with the blob ID for a file may download it via API. |
Builder¶
These options are related to the Domino builder.
The Domino builder is a container that runs as a Kubernetes job to build
the Docker images for Domino environments and Domino model APIs.
This container is deployed to a node labeled with a configurable Kubernetes label (defaults to domino/build-node=true) whenever a user triggers an environment or model build.
| key | default | description |
|---|---|---|
|
domino/build-node |
Node label key that the selector in the pod specification for the builder job will target. |
|
true |
Node label value that the selector in the pod specification for the builder job will target. |
|
/var/run/docker.sock |
The builder job mounts the host Docker socket to execute builds. This should point to a path on the builder nodes where a Docker socket file can be mounted as part of the builder job pod specification. |