Domino 4.4 (February 2021)¶
- Resumable Workspaces – Stop and resume your workspaces sessions as needed. Your work persists from session to session, ensuring that you never lose your work and enabling you to commit your work to version control whenever you want. To learn more, refer to the workspace sessions documentation.
- Git-based Projects – Git-based projects are a new type of project in Domino that provide a full Git-first experience for your project’s code. Create branches, commit your code, and push or pull changes to your code all from within a workspace in a Git-based project. To learn more, refer to the Git-based projects documentation.
Upgrades & Enhancements
- The Domino Analytics Distribution (DAD) has been upgraded to use Python 3.8. Notable upgrades are listed below. Please see the corresponding changes outlined in the “Breaking Changes” section.
- Upgrade to R 4.0 from 3.6
- Upgrade to Python 3.8 from 3.6
- Upgrade Scala kernel to 2.12.9 and almond to 0.10.9
- Upgrade Julia to 1.5.3 from 1.1.0
- Upgrade JupyterLab 2.2.9 from 1.2.12
- Upgrade Jupyter Notebook 6.1.6 from 6.0.3
- Upgrade (VS Code) Code server 3.7.3 from 3.4.1
- New Python language server for VS Code
- Python extension fix for VS Code
- Jupyterlab-git extension for Jupyterlab
The default Domino Analytics Distribution (DAD) uses Python 3.8, however, PySpark 2 does not support Python 3.8 or higher. If you need a PySpark 2 environment, make sure to build it from images that use Python versions < 3.8.
CUDA has been removed from the upgraded DAD in Domino 4.4.0 to keep the size of the DAD image to a minimal size. If you need to use CUDA 10 or CUDA 11, use the following image:
quay.io/domino/base:Ubuntu18_DAD_Py3.8_R4.0-20210127_CUDA11.0_full. Please note that drivers must be present on the underlying hosts.
You can now set your own volume size for your workspace sessions and Jobs. Your Domino administrator can configure the minimum, maximum, and default sizes for the volume. If your Domino deployment previously utilized a custom volume setting in a prior version of Domino, make sure to edit the corresponding central configuration values after upgrading to Domino 4.4.0 to ensure your runs execute as intended.
If you are upgrading to 4.4.0 from Domino version 4.1.9 or earlier, there is a Keycloak client mapper that Domino depends on which will need to be manually created prior to upgrading.
To create the mapper:
- Go to the Clients tab in the DominoRealm in Keycloak and select the domino-play client.
- Select the Mappers tab for the domino-play client
- Create a new mapper with type User Attribute and the following settings:
- Name: <Your desired friendly name>
- Mapper Type: User Attribute
- User Attribute: domino-system-roles
- Token Claim Name: roles
- Claim JSON Type: string
- Add to ID token: Yes
- Add to access token: Yes
- Add to userinfo: Yes
- Multivalued: Yes
- Aggregate attribute values: No
- After modifying email settings, manually restart services for the email settings to take effect.
- Attempting to update the CLI via the CLI API will fail. Instead, install the CLI from a fresh Domino 4.4.0 deployment.
- Emails are not sending to user(s) mentioned using the “@” tagging feature in a file comment or job comment. Please communicate with the intended user(s) in a different way.
- If you’re launching a Job in a Git-based project, use absolute paths if you’re specifying the name of a file outside of the /mnt/code working directory. The
..command is currently not supported.
- If you’re using a Launcher in a Git-based project, note that files or scripts specified in the “Command to run” text area will execute in /mnt/code. Be sure to account for this if your script results in outputs you’d like to persist.
- Fixed an issue that prevented workspaces from launching in Domino if Domino was deployed with Istio.
- Fixed an issue that affected file creation and file editing in projects.
- Fixed an issue that prevented Spark clusters from launching if they used a GPU-based hardware tier.
- Fixed an issue that prevented users with the “Practitioner” role from creating a project.
- Fixed an issue that prevented Domino runs from executing properly if a file in a linked repository contained non-ASCII characters.
- Restored the “Support” button for all Domino 4.x deployments.
- Fixed an issue that prevented Domino workspaces from being stopped.
- Fixed an issue that prevented data frames from being read properly when using a Spark cluster.
- Fixed an issue that prevented model APIs from being properly exported.
- Fixed an issue that caused failed attempts to push to a protected branch in an external Git repository to appear to have succeeded.
- Fixed an issue that prevented a Git credential from being created if the domain was entered as an IP address.
- Fixed an issue that prevented new models from being created.
- Fixed an issue that prevented project settings from being properly propagated to Spark clusters.
- Fixed an issue that allowed users to edit their own roles.
- Fixed issues that prevented usage report emails from being sent.
- Fixed an issue that prevented datasets from mounting properly when executing a Domino run using the “Save & Run” option present in the “Files” page of a Domino project.
- Fixed an issue that prevented SMPT configuration values from being properly set.
- Fixed an issue that prevented users from viewing datasets in their project if the dataset originated from an imported project.
- Fixed an issue that prevented scratch spaces from being assigned to workspaces that were launched from the “Files” page of a Domino project.
- Fixed an issue that prevented workspaces from launching if a snapshot that was marked for deletion was mounted to another project through a shared dataset.
- Fixed an issue that caused a 502 error when attempting to generate a user activity report.
- Fixed an issue that prevented some Python-based extensions from functioning properly in workspaces that utilized VS Code.
- Fixed an issue that caused files specified in .modelignore to continue to appear with a published model’s files.
- Fixed an issue that allowed multiple hardware tiers to be designated as the “default” hardware tier for a Domino deployment.
- Fixed an issue that affected the “Name” field in cloned hardware tiers.